From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Matthew Hanzelik <mrhanzelik@gmail.com>
Cc: manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: qlge: qlge: Fix SPDX License Identifier style issue
Date: Mon, 30 Dec 2019 13:44:20 +0900 [thread overview]
Message-ID: <20191230044420.GA13113@f3> (raw)
In-Reply-To: <20191227055138.erzmqrahz2xksfda@mandalore.localdomain>
On 2019/12/27 00:51, Matthew Hanzelik wrote:
> Fixed a style issue with the SPDX License Identifier style.
>
> Signed-off-by: Matthew Hanzelik <mrhanzelik@gmail.com>
> ---
> drivers/staging/qlge/qlge.h | 1 +
> 1 file changed, 1 insertion(+)
Should it also be added to qlge_main.c?
You can remove the outdated comment about LICENSE.qlge at the same time.
prev parent reply other threads:[~2019-12-30 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 5:51 [PATCH] Staging: qlge: qlge: Fix SPDX License Identifier style issue Matthew Hanzelik
2019-12-30 4:44 ` Benjamin Poirier [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=20191230044420.GA13113@f3 \
--to=benjamin.poirier@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=mrhanzelik@gmail.com \
--cc=netdev@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).