Re: [dpdk-dev] [EXT] [PATCH] net/octeontx: use logtype_init for failed probe

[Jerin Jacob Kollanukkaran <jerinj@marvell.com>]

> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, July 19, 2019 10:29 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: dev@dpdk.org
> Subject: Re: [EXT] [PATCH] net/octeontx: use logtype_init for failed probe
> 
> On Fri, 19 Jul 2019 03:37:26 +0000
> Jerin Jacob Kollanukkaran <jerinj@marvell.com> wrote:
> 
> > > -----Original Message-----
> > > From: Stephen Hemminger <stephen@networkplumber.org>
> > > Sent: Wednesday, July 17, 2019 12:18 AM
> > > To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> > > Cc: dev@dpdk.org
> > > Subject: [EXT] [PATCH] net/octeontx: use logtype_init for failed
> > > probe
> >
> > > All log messages should use driver logtype. RTE_LOGTYPE_PMD is
> > > planned to be deprecated in the future.
> > >
> > > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > > ---
> >
> > Please fix
> >
> > $ ./devtools/check-git-log.sh
> > Wrong headline format:
> >         net/octeontx: use logtype_init for failed probe
> >

Changed the git commit to:
net/octeontx: use driver logtype

Applied to dpdk-next-net-mrvl/master. Thanks


> 
> OK but
> 
> That rule in check-git-log is still ridiculous because it rejects perfectly good
> commit subjects. The intention is good "stop automated bots" but the
> implementation rejects too many good patches.