[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111214012141.GA18215@kroah.com>
Date: Tue, 13 Dec 2011 17:21:41 -0800
From: Greg KH <greg@...ah.com>
To: Kay Sievers <kay.sievers@...y.org>
Cc: linux-kernel@...r.kernel.org, ak@...ux.intel.com, trenn@...e.de,
davej@...hat.com
Subject: Re: [PATCH-WIP] convert CPU sysdev class to a real subsytem (needed
for CPU modaliases)
On Wed, Dec 14, 2011 at 01:50:57AM +0100, Kay Sievers wrote:
> On Fri, Dec 9, 2011 at 23:34, Greg KH <greg@...ah.com> wrote:
> > On Fri, Dec 09, 2011 at 04:25:21PM +0100, Kay Sievers wrote:
> >> Greg, would be nice, if you can take a quick look a the driver core (not
> >> the sysdev) bits in core.c, bus.c, device.h, ... and its interaction, if
> >> they look sane to you. I'll then split the driver core stuff out, so we
> >> can merge that before we port the individual drivers over.
> >
> > Yes, it looks sane to me, thanks again for doing this work.
>
> Split-up patches are here:
> http://git.kernel.org/?p=linux/kernel/git/kay/patches.git;a=tree
>
> That's the size of it:
> 60 files changed, 1170 insertions(+), 1421 deletions(-)
Very nice.
> The current state and the list of the remaining non-x86 files is here:
> http://git.kernel.org/?p=linux/kernel/git/kay/patches.git;a=blob;f=README;hb=HEAD
>
> We need a plan now. :)
If I take those patches, none of those other ones will break their
build, right? Or will the cpu ones?
I'll look at this tomorrow, gotta go now, I'm burnt out by badly written
staging patches that must have been created by someone who is bent on
driving me crazy.
thanks so much for doing this.
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/
Powered by blists - more mailing lists