mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alex Chiang <achiang@hp.com>
Cc: kaneshige.kenji@jp.fujitsu.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] pciehp/shpchp prevent duplicate slot names
Date: Thu, 21 Aug 2008 15:16:59 -0700	[thread overview]
Message-ID: <200808211517.00087.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080821211137.GB24411@ldl.fc.hp.com>

On Thursday, August 21, 2008 2:11 pm Alex Chiang wrote:
> Hi Jesse,
>
> Here are patches:
>
> 	[PATCH 1/2] pciehp: Rename duplicate slot name N as N-1, N-2, N-M...
> 	[PATCH 2/2] shpchp: Rename duplicate slot name N as N-1, N-2, N-M...
>
> Against Linus's 2.6.27-rc4.
>
> As noted in the changelogs, these are temporary patches, meant as
> placeholders until I complete the longer patch series that allows
> the PCI core to manage the slot names on behalf of the drivers.
>
> The longer patch series will keep the same behavior that these
> temp patches implement, so that's goodness.
>
> These patches have already been tested and acked by Kenji-san.
>
> 	http://article.gmane.org/gmane.linux.kernel/714583
> 	http://article.gmane.org/gmane.linux.kernel/714582
>
> So I think you can add his sign-offs too.

Excellent, thanks Alex & Kenji-san.  I applied this to my for-linus branch.  
I'll have Linus pull it soon.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2008-08-21 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 21:11 Alex Chiang
2008-08-21 21:13 ` [PATCH 1/2] pciehp: Rename duplicate slot name N as N-1, N-2, N-M Alex Chiang
2008-08-21 21:13 ` [PATCH 2/2] shpchp: " Alex Chiang
2008-08-21 22:16 ` Jesse Barnes [this message]

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=200808211517.00087.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=achiang@hp.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --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

Powered by JetHome