From: Jens Axboe <jaxboe@fusionio.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: linux-next: build warning after merge of the moduleh tree
Date: Tue, 2 Aug 2011 10:42:11 +0200 [thread overview]
Message-ID: <4E37B863.4080700@fusionio.com> (raw)
In-Reply-To: <20110802183558.fda9e3b1e9f3b93a70f6e494@canb.auug.org.au>
On 2011-08-02 10:35, Stephen Rothwell wrote:
> Hi Jens,
>
> On Tue, 2 Aug 2011 09:26:14 +0200 Jens Axboe <jaxboe@fusionio.com> wrote:
>>
>> Thanks, will you carry this until things are merged? Not easy for me to
>> fix up.
>
> Yes, no problem. It is possible that the module.h split may not even go
> into v3.1, in which case the fix patch will jst become part of the moduleh
> tree after the block tree is merged.
>
> Though the feedback to the original patch writer is that they should have
> included module.h instead of relying on it being implicitly included.
That would arguably have been a much saner approach.
> You could include a patch to add an include of module.h to this file in
> your tree - that way even if the module.h split goes ahead, your tree
> won't get broken. It could then be changed to the lighter weight
> export.h later.
OK, I will add that. Thanks.
--
Jens Axboe
next prev parent reply other threads:[~2011-08-02 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 3:23 linux-next: build warning after merge of the moduleh tree Stephen Rothwell
2011-08-02 7:26 ` Jens Axboe
2011-08-02 8:35 ` Stephen Rothwell
2011-08-02 8:42 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-18 5:09 Stephen Rothwell
2011-08-18 8:26 ` Rafael J. Wysocki
2011-08-18 9:27 ` Stephen Rothwell
2011-08-18 20:57 ` Rafael J. Wysocki
2011-09-28 7:18 Stephen Rothwell
2011-09-28 7:39 ` Pihet-XID, Jean
2011-10-11 9:21 Stephen Rothwell
2011-10-11 13:16 ` Paul Gortmaker
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=4E37B863.4080700@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=paul.gortmaker@windriver.com \
--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).