| 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, 21 Aug 2013 10:54:16 -0500 From: Ben Myers <bpm@....com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: cbe-oss-dev@...ts.ozlabs.org, Arnd Bergmann <arnd@...db.de>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Dwight Engen <dwight.engen@...cle.com>, linux-kernel@...r.kernel.org, xfs@....sgi.com, linux-next@...r.kernel.org, Jeremy Kerr <jk@...abs.org>, linuxppc-dev@...ts.ozlabs.org, Gao feng <gaofeng@...fujitsu.com> Subject: Re: linux-next: build failure after merge of the final tree Hey Stephen, On Wed, Aug 21, 2013 at 10:22:46AM +1000, Stephen Rothwell wrote: > On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers <bpm@....com> wrote: > > I'd prefer not to break Stephen's tree two days in a row. We could just revert > > d6970d4b726c in the xfs tree for the time being as Stephen has done, but given > > the choice would prefer the fix. Do you have a preference between the two > > approaches that Dwight has posted? The first seems more conservative... > > I will automatically revert that commit when I merge the xfs tree until > some other solution is forthcoming (so you don't have to do the revert in > the xfs tree). Gah. That makes sense. ;) > This does need to be fixed fairly soon, though. Agreed, thanks. -Ben -- 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