| 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, 5 Oct 2011 11:52:35 -0600 From: Grant Likely <grant.likely@...retlab.ca> To: Tomoya MORINAGA <tomoya-linux@....lapis-semi.com> Cc: Tomoya MORINAGA <tomoya-linux@....okisemi.com>, linux-kernel@...r.kernel.org, alexander.stein@...tec-electronic.com, qi.wang@...el.com, yong.y.wang@...el.com, joel.clark@...el.com, kok.howg.ewe@...el.com Subject: Re: [PATCH 3/3] gpio-ml-ioh: Fix suspend/resume issue On Wed, Oct 05, 2011 at 10:30:15AM +0900, Tomoya MORINAGA wrote: > Hi Grant, > > (2011/10/05 1:07), Grant Likely wrote: > >On Fri, Aug 05, 2011 at 01:04:22PM +0900, Tomoya MORINAGA wrote: > >Can this one be merged without 1/3 and 2/3? Patch 2 looks like a > >feature instead of a bug fix. > > > > Is the above true ? > I think, > 1/3 is a bug fix. > 2/3 and 3/3 are feature. Considering that the title of 3/3 is "Fix suspend/resume issue", you can understand my confusion. I'm not talking about 1/3 because it looks like a trivial cleanup (not a bug fix). > Do you mean you will merge only patch for a bug fix ? > What will you do feature patch ? I'll merge them regardless, I just need to know which branch to merge them in. If patch 3 is a bug fix independent of patches 1 & 2, then I'll put it in spi/merge and ask Linus to pull right away. Otherwise I'll put it in spi/next along with patches 1 & 2. g. -- 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