From: "krzk@kernel.org" <krzk@kernel.org>
To: Bongsu Jeon <bongsu.jeon@samsung.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
Krzysztof Opasiak <k.opasiak@samsung.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/3] nfc: s3fwrn5: Change the error code.
Date: Sat, 14 Nov 2020 11:08:21 +0100 [thread overview]
Message-ID: <20201114100821.GC5253@kozik-lap> (raw)
In-Reply-To: <20201114002134epcms2p1b504111777f3b1be7a0d1706882a5237@epcms2p1>
On Sat, Nov 14, 2020 at 09:21:34AM +0900, Bongsu Jeon wrote:
>
> ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP.
The same as in patch #1 - trailing dot a subject end empty line at
beginning of commit.
Please CC all required maintainers and lists when submitting patches.
You skipped here LKML and the most important - NFC mailing list. Use the
scripts/get_maintainer.pl to get the necessary addresses.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-11-14 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201114002134epcms2p1b504111777f3b1be7a0d1706882a5237@epcms2p1>
2020-11-14 0:21 ` [PATCH net-next 3/3] nfc: s3fwrn5: Change the error code Bongsu Jeon
2020-11-14 10:08 ` krzk [this message]
[not found] <CGME20201116011950epcms2p68117cc4a7228db2baecb7d4a4840b955@epcms2p6>
2020-11-16 1:19 ` Bongsu Jeon
2020-11-16 9:08 ` krzk
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=20201114100821.GC5253@kozik-lap \
--to=krzk@kernel.org \
--cc=bongsu.jeon@samsung.com \
--cc=k.opasiak@samsung.com \
--cc=kuba@kernel.org \
--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).