From: Kalle Valo <kvalo@kernel.org>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <ath11k@lists.infradead.org>,
<ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH v3 1/3] wifi: ath12k: replace ENOTSUPP with EOPNOTSUPP
Date: Thu, 18 Jan 2024 05:50:41 +0000 (UTC) [thread overview]
Message-ID: <170555703932.2637903.971806943065664355.kvalo@kernel.org> (raw)
In-Reply-To: <20240117080431.2907471-2-quic_periyasa@quicinc.com>
Karthikeyan Periyasamy <quic_periyasa@quicinc.com> wrote:
> ENOTSUPP is not a standard error code, don't use it. Replace with
> EOPNOTSUPP instead.
>
> No functional changes, compile tested only.
>
> Signed-off-by: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
> Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
3 patches applied to ath-next branch of ath.git, thanks.
49b88e5f3fa1 wifi: ath12k: replace ENOTSUPP with EOPNOTSUPP
3422402bacd0 wifi: ath11k: replace ENOTSUPP with EOPNOTSUPP
bc2ef64931c2 wifi: ath10k: replace ENOTSUPP with EOPNOTSUPP
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240117080431.2907471-2-quic_periyasa@quicinc.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-01-18 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 8:04 [PATCH v3 0/3] wifi: ath: replace ENOTSUPP with EOPNOTSUPP Karthikeyan Periyasamy
2024-01-17 8:04 ` [PATCH v3 1/3] wifi: ath12k: " Karthikeyan Periyasamy
2024-01-18 5:50 ` Kalle Valo [this message]
2024-01-17 8:04 ` [PATCH v3 2/3] wifi: ath11k: " Karthikeyan Periyasamy
2024-01-17 8:04 ` [PATCH v3 3/3] wifi: ath10k: " Karthikeyan Periyasamy
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=170555703932.2637903.971806943065664355.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_periyasa@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).