linux-kernel - Re: [git patches] net driver fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 20 Sep 2008 00:24:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	horms@...ge.net.au
Cc:	jeff@...zik.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [git patches] net driver fixes

From: Simon Horman <horms@...ge.net.au>
Date: Tue, 16 Sep 2008 12:01:18 +1000

> On Mon, Sep 15, 2008 at 02:11:59PM -0700, David Miller wrote:
> 
> [snip]
> > 
> > Not a 2.6.27 regression, this problem has been there forever.
> > 
> > 	Magnus Damm (2):
> > 	      smc91x: fix nowait printout
> > 
> > This one is good but the commit message needs to be fixed up.
> > It references a raw SHA1 ID but does not give the commit message
> > header line as well, which is a requirement.
> > 
> >       smc91x: SMC_IO_SHIFT platform data support for default case
> > 
> > Ok, but needs commit header line text for referenced commit.
> 
> can you confirm that the commit message requirement stands even
> if the SHA1 ID references Linus' tree? I personally think that is
> reasonable, I just want to confirm that is the requirement.

Yes, because the commit messages will propagate back usually
verbatim for changes backported into the -stable branches.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/