All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: cpufreq tree build failure
Date: Thu, 5 Feb 2009 16:34:51 -0500	[thread overview]
Message-ID: <20090205213451.GA14664@redhat.com> (raw)
In-Reply-To: <200902052157.45344.trenn@suse.de>

On Thu, Feb 05, 2009 at 09:57:44PM +0100, Thomas Renninger wrote:

 > > I added the 'static's directly to the patches, and regenerated the tree
 > > on kernel.org
 > > For other stuff, unless it's a build-fix, send an incremental diff ?
 > Yes, will do so.
 > But if possible, I'd like to wait for Ingo's
 > printk_once function popping up in linux-next.
 > How frequently are linux-next patches pulled back into the cpufreq tree?

There's no regular schedule. It typically happens if a) they get merged into
Linus tree, and b) I rebase the cpufreq tree (which I try to avoid where possible,
I try to only do it to get around a build failure, or if there's massive
conflicts with something else that got merged).

 > Anyway, I am going to look at your tree in a week or two and send
 > something then. It's only about a cleaned up message in broken BIOS case,
 > that should not hurt in linux-next for a while.

Sounds good to me.

Thanks,

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2009-02-05 21:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05  7:54 linux-next: cpufreq tree build failure Stephen Rothwell
2009-02-05  9:33 ` Thomas Renninger
2009-02-05  9:47 ` Thomas Renninger
2009-02-05 17:45   ` Dave Jones
2009-02-05 20:57     ` Thomas Renninger
2009-02-05 21:34       ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-03  2:28 Stephen Rothwell
2009-08-03 23:22 ` Thomas Renninger
2009-08-03 23:44   ` Dave Jones
2009-02-24  6:21 Stephen Rothwell
2009-02-24 16:51 ` Dave Jones
2009-02-25  3:29   ` Stephen Rothwell
2009-02-25  3:45     ` Dave Jones
2009-02-25  4:23       ` Stephen Rothwell
2009-01-20  2:50 Stephen Rothwell
2009-01-20  5:30 ` Dave Jones
2009-01-20  6: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=20090205213451.GA14664@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=trenn@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.