From: Leon Romanovsky <leon@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Boris Pismenny <borisp@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx5: fix spelling mistake "reserverd" -> "reserved"
Date: Tue, 18 Feb 2020 15:45:46 +0200 [thread overview]
Message-ID: <20200218134546.GA8816@unreal> (raw)
In-Reply-To: <20200214143002.23140-1-alexandre.belloni@bootlin.com>
On Fri, Feb 14, 2020 at 03:30:01PM +0100, Alexandre Belloni wrote:
> The reserved member should be named reserved.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
> include/linux/mlx5/mlx5_ifc_fpga.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied to mlx5-next.
Thanks
prev parent reply other threads:[~2020-02-18 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 14:30 [PATCH] net/mlx5: fix spelling mistake "reserverd" -> "reserved" Alexandre Belloni
2020-02-18 13:45 ` Leon Romanovsky [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=20200218134546.GA8816@unreal \
--to=leon@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=borisp@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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;
as well as URLs for NNTP newsgroup(s).