All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Matthew Wilcox <matthew@wil.cx>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] PCI: pcie hotplug related patch
Date: Mon, 30 Jan 2012 12:42:07 +0900	[thread overview]
Message-ID: <4F26118F.7090803@jp.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQU70tBVCK-73x7kTX82XE3H03HTwP+HaS2E4_GqwMY1SQ@mail.gmail.com>

(2012/01/28 3:58), Yinghai Lu wrote:
> On Fri, Jan 27, 2012 at 10:36 AM, Jesse Barnes<jbarnes@virtuousgeek.org>  wrote:
>
>>>
>>>        git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
>>> for-pci-hp
>>
>> Ok I dropped the earlier link state check; can you re-post the series
>> with Linus's comments addressed?
>
> resent.
>
> first one patch should get Linus's Ack, but he just said that solution
> is the best so far.
>
>>
>> Kenji-san, do you have time to at least review these?  Testing would be
>> nice too...
>
> others should already address all Kenji's reviews.
>

I have a chance to test the patches in this week. I will do it and report
the result. For some patches, I don't have any environment to reproduce
the problem the patch wants to solve. So it is difficult for me to confirm
the patch fix the problem. But I will test them from the regression
point of view.

Regards,
Kenji Kaneshige

      reply	other threads:[~2012-01-30  3:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21  9:52 [PATCH 0/7] PCI: pcie hotplug related patch Yinghai Lu
2012-01-21  9:52 ` [PATCH 1/7] PCI: Make sriov work with hotplug remove Yinghai Lu
2012-01-23 16:06   ` Linus Torvalds
2012-01-23 18:30     ` Yinghai Lu
2012-01-23 18:45       ` Linus Torvalds
2012-01-23 19:34         ` Linus Torvalds
2012-01-23 19:59           ` Yinghai Lu
2012-01-23 20:48             ` Yinghai Lu
2012-01-23 22:35               ` Linus Torvalds
2012-01-24  4:34           ` Benjamin Herrenschmidt
2012-01-23 19:36         ` Yinghai Lu
2012-01-23 19:44           ` Linus Torvalds
2012-01-23 21:34             ` Yinghai Lu
2012-01-23 22:30               ` Yinghai Lu
2012-01-23 22:38                 ` Linus Torvalds
2012-01-21  9:52 ` [PATCH 2/7] PCI: Separate pci_bus_read_dev_vendor_id from pci_scan_device Yinghai Lu
2012-01-21  9:52 ` [PATCH 3/7] pciehp: Checking pci conf reading to new added device instead of sleep 1s Yinghai Lu
2012-01-21  9:52 ` [PATCH 4/7] pciehp: print out link status when dlla get active Yinghai Lu
2012-01-21  9:52 ` [PATCH 5/7] pciehp: Add pcie_wait_link_not_active() Yinghai Lu
2012-01-21  9:52 ` [PATCH 6/7] pciehp: Add Disable/enable link functions Yinghai Lu
2012-01-23 16:13   ` Linus Torvalds
2012-01-24  5:36     ` Yinghai Lu
2012-01-21  9:52 ` [PATCH 7/7] pciehp: Disable/enable link during slot power off/on Yinghai Lu
2012-01-21 10:26 ` [PATCH 0/7] PCI: pcie hotplug related patch Yinghai Lu
2012-01-27 18:36   ` Jesse Barnes
2012-01-27 18:58     ` Yinghai Lu
2012-01-30  3:42       ` Kenji Kaneshige [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=4F26118F.7090803@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.