From: Jason Gunthorpe <jgg@ziepe.ca>
To: Colton Lewis <colton.w.lewis@protonmail.com>
Cc: linux-rdma@vger.kernel.org, dledford@redhat.com
Subject: Re: Fwd: [PATCH] infiniband: correct trivial kernel-doc inconsistencies
Date: Mon, 22 Jun 2020 12:00:18 -0300 [thread overview]
Message-ID: <20200622150018.GV6578@ziepe.ca> (raw)
In-Reply-To: <5373936.DvuYhMxLoT@laptop.coltonlewis.name>
On Sun, Jun 21, 2020 at 02:07:38AM +0000, Colton Lewis wrote:
> Can someone please accept or comment on this patch?
>
>
> Subject: [PATCH] infiniband: correct trivial kernel-doc inconsistencies
> Date: Thursday, June 11, 2020, 1:45:06 AM CDT
> From: Colton Lewis <colton.w.lewis@protonmail.com>
> To: dledford@redhat.com
> CC: trivial@kernel.org, Colton Lewis <colton.w.lewis@protonmail.com>
Patches that are not sent to linux-rdma@vger.kernel.org won't get
applied..
Applied to rmda for-next
Thanks,
Jason
prev parent reply other threads:[~2020-06-22 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 2:07 Fwd: [PATCH] infiniband: correct trivial kernel-doc inconsistencies Colton Lewis
2020-06-22 15:00 ` Jason Gunthorpe [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=20200622150018.GV6578@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=colton.w.lewis@protonmail.com \
--cc=dledford@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).