From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: build failure after merge of the final tree (pci tree related)
Date: Mon, 12 Dec 2011 12:53:09 -0800 [thread overview]
Message-ID: <20111212125309.54a47973@jbarnes-desktop> (raw)
In-Reply-To: <0207C53569FE594381A4F2EB66570B2A018EFB78F3@orsmsx508.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On Fri, 9 Dec 2011 12:02:48 -0800
"Luck, Tony" <tony.luck@intel.com> wrote:
> > Sigh, I'm sorry. Attached are the incremental patch to fix this, and
> > an updated version of the original patch. I'm not git-smart enough to
> > push it this time (the box where I normally do that is down at the
> > moment, along with my notes).
>
> Bjorn,
>
> Thanks - the incremental patch works great.
Thanks, just applied it (by hand) to the linux-next branch. Hopefully
I didn't botch it...
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-12 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 6:05 linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell
2011-12-07 15:08 ` Bjorn Helgaas
2011-12-07 15:25 ` Bjorn Helgaas
2011-12-07 17:13 ` Jesse Barnes
2011-12-07 20:24 ` Stephen Rothwell
2011-12-08 19:01 ` Tony Luck
2011-12-09 3:53 ` Bjorn Helgaas
2011-12-09 20:02 ` Luck, Tony
2011-12-12 20:53 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-12 4:54 Stephen Rothwell
2012-06-12 15:31 ` Bjorn Helgaas
2012-06-13 0:50 ` Stephen Rothwell
2012-06-13 23:20 ` Bjorn Helgaas
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=20111212125309.54a47973@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
/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