From: Herbert Xu <herbert@gondor•apana.org.au>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Mathias Krause <minipli@googlemail•com>
Subject: Re: linux-next: build warning after merge of the final tree
Date: Tue, 16 Aug 2011 15:08:44 +0800 [thread overview]
Message-ID: <20110816070844.GA7339@gondor.apana.org.au> (raw)
In-Reply-To: <20110816170311.78935e0cae3d6c3f5955e1c0@canb.auug.org.au>
On Tue, Aug 16, 2011 at 05:03:11PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> On Tue, 16 Aug 2011 14:04:10 +0800 Herbert Xu <herbert@gondor•apana.org.au> wrote:
> >
> > Does this patch fix the problem?
>
> Yes, it does.
>
> Tested-by: Stephen Rothwell <sfr@canb•auug.org.au>
Thanks for checking!
--
Email: Herbert Xu <herbert@gondor•apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2011-08-16 7:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 5:22 linux-next: build warning after merge of the final tree Stephen Rothwell
2011-08-16 6:04 ` Herbert Xu
2011-08-16 7:03 ` Stephen Rothwell
2011-08-16 7:08 ` Herbert Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 5:29 Stephen Rothwell
2013-05-29 5:44 ` David Miller
2013-04-19 8:07 Stephen Rothwell
2013-04-19 9:44 ` Joerg Roedel
2012-12-17 3:22 Stephen Rothwell
2012-12-17 3:34 ` Stephen Rothwell
2012-12-17 20:59 ` Andrew Morton
2012-08-02 4:04 Stephen Rothwell
2012-08-02 14:45 ` Nathan Zimmer
2012-03-26 4:11 Stephen Rothwell
2012-03-28 7:59 ` Williams, Dan J
2011-07-22 6:24 Stephen Rothwell
2011-07-22 6:26 ` David Miller
2010-09-29 4:02 Stephen Rothwell
2010-09-16 5:05 Stephen Rothwell
2010-09-16 6:29 ` Jens Axboe
2010-05-26 5:15 Stephen Rothwell
2010-03-01 8:14 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=20110816070844.GA7339@gondor.apana.org.au \
--to=herbert@gondor$(echo .)apana.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=minipli@googlemail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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