From: Paul Mundt <lethal@linux-sh.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: suspend tree build failure
Date: Wed, 19 Aug 2009 07:47:49 +0900 [thread overview]
Message-ID: <20090818224749.GA26661@linux-sh.org> (raw)
In-Reply-To: <200908190040.50949.rjw@sisk.pl>
On Wed, Aug 19, 2009 at 12:40:50AM +0200, Rafael J. Wysocki wrote:
> On Wednesday 19 August 2009, Paul Mundt wrote:
> > Argh, and rebased in the process, again. This is now the second time in
> > as many days this has been rebased, meaning I have to throw away my topic
> > branch and re-create. I thought this was going to remain stable? I would
> > like the SH runtime PM code to get some coverage in -next, but I can't
> > merge it in to my tree if the suspend tree keeps rebasing every day.
>
> Well, my linux-next branch is not to guaranteed to be stable, just like the
> entire linux-next tree.
>
> Once the patch stops making trouble, I'll move it into my for-linus branch,
> which _is_ guaranteed not to be rebased (in fact it's never rebased).
>
> I haven't done it yet exactly because of these build problems. Please wait
> for a couple of days more for things to settle down.
>
Ah, ok, I misunderstood the intention of your -next branch. I'll wait for
it to cool off, thanks. ;-)
next prev parent reply other threads:[~2009-08-18 22:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 8:30 linux-next: suspend tree build failure Stephen Rothwell
2009-08-18 21:43 ` Rafael J. Wysocki
2009-08-18 22:13 ` Paul Mundt
2009-08-18 22:40 ` Rafael J. Wysocki
2009-08-18 22:47 ` Paul Mundt [this message]
2009-08-18 23:57 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 3:00 Stephen Rothwell
2009-10-12 22:44 ` Rafael J. Wysocki
2009-10-13 0:58 ` Stephen Rothwell
2009-10-08 4:30 Stephen Rothwell
2009-10-06 2:55 Stephen Rothwell
2009-10-06 22:31 ` Rafael J. Wysocki
2009-10-07 4:29 ` Stephen Rothwell
2009-10-07 20:41 ` Rafael J. Wysocki
2009-10-07 23:48 ` Stephen Rothwell
2009-10-05 5:00 Stephen Rothwell
2009-10-05 23:55 ` Rafael J. Wysocki
2009-10-06 2:39 ` Stephen Rothwell
2009-08-17 8:40 Stephen Rothwell
2009-08-17 12:06 ` Rafael J. Wysocki
2009-03-16 9:13 Stephen Rothwell
2009-03-16 22:07 ` Rafael J. Wysocki
2009-03-16 23:09 ` 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=20090818224749.GA26661@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 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.