From: Logan Gunthorpe <logang@deltatee.com>
To: Jonathan Corbet <corbet@lwn.net>, Wesley Sheng <wesleyshenggit@sina.com>
Cc: kurt.schwemmer@microsemi.com, linux-pci@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bhelgaas@google.com, linux-ntb@googlegroups.com,
Wesley Yung <wesley.yung@microchip.com>,
Kelvin Cao <kelvin.cao@microchip.com>
Subject: Re: [PATCH v3] NTB: switchtec_ntb: Update switchtec documentation with pre-requisites for NTB
Date: Fri, 12 Oct 2018 11:54:11 -0600 [thread overview]
Message-ID: <f6dbcdc1-b1e1-98e8-fbcb-73fc6f92ce67@deltatee.com> (raw)
In-Reply-To: <20181012113040.52bfff58@lwn.net>
On 2018-10-12 11:30 a.m., Jonathan Corbet wrote:
> On Wed, 10 Oct 2018 20:33:08 +0800
> Wesley Sheng <wesleyshenggit@sina.com> wrote:
>
>> The ntb_hw_switchtec driver has requirements on kernel configuration
>> so we add these notes to the documentation and also clean up a few
>> other sentences in the documentation.
>>
>> Signed-off-by: Wesley Yung <wesley.yung@microchip.com>
>> Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
>> Signed-off-by: Wesley Sheng <wesleyshenggit@sina.com>
>
> So why all of these signoffs for such a small patch? Who is the actual
> author of the patch?
It was originally two very small patches from Mr. Yung[1] and Mr. Cao[2]
combined and then cleaned up for upstream by Mr. Sheng.
There will likely be a bit more of this as they intend on upstreaming
more of the work that has been done out-of-tree. I believe most of this
is minor bug fixes and small feature additions.
Logan
[1]
https://github.com/Microsemi/switchtec-kernel/commit/5e7e7709c8ce6f37163113a8b6282aa4a788b6a0
[2]
https://github.com/Microsemi/switchtec-kernel/commit/e25fbb7267a742d08ca0802e0a6886c183e8b7b4
next prev parent reply other threads:[~2018-10-12 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539174788-25878-1-git-send-email-wesleyshenggit@sina.com>
2018-10-12 17:30 ` Jonathan Corbet
2018-10-12 17:54 ` Logan Gunthorpe [this message]
2018-10-10 14:42 Wesley Sheng
2018-10-10 15:58 ` Logan Gunthorpe
2018-10-11 16:27 ` Bjorn Helgaas
2018-10-11 16:36 ` Logan Gunthorpe
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=f6dbcdc1-b1e1-98e8-fbcb-73fc6f92ce67@deltatee.com \
--to=logang@deltatee.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=kelvin.cao@microchip.com \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
--cc=wesley.yung@microchip.com \
--cc=wesleyshenggit@sina.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®