| 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: Wed, 8 Apr 2015 12:35:12 +0200 From: Pavel Machek <pavel@....cz> To: Lee Jones <lee.jones@...aro.org> Cc: Eduardo Valentin <edubezval@...il.com>, ajitpal.singh@...com, rui.zhang@...el.com, linux-kernel@...r.kernel.org Subject: Re: patch "drivers: thermal: st: remove several sparse warnings" added to thermal-soc tree > > > > And there's no harm in having patch available in git for easy testing. > > > > > > If we weren't so deep into the release cycle, I'd agree with you. But > > > even if we weren't so close to the merge-window, I'd still expect a > > > note to the tune of "tentatively applying this for reason X for early > > > soak testing in -next". Although X would have to be a pretty good > > > reason, as that's not usually how we do things. > > > > Patches should spend a week or so in -next (that's documented > > somewhere), so people in the Cc list will have their chance to > > comment. > > Yes they should, _after_ reviewing. Chucking patches into -next > before others have been given a chance to review is _not_ the right > thing to do. If everyone did that -next would be unbuildable and This is up to the maintainer, and given how trivial patch was, he did the right thing. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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