From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
Cc: Brian King <brking@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] Fixes for PCI-E link speed
Date: Fri, 31 Jan 2014 23:29:21 +1100 [thread overview]
Message-ID: <1391171361.27142.6.camel@pasglop> (raw)
In-Reply-To: <52EB94F6.6000800@linux.vnet.ibm.com>
On Fri, 2014-01-31 at 10:20 -0200, Kleber Sacilotto de Souza wrote:
> On 01/17/2014 11:56 AM, Kleber Sacilotto de Souza wrote:
> > These two patches fix problems on the PCI-E link speed detection.
> > The first one fixes a regression and adds some improvements on the
> > code, and the second one adds definitions for Gen3 speeds.
> >
> > Kleber Sacilotto de Souza (2):
> > powerpc/pseries: fix regression on PCI link speed
> > powerpc/pseries: add Gen3 definitions for PCIE link speed
> >
> > arch/powerpc/platforms/pseries/pci.c | 22 +++++++++++++++-------
> > 1 files changed, 15 insertions(+), 7 deletions(-)
> >
>
> Hi,
>
> Any feedback on this patch series?
Patches on this list are tracked in patchwork so are generally not
"lost". Plus I was on vacation last week. So there's no need for such
pings unless much more time has elapsed. I'll probably put it in after
-rc1.
Ben.
prev parent reply other threads:[~2014-01-31 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 13:56 [PATCH 0/2] Fixes for PCI-E link speed Kleber Sacilotto de Souza
2014-01-17 13:56 ` [PATCH 1/2] powerpc/pseries: fix regression on PCI " Kleber Sacilotto de Souza
2014-01-17 13:56 ` [PATCH 2/2] powerpc/pseries: add Gen3 definitions for PCIE " Kleber Sacilotto de Souza
2014-01-31 12:20 ` [PATCH 0/2] Fixes for PCI-E " Kleber Sacilotto de Souza
2014-01-31 12:29 ` Benjamin Herrenschmidt [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=1391171361.27142.6.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=brking@linux.vnet.ibm.com \
--cc=klebers@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).