From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kurt Roeckx <kurt@roeckx.be>
Subject: Re: linux-next: cpufreq-current tree build warning
Date: Wed, 16 Sep 2009 23:17:59 -0400 [thread overview]
Message-ID: <20090917031759.GB30706@redhat.com> (raw)
In-Reply-To: <20090917125556.1125d8ae.sfr@canb.auug.org.au>
On Thu, Sep 17, 2009 at 12:55:56PM +1000, Stephen Rothwell wrote:
> so, no.
> (origin/master is Linus' tree of about 2 hours ago, commit
> ab86e5765d41a5eb4239a1c04d613db87bea5ed8 "Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6")
>
> Looking further, this is the cpureq-current tree I am complaining about,
> in the cpufreq tree, you also have:
Oh, from the 'fixes' branch ? Just drop that for now, and only pick up 'next'
(though next pull request went to linus today, so the whole thing should be
gone soon).
Dave
prev parent reply other threads:[~2009-09-17 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 2:06 linux-next: cpufreq-current tree build warning Stephen Rothwell
2009-09-17 2:27 ` Dave Jones
2009-09-17 2:55 ` Stephen Rothwell
2009-09-17 3:17 ` Dave Jones [this message]
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=20090917031759.GB30706@redhat.com \
--to=davej@redhat.com \
--cc=kurt@roeckx.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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