All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wim ten Have <wim.ten.have@oracle.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Wim ten Have <wim.ten.have@oracle.com>
Subject: Re: Red Hat (Fedora) bug report 1467674 concerning your kernel functional performance enhancements causing PCI Express crashes,
Date: Wed, 5 Jul 2017 15:00:06 +0200	[thread overview]
Message-ID: <20170705150006.7f6a3c44.wim.ten.have@oracle.com> (raw)
In-Reply-To: <c350ebc3-51cf-d2d7-e40c-740360f1dc4d@codeaurora.org>

On Wed, 5 Jul 2017 08:37:03 -0400
Sinan Kaya <okaya@codeaurora.org> wrote:

> On 7/5/2017 7:13 AM, Wim ten Have wrote:
> >  From an 'rpmbuild -ba kernel.spec' nicely proceeded and generated all
> >   package.  They all installed and the system boots and works like a charm!  
> 
> Thanks for testing. I'll re-post the same patch with better commit text
> and fixes tag so that Bjorn can review it.
> 
> Can I have a tested-by?

  Sure.

  tested-by: Wim ten Have <wim.ten.have@oracle.com>

- Wim.

  reply	other threads:[~2017-07-05 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170704161352.1cdb2670.wim.ten.have@oracle.com>
2017-07-04 15:32 ` Fwd: Red Hat (Fedora) bug report 1467674 concerning your kernel functional performance enhancements causing PCI Express crashes, Bjorn Helgaas
2017-07-04 15:57   ` Sinan Kaya
2017-07-04 17:59     ` Wim ten Have
2017-07-04 22:25       ` Sinan Kaya
2017-07-05  1:00         ` Sinan Kaya
2017-07-05  7:42           ` Ethan Zhao
2017-07-05 12:28             ` Sinan Kaya
2017-07-05 11:13           ` Wim ten Have
2017-07-05 12:37             ` Sinan Kaya
2017-07-05 13:00               ` Wim ten Have [this message]
2017-07-05 13:20                 ` Sinan Kaya

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=20170705150006.7f6a3c44.wim.ten.have@oracle.com \
    --to=wim.ten.have@oracle.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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.