From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org, ak@linux.intel.com, trenn@suse.de,
davej@redhat.com
Subject: Re: [PATCH-WIP] convert CPU sysdev class to a real subsytem (needed for CPU modaliases)
Date: Tue, 13 Dec 2011 17:21:41 -0800 [thread overview]
Message-ID: <20111214012141.GA18215@kroah.com> (raw)
In-Reply-To: <CAPXgP11fwJ=9E-K4ZpZ-nhf-Ry9=+oX4r7F1mLchxLMmvj_8ZA@mail.gmail.com>
On Wed, Dec 14, 2011 at 01:50:57AM +0100, Kay Sievers wrote:
> On Fri, Dec 9, 2011 at 23:34, Greg KH <greg@kroah.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
next prev parent reply other threads:[~2011-12-14 1:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 1:58 [PATCH-WIP] convert CPU sysdev class to a real subsytem (needed for CPU modaliases) Kay Sievers
2011-12-08 15:10 ` Andi Kleen
2011-12-09 0:11 ` Greg KH
2011-12-09 4:20 ` Kay Sievers
2011-12-09 15:25 ` Kay Sievers
2011-12-09 22:34 ` Greg KH
2011-12-14 0:50 ` Kay Sievers
2011-12-14 1:21 ` Greg KH [this message]
2011-12-14 2:11 ` Kay Sievers
2011-12-14 22:44 ` Greg KH
2011-12-15 3:09 ` Greg KH
2011-12-20 22:43 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111214012141.GA18215@kroah.com \
--to=greg@kroah.com \
--cc=ak@linux.intel.com \
--cc=davej@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox