From: Dan Carpenter <dan.carpenter@oracle.com>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"supporter:QLOGIC QLGE 10Gb ETHERNET DRIVER"
<GR-Linux-NIC-Dev@marvell.com>,
open list <linux-kernel@vger.kernel.org>,
Manish Chopra <manishc@marvell.com>,
"open list:QLOGIC QLGE 10Gb ETHERNET DRIVER"
<netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2] fix trailing */ in block comment
Date: Thu, 25 Jun 2020 20:25:10 +0300 [thread overview]
Message-ID: <20200625172510.GF2549@kadam> (raw)
In-Reply-To: <20200625153614.63912-2-coiby.xu@gmail.com>
The subject isn't right (no subsystem prefix) and we need a commit
message.
regards,
dan carpenter
next prev parent reply other threads:[~2020-06-25 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200625153614.63912-1-coiby.xu@gmail.com>
2020-06-25 15:36 ` [PATCH 1/2] fix trailing */ in block comment Coiby Xu
2020-06-25 17:24 ` Greg Kroah-Hartman
2020-06-25 17:25 ` Dan Carpenter [this message]
2020-06-25 22:00 ` Coiby Xu
2020-06-25 15:36 ` [PATCH 2/2] fix else after return or break Coiby Xu
2020-06-25 17:23 ` Greg Kroah-Hartman
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=20200625172510.GF2549@kadam \
--to=dan.carpenter@oracle.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=coiby.xu@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.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