From: Kalle Valo <kvalo@kernel.org>
To: "serge" <vasilugin@yandex.ru>
Cc: linux-wireless@vger.kernel.org, Stanislaw Gruszka <stf_xl@wp.pl>
Subject: Re: [PATCH] wifi:rt2x00: don't overwrite SoC specific bbp init
Date: Mon, 26 Feb 2024 09:18:47 +0200 [thread overview]
Message-ID: <87o7c3ae20.fsf@kernel.org> (raw)
In-Reply-To: <20240226094016.1JaTRGbB@mail-nwsmtp-smtp-production-main-29.myt.yp-c.yandex.net> (serge's message of "Mon, 26 Feb 2024 13:40:14 +0700")
"serge" <vasilugin@yandex.ru> writes:
> SoCs rt305x have the same MAC version but SoC specific bbp init function
>
> Signed-off-by: Serge Vailugin <vasilugin@yandex.ru>
The commit message should answer to the question 'Why?'. What user
visible issue/symptom does this patch fix?
Also From field need to match with s-o-b, now the names are different.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-02-26 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 6:40 [PATCH] wifi:rt2x00: don't overwrite SoC specific bbp init serge
2024-02-26 7:18 ` Kalle Valo [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=87o7c3ae20.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
--cc=vasilugin@yandex.ru \
/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).