From: ebiederm@xmission.com (Eric W. Biederman)
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pcie_portdriver: FIX: pcie_port_device_remove
Date: Thu, 19 Feb 2009 15:30:39 -0800 [thread overview]
Message-ID: <m13aeaxaw0.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <200902192247.46370.rjw@sisk.pl> (Rafael J. Wysocki's message of "Thu\, 19 Feb 2009 22\:47\:45 +0100")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Thursday 19 February 2009, Eric W. Biederman wrote:
>> Andrew Morton <akpm@linux-foundation.org> writes:
>>
>> >
>> > There are large-scale and conflicting changes to this file in linux-next.
>> >
>> > If we want to jam this fix into 2.6.29 (and it looks like something we
>> > want) then this will trash the linux-next changes. It will cause me
>> > grief, and will cause Stephen grief unless the pci tree is suitably
>> > changed, which will cause Jesse grief. Either way: grief.
>>
>> Ugh.
>>
>> I had better have a good hard look at linux-next. I tried to ask earlier
> about
>> ongoing working but I didn't hear anything.
>
> Yes, you did: http://marc.info/?l=linux-kernel&m=123342565225134&w=4
My apologies. I should have said I did not recognize anything that
was likely to conflict from what I hear from what I heard. I did
hear that the pcie port driver was touched to properly handle msi-x and I
foolishly thought that was already merged upstream. Especially after
I glanced at Jesse's tree and I did not see any recent pci patches.
Which led me to foolishly assume everything had already been merged
into Linus's tree.
Andrew with respect to 2.6.29 my patch while correct and useful has
no immediate utility, as the pciehp driver will crash and burn horribly
if you attempt to hotplug it. So I should find the other pci port driver
changes and rebase on top of them. Assuming that patch is scheduled to
merge for 2.6.30.
Eric
next prev parent reply other threads:[~2009-02-19 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 4:23 [PATCH] pcie_portdriver: FIX: pcie_port_device_remove Eric W. Biederman
2009-02-19 20:03 ` Andrew Morton
2009-02-19 20:55 ` Eric W. Biederman
2009-02-19 21:47 ` Rafael J. Wysocki
2009-02-19 23:30 ` Eric W. Biederman [this message]
2009-02-19 23:53 ` Jesse Barnes
2009-02-20 10:53 ` Rafael J. Wysocki
2009-02-21 4:16 ` [PATCH] pcie_portdriver: FIX: pcie_port_device_remove (take 2) Eric W. Biederman
2009-02-24 19:12 ` Jesse Barnes
2009-02-25 4:22 ` Eric W. Biederman
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=m13aeaxaw0.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
/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