Re: [EXT] Re: [PATCH v2] devtools: ensure proper tag sequence

2022-06-15 Thread Thomas Monjalon
15/06/2022 10:46, Jakub Palider: > > -Original Message- > > From: Thomas Monjalon > > Sent: Wednesday, June 15, 2022 8:21 AM > > To: Jakub Palider > > Cc: dev@dpdk.org; david.march...@redhat.com > > Subject: [EXT] Re: [PATCH v2] devtools: ensure p

RE: [EXT] Re: [PATCH v2] devtools: ensure proper tag sequence

2022-06-15 Thread Jakub Palider
> -Original Message- > From: Thomas Monjalon > Sent: Wednesday, June 15, 2022 8:21 AM > To: Jakub Palider > Cc: dev@dpdk.org; david.march...@redhat.com > Subject: [EXT] Re: [PATCH v2] devtools: ensure proper tag sequence &

Re: [PATCH v2] devtools: ensure proper tag sequence

2022-06-14 Thread Thomas Monjalon
14/06/2022 00:21, jpali...@marvell.com: > + SEQ[0] = "Coverity issue"; > + SEQ[1] = "Bugzilla ID"; > + SEQ[2] = "Fixes"; > + SEQ[3] = "Cc"; > + SEQ[4] = "^$"; > + SEQ[5] = "Suggested-by"; > + SEQ[6] = "Reported-by";

[PATCH v2] devtools: ensure proper tag sequence

2022-06-13 Thread jpalider
From: Jakub Palider This change to log checking procedure ensures that certain tags are in proper order. The order of tags is as follows: * Coverity issue * Bugzilla ID * Fixes * Cc * * Suggested-by * Reported-by + Signed-off-by where: * => 0 or more than one instance possible + => mor