From: Jens Axboe <axboe@kernel.dk>
To: Jinpu Wang <jinpu.wang@cloud.ionos.com>
Cc: Danil Kipnis <danil.kipnis@cloud.ionos.com>,
swapnil ingle <ingleswapnil@gmail.com>,
linux-rdma@vger.kernel.org,
"open list:RNBD BLOCK DRIVERS" <linux-block@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block/rnbd: Adding name to the Contributors List
Date: Fri, 18 Dec 2020 07:53:03 -0700 [thread overview]
Message-ID: <a36bef5e-f7e3-c29b-8e65-38dc92812850@kernel.dk> (raw)
In-Reply-To: <CAMGffEm2LVxXJP-HseTqihcCvPeYOkCsaFHVNKXDZAYxCPzwTA@mail.gmail.com>
On 12/17/20 11:46 PM, Jinpu Wang wrote:
> Hi Jens,
>
> On Thu, Dec 17, 2020 at 6:44 PM swapnil ingle <ingleswapnil@gmail.com> wrote:
>>
>> Adding linux-rdma@vger.kernel.org
>>
>> On Fri, Nov 27, 2020 at 1:54 PM Danil Kipnis <danil.kipnis@cloud.ionos.com> wrote:
>>>
>>> On Fri, Nov 27, 2020 at 1:31 PM Swapnil Ingle <ingleswapnil@gmail.com> wrote:
>>>>
>>>> Adding name to the Contributors List
>>>>
>>>> Signed-off-by: Swapnil Ingle <ingleswapnil@gmail.com>
>>>
>>> Acked-by: Danil Kipnis <danil.kipnis@cloud.ionos.com>
> Can you pick up this patch, or do you need a resend from me or Swapnil?
Just include as part of the next series of patches. Though I do question
why we need such a contributors list to begin with, if you do git log on
the rnbd/ directory it'd show you anyway.
I'd also suggest moving the parts of the README that makes sense into a
proper Documentation/ file, nobody is going to find it deep in the
kernel source tree as it is.
--
Jens Axboe
next prev parent reply other threads:[~2020-12-18 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1606479915-7259-1-git-send-email-ingleswapnil@gmail.com>
2020-11-27 12:49 ` Jinpu Wang
2020-11-27 12:54 ` Danil Kipnis
[not found] ` <CAJCWmDdEPa23XDZ8pdStH=PgMszq4N6mHmNWtUA5Fn4THSNRmw@mail.gmail.com>
2020-12-18 6:46 ` Jinpu Wang
2020-12-18 14:53 ` Jens Axboe [this message]
2020-12-18 15:33 ` Jinpu Wang
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=a36bef5e-f7e3-c29b-8e65-38dc92812850@kernel.dk \
--to=axboe@kernel.dk \
--cc=danil.kipnis@cloud.ionos.com \
--cc=ingleswapnil@gmail.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.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 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®