From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 09/17] pcmcia: update gfp/slab.h includes
Date: Tue, 30 Mar 2010 10:01:47 +0900 [thread overview]
Message-ID: <4BB14D7B.4010602@kernel.org> (raw)
In-Reply-To: <20100330103129.b76a70e3.sfr@canb.auug.org.au>
Hello,
On 03/30/2010 08:31 AM, Stephen Rothwell wrote:
> Hi Dominik,
> On Mon, 29 Mar 2010 21:32:03 +0200 Dominik Brodowski <linux@dominikbrodowski.net> wrote:
>>
>> On Tue, Mar 30, 2010 at 02:52:37AM +0900, Tejun Heo wrote:
>>> Implicit slab.h inclusion via percpu.h is about to go away. Make sure
>>> gfp.h or slab.h is included as necessary.
>>>
>>> Signed-off-by: Tejun Heo <tj@kernel.org>
>>> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
>>> Cc: Dominik Brodowski <linux@dominikbrodowski.net>
>> Acked-by: Dominik Brodowski <linux@dominikbrodowski.net>
>
> The plan here is for you to put this in your tree now. It is safe to do
> so and Tejun can't carry it because this does not apply to mainline.
Yeap, something I completely forgot about when I asked Stephen to pull
from the slabh tree. It would be great if you can apply this one and
Stephen's patches on drivers/input/misc/ad714x.c and pcf8574_keypad.c
into input tree.
Thank you.
--
tejun
next prev parent reply other threads:[~2010-03-30 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1269885165-18617-1-git-send-email-tj@kernel.org>
[not found] ` <1269885165-18617-10-git-send-email-tj@kernel.org>
2010-03-29 19:32 ` [PATCH 09/17] pcmcia: update gfp/slab.h includes Dominik Brodowski
2010-03-29 23:31 ` Stephen Rothwell
2010-03-30 1:01 ` Tejun Heo [this message]
2010-03-30 6:36 ` Dominik Brodowski
2010-03-30 6:56 ` Dmitry Torokhov
2010-03-30 8:22 ` Stephen Rothwell
[not found] ` <20100330065605.GA12764@core.coreip.homeip.net>
2010-03-30 8:23 ` Stephen Rothwell
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=4BB14D7B.4010602@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).