From: Andi Kleen <andi@firstfloor.org>
To: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Nathan Lynch <ntl@pobox.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Removing sysdevs?
Date: Thu, 03 Jul 2008 11:53:14 +0200 [thread overview]
Message-ID: <486CA18A.2040604@firstfloor.org> (raw)
In-Reply-To: <20080702221517.GA17929@kroah.com>
> The patches look fine, do you want me to take them through my tree, or
> do you want to have them go through somewhere else as you have some
> dependancies on them?
Through your tree is fine. Thanks.
Perhaps drop the x86 dynamic bank patch, it would actually conflict
with one patch currently in the x86 tree and doesn't really
belong into your tree.
>
> If somewhere else, that's fine with me, feel free to add:
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> to them.
-Andi
next prev parent reply other threads:[~2008-07-03 12:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 6:27 Is sysfs the right place to get cache and CPU topology info? Paul Mackerras
2008-07-02 7:37 ` Andrew Morton
2008-07-02 9:45 ` Paul Mackerras
2008-07-02 10:01 ` Andrew Morton
2008-07-02 11:46 ` Paul Mackerras
2008-07-02 16:47 ` Andrew Morton
2008-07-02 11:12 ` Andi Kleen
2008-07-02 14:35 ` Nathan Lynch
2008-07-02 15:14 ` Andi Kleen
2008-07-02 18:51 ` Greg KH
2008-07-02 21:41 ` Removing sysdevs? (was: Re: Is sysfs the right place to get cache and CPU topology info?) Rafael J. Wysocki
2008-07-02 21:48 ` Greg KH
2008-07-02 21:57 ` Removing sysdevs? Andi Kleen
2008-07-02 22:15 ` Greg KH
2008-07-03 9:53 ` Andi Kleen [this message]
2008-07-04 1:09 ` Greg KH
2008-07-02 22:17 ` Benjamin Herrenschmidt
2008-07-02 22:08 ` Removing sysdevs? (was: Re: Is sysfs the right place to get cache and CPU topology info?) Rafael J. Wysocki
2008-07-02 22:16 ` Greg KH
2008-07-02 23:06 ` Rafael J. Wysocki
2008-07-02 17:08 ` [PATCH] sysfs-rules.txt: reword API stability statement Nathan Lynch
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=486CA18A.2040604@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
/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