From: Bjorn Helgaas <bhelgaas@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next list <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the pci tree
Date: Tue, 3 Sep 2013 17:59:48 -0600 [thread overview]
Message-ID: <CAErSpo7m77dD4zic5nn-KaaTwJyvDPtpr2pbGy6i6Tf6N5dt0Q@mail.gmail.com> (raw)
In-Reply-To: <20130904095527.d5e694435fd03a5252de0d42@canb.auug.org.au>
On Tue, Sep 3, 2013 at 5:55 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Bjorn,
>
> You have sent a pull request to Linus for the pci tree, but at the same
> time you have reset the branch I pull into linux-next to be v3.11. So
> you have effectively removed all that code from linux-next until Linus'
> merges it :-(
>
> Ordering is important.
Oops, sorry about that!. I jumped the gun because I forgot about your
dependency on that branch (stupid, I know, since that's the whole
point of it). Next time I'll wait until after Linus pulls my tag.
Bjorn
next prev parent reply other threads:[~2013-09-04 0:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 23:55 linux-next: build warning after merge of the pci tree Stephen Rothwell
2013-09-03 23:59 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 2:38 Stephen Rothwell
2020-09-15 3:43 ` Stephen Rothwell
2020-09-09 2:37 Stephen Rothwell
2020-09-09 16:06 ` Rob Herring
2020-09-15 3:47 ` Stephen Rothwell
2020-09-15 10:53 ` Lorenzo Pieralisi
2020-09-15 17:22 ` Bjorn Helgaas
2020-09-02 1:07 Stephen Rothwell
2020-09-02 12:33 ` Bjorn Helgaas
2020-09-02 14:13 ` Vaibhav Gupta
2020-08-05 1:32 Stephen Rothwell
2020-08-05 2:29 ` Bjorn Helgaas
2016-06-23 1:51 Stephen Rothwell
2016-06-23 16:48 ` Bjorn Helgaas
2016-06-24 8:07 ` Johannes Thumshirn
2012-12-10 9:03 Stephen Rothwell
2012-12-10 21:25 ` Bjorn Helgaas
2012-12-10 23:21 ` Bjorn Helgaas
2012-05-01 6:08 Stephen Rothwell
2012-05-01 7:35 ` Yinghai Lu
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=CAErSpo7m77dD4zic5nn-KaaTwJyvDPtpr2pbGy6i6Tf6N5dt0Q@mail.gmail.com \
--to=bhelgaas@google.com \
--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;
as well as URLs for NNTP newsgroup(s).