From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: Thomas Renninger <trenn@suse•de>, Jason Baron <jbaron@redhat•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (driver-core tree related)
Date: Tue, 7 Sep 2010 17:05:53 +1000 [thread overview]
Message-ID: <20100907170553.728232dd.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100907023404.GA11972@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
Hi Greg,
On Mon, 6 Sep 2010 19:34:04 -0700 Greg KH <greg@kroah•com> wrote:
>
> Wierd, why didn't this show up yesterday? The patch was in that tree
> then, right?
It may have ... there are lots of warnings and I don't always notice new ones.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-09-07 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 1:54 linux-next: build warning after merge of the final tree (driver-core tree related) Stephen Rothwell
2010-09-07 2:34 ` Greg KH
2010-09-07 7:05 ` Stephen Rothwell [this message]
2010-09-13 15:51 ` Randy Dunlap
2010-09-13 19:26 ` Thomas Renninger
2010-09-13 20:57 ` Greg KH
2010-09-14 7:22 ` Thomas Renninger
2010-09-14 13:28 ` Greg KH
2010-09-14 4:31 ` Stephen Rothwell
2010-09-14 5:14 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 7:32 Stephen Rothwell
2013-06-06 7:59 ` Ming Lei
2013-06-19 8:00 Stephen Rothwell
2013-06-19 14:38 ` Greg KH
2013-06-20 1:34 ` Ming Lei
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=20100907170553.728232dd.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=jbaron@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=trenn@suse$(echo .)de \
/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