Re: [dpdk-dev] [PATCH] devtools: select patches to check with git range

2019-05-09 Thread Thomas Monjalon
09/05/2019 23:54, Thomas Monjalon: > 22/03/2019 14:16, David Marchand: > > --- a/devtools/checkpatches.sh > > +++ b/devtools/checkpatches.sh > > - usage: $(basename $0) [-q] [-v] [-nX|patch1 [patch2] ...]] > > + usage: $(basename $0) [-q] [-v] [-nX|patch1 [patch2] ...]] [-r range] > > The opti

Re: [dpdk-dev] [PATCH] devtools: select patches to check with git range

2019-05-09 Thread Thomas Monjalon
22/03/2019 14:16, David Marchand: > --- a/devtools/checkpatches.sh > +++ b/devtools/checkpatches.sh > - usage: $(basename $0) [-q] [-v] [-nX|patch1 [patch2] ...]] > + usage: $(basename $0) [-q] [-v] [-nX|patch1 [patch2] ...]] [-r range] The option -r should be before the filename arguments

[dpdk-dev] [PATCH] devtools: select patches to check with git range

2019-03-22 Thread David Marchand
Rather than default to origin/master.., it can be handy to choose the range you want to check. Example on a branch rebased on next-net: Before: [dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh ... ... 67/69 valid patches After: [dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh -r next-net