From: Saeed Mahameed <saeed@kernel.org>
To: Zou Wei <zou_wei@huawei.com>,
leon@kernel.org, davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] net/mlx5_core: remove unused including <generated/utsrelease.h>
Date: Mon, 14 Dec 2020 23:30:55 -0800 [thread overview]
Message-ID: <44630610f64e4535646e4cb5ba8e0e62d52fc360.camel@kernel.org> (raw)
In-Reply-To: <1607497292-121156-1-git-send-email-zou_wei@huawei.com>
On Wed, 2020-12-09 at 15:01 +0800, Zou Wei wrote:
> Remove including <generated/utsrelease.h> that don't need it.
>
> Fixes: 17a7612b99e6 ("net/mlx5_core: Clean driver version and name")
> Signed-off-by: Zou Wei <zou_wei@huawei.com>
> ---
Applied to net-next-mlx5.
Thanks!
prev parent reply other threads:[~2020-12-15 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 7:01 [PATCH -next v2] net/mlx5_core: remove unused including <generated/utsrelease.h> Zou Wei
2020-12-15 7:30 ` Saeed Mahameed [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=44630610f64e4535646e4cb5ba8e0e62d52fc360.camel@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zou_wei@huawei.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).