From: Jon Masters <jcm@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: David Daney <ddaney@caviumnetworks.com>,
Auger Eric <eric.auger@redhat.com>,
David Daney <david.daney@cavium.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
Robert Richter <robert.richter@cavium.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] PCI: Avoid bus reset for Cavium cn8xxx root ports.
Date: Wed, 17 May 2017 10:04:06 -0400 (EDT) [thread overview]
Message-ID: <925EB284-D73A-44A4-AAEB-C086041C5A3E@redhat.com> (raw)
In-Reply-To: <1495004825.31562.20.camel@perches.com>
Hahahahahaha :)
--
Computer Architect | Sent from my 64-bit #ARM Powered phone
> On May 17, 2017, at 03:08, Joe Perches <joe@perches.com> wrote:
>
>> On Tue, 2017-05-16 at 13:29 -0700, David Daney wrote:
>> We really need to improve the
>> grammatical analysis capabilities of checkpatch.pl, I think I will lay
>> the blame there.
>
> Uh huh. Best of luck. Submit a patch...
>
> ;)
>
next prev parent reply other threads:[~2017-05-17 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 0:17 [PATCH 0/2] PCI: Workaround for bus reset on " David Daney
2017-05-16 0:17 ` [PATCH 1/2] PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device David Daney
2017-05-16 20:14 ` Auger Eric
2017-05-16 0:17 ` [PATCH 2/2] PCI: Avoid bus reset for Cavium cn8xxx root ports David Daney
2017-05-16 20:14 ` Auger Eric
2017-05-16 20:29 ` David Daney
2017-05-16 20:48 ` Alex Williamson
2017-05-17 7:07 ` Joe Perches
2017-05-17 14:04 ` Jon Masters [this message]
2017-05-16 20:14 ` [PATCH 0/2] PCI: Workaround for bus reset on " Auger Eric
2017-05-23 20:47 ` Bjorn Helgaas
2017-05-23 21:04 ` Alex Williamson
2017-05-23 21:20 ` Bjorn Helgaas
2017-05-23 21:22 ` David Daney
2017-05-23 22:15 ` Alex Williamson
2017-05-30 3:30 ` Jon Masters
2017-05-30 17:32 ` Alex Williamson
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=925EB284-D73A-44A4-AAEB-C086041C5A3E@redhat.com \
--to=jcm@redhat.com \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=eric.auger@redhat.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robert.richter@cavium.com \
/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
all inboxes | Powered by JetHome®