All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 14 Dec 2011 14:44:20 -0800	[thread overview]
Message-ID: <20111214224420.GA10610@kroah.com> (raw)
In-Reply-To: <CAPXgP10ZVjy00H3g1YbGJz+e0=mP9hXfdeDT8pOLrDE-e5E5_A@mail.gmail.com>

On Wed, Dec 14, 2011 at 03:11:34AM +0100, Kay Sievers wrote:
> On Wed, Dec 14, 2011 at 02:21, Greg KH <greg@kroah.com> wrote:
> > 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?
> 
> The first patch should not break anything, the non-core things
> shouldn't too.

Nice, I've applied the first patch to my tree and pushed it out and I'll
read over the rest now.

> > Or will the cpu ones?
> 
> The cpu patch as it is will break power, s390, sh and tile.
>   $ git grep -w -l cpu_sysdev_class
>   arch/powerpc/kernel/sysfs.c
>   arch/powerpc/platforms/pseries/pseries_energy.c
>   arch/s390/kernel/smp.c
>   arch/sh/kernel/cpu/sh4/sq.c
>   arch/tile/kernel/sysfs.c
> 
> If all should be bisectable, we would need to merge these changes into
> the cpu patch.

Yeah, we need to do that, I'll look at it.

> The other two core patches, node and memory, could need arch fixes
> too, but a quick grep did not reveal anything.

Ok, we might be safe there, I'll look at them.

thanks,

greg k-h

  reply	other threads:[~2011-12-14 22:47 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
2011-12-14  2:11             ` Kay Sievers
2011-12-14 22:44               ` Greg KH [this message]
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=20111214224420.GA10610@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.