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]
Message-ID: <1284738264.4177.25.camel@m0nster>
Date:	Fri, 17 Sep 2010 08:44:24 -0700
From:	Daniel Walker <dwalker@...o99.com>
To:	Russell King <rmk@....linux.org.uk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Sundar R IYER <sundar.iyer@...ricsson.com>,
	Linus WALLEIJ <linus.walleij@...ricsson.com>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: FW: next build fails

On Fri, 2010-09-17 at 11:35 +0100, Russell King wrote:
> On Thu, Sep 16, 2010 at 03:08:55PM -0700, Daniel Walker wrote:
> > On Fri, 2010-09-17 at 08:04 +1000, Stephen Rothwell wrote:
> > > Hi Daniel,
> > > 
> > > On Thu, 16 Sep 2010 14:58:57 -0700 Daniel Walker <dwalker@...o99.com> wrote:
> > > >
> > > > Yeah, exactly .. This is what I did to update my patch .. Do you want to
> > > > include this, or should I update my version and my tree.. Ultimately my
> > > > version has to go into Russell's tree..
> > > 
> > > Well, you can't really update that in your tree until after your tree is
> > > merged with Russell's, right (since ALT_UP etc are not defined in your
> > > tree)?  In that case, I need to do the fix when I merge your tree into
> > > linux-next (and so with Russell's tree).
> > 
> > Right, I see what your saying .. Ok, thanks.
> 
> There is another way to handle this - we shouldn't be tinkering with
> the aux control register on non-ARM cores (as we don't know what the
> bits on such cores do) we could view this as a bug fix, and put it
> into -rc.

Yeah, it does seem to fit that category ..

> I'd prefer to do that - so could you send the original patch you posted
> to lakml to the patch system please?

Ok, I submitted it to your patch system (I'm assuming that's what you
mean by "patch system above").

http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6398/1

Daniel

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ