From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2][next] IB/hfi1: Use fallthrough pseudo-keyword
Date: Fri, 24 Jul 2020 15:13:33 -0500 [thread overview]
Message-ID: <47048c5a-a2b3-5c45-22a2-153a27d42864@embeddedor.com> (raw)
In-Reply-To: <20200724200143.GA3670533@nvidia.com>
On 7/24/20 15:01, Jason Gunthorpe wrote:
>
> Applied to for-next, thanks
>
Thanks, Jason.
--
Gustavo
prev parent reply other threads:[~2020-07-24 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 13:34 [PATCH v2][next] IB/hfi1: Use fallthrough pseudo-keyword Gustavo A. R. Silva
2020-07-24 20:01 ` Jason Gunthorpe
2020-07-24 20:13 ` Gustavo A. R. Silva [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=47048c5a-a2b3-5c45-22a2-153a27d42864@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=gustavoars@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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