linux-kernel - Re: [PATCH RESEND] x86, intel

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120411234632.GA11113@kroah.com>
Date:	Wed, 11 Apr 2012 16:46:32 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, mingo@...e.hu,
	linux-kernel@...r.kernel.org, Jonathan Cameron <jic23@...nel.org>,
	"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>
Subject: Re: [PATCH RESEND] x86, intel_mid: ADC management

On Wed, Apr 11, 2012 at 05:30:47PM +0100, Jonathan Cameron wrote:
> >Anyway, all I care about to get this code out of staging is that you
> >feel your userspace api is "sane" and not going to change.  Your
> >in-kernel stuff can radically change every kernel release with no
> >objection from me at all.
> >
> >And from what I can tell, your userspace stuff looks pretty stable now,
> >right?  So, I don't mind moving this all out of staging for 3.5 as-is.
> 
> There are corners of the userspace abi that aren't but they aren't
> related to the core so we can break the abi docs in two and just move
> the good stuff...

Ok, that sounds like a good first step.

> >If so, I'll be glad to make the change to my repo so it starts to show
> >up in linux-next in the "correct" place whenever you want me to.
> 
> Will clear current queue under review then that would be great.
> 
> Note we will need to leave a lot of drivers in staging for now so move
> may require a few sed scripts to link up headers etc...  quite a lot
> of drivers are way off.

Why would some drivers stay?  It should only be because of the userspace
api, not because they don't work properly, that's never stopped drivers
from entering the main part of the kernel before :)

> Lets start a fresh thread on the move to make sure everyone agrees on
> what is ready!

Sounds good.

greg k-h
--
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/