public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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 12:55:37 -0800	[thread overview]
Message-ID: <m163j61706.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20090219120333.af992d9e.akpm@linux-foundation.org> (Andrew Morton's message of "Thu\, 19 Feb 2009 12\:03\:33 -0800")

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.

Eric


  reply	other threads:[~2009-02-19 20:55 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 [this message]
2009-02-19 21:47     ` Rafael J. Wysocki
2009-02-19 23:30       ` Eric W. Biederman
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=m163j61706.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 \
    /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