From: Jesse Barnes <jbarnes@virtuousgeek•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org,
Vincent Legoll <vincent.legoll@gmail•com>,
Sitsofe Wheeler <sitsofe@yahoo•com>
Subject: Re: linux-next: manual merge of the pci tree
Date: Thu, 16 Oct 2008 05:32:30 -0700 [thread overview]
Message-ID: <200810160532.30691.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081016142418.c94967d8.sfr@canb.auug.org.au>
On Wednesday, October 15, 2008 8:24 pm Stephen Rothwell wrote:
> Hi Jesse,
>
> Today's linux-next merge of the pci tree got a conflict in
> drivers/pci/pcie/aspm.c between commit
> e1f4f59d1ab9ebac44830d6ae450fb358ac559d3 ("PCI: Fix pcie_aspm=force")
> from Linus' tree and commit 4f56ffe4ff214284f9c92037f9ad5f389a74bb84
> ("PCI: probing debug message uniformization") from the pci tree.
>
> Just context. I fixed it up (see below).
Yeah I sent that fix to Linus but it's not in my linux-next tree. Looks like
I'll have to do some re-basing to fix up Ben's PPC legacy stuff so I can take
care of it then.
Jesse
next prev parent reply other threads:[~2008-10-16 12:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 3:24 linux-next: manual merge of the pci tree Stephen Rothwell
2008-10-16 12:32 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-19 22:40 Stephen Rothwell
2009-01-06 0:54 Stephen Rothwell
2008-12-11 0:53 Stephen Rothwell
2008-10-20 4:00 Stephen Rothwell
2008-10-20 18:36 ` Jesse Barnes
2008-07-08 1:13 Stephen Rothwell
2008-07-03 2:10 Stephen Rothwell
2008-07-03 2:15 ` Stephen Rothwell
2008-07-03 3:28 ` Greg KH
2008-07-03 19:23 ` Jesse Barnes
2008-07-04 0:09 ` Stephen Rothwell
2008-07-04 0:13 ` Jesse Barnes
2008-07-04 0:14 ` Stephen Rothwell
2008-07-01 3:53 Stephen Rothwell
2008-07-01 5:58 ` Ingo Molnar
2008-07-01 6:29 ` Stephen Rothwell
2008-07-02 1:56 ` Jesse Barnes
2008-07-02 2:09 ` Yinghai Lu
2008-07-02 3:19 ` Stephen Rothwell
2008-06-25 3:01 Stephen Rothwell
2008-06-25 19:28 ` Jesse Barnes
2008-06-25 2:57 Stephen Rothwell
2008-06-25 19:27 ` Jesse Barnes
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=200810160532.30691.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sitsofe@yahoo$(echo .)com \
--cc=vincent.legoll@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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