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
| ||
|
Date: Fri, 11 Jul 2014 19:00:48 -0700 From: Randy Dunlap <rdunlap@...radead.org> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Peter Hurley <peter@...leysoftware.com> CC: Stephen Rothwell <sfr@...b.auug.org.au>, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org Subject: Re: [PATCH] serial: imx: Fix build breakage On 07/11/14 17:42, Greg Kroah-Hartman wrote: > On Thu, Jul 10, 2014 at 10:36:46PM -0400, Peter Hurley wrote: >> Fix breakage introduced by >> commit c557d392fbf5badd693ea1946a4317c87a26a716, >> 'serial: Test for no tx data on tx restart'. >> >> Signed-off-by: Peter Hurley <peter@...leysoftware.com> > > You forgot a "Reported-by:" tag. > > I'll go add it... It's not clear to me that Peter forgot it. Someone else brought this up -- it seems to me that Documentation/SubmittingPatches is a little too strong about needing permission to use Reported-by: If this patch fixes a problem reported by somebody else, consider adding a Reported-by: tag to credit the reporter for their contribution. Please note that this tag should not be added without the reporter's permission, especially if the problem was not reported in a public forum. That said, if we diligently credit our bug reporters, they will, hopefully, be inspired to help us again in the future. Sure, if a problem was reported privately, then we need to have permission to use Reported-by, but if it was reported in a public forum, that should be implicit permission (IMHO). eh? -- ~Randy -- 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/
Powered by blists - more mailing lists