From: Kalle Valo <kvalo@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jaewan Kim <jaewan@google.com>,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, kernel-team@android.com,
adelva@google.com
Subject: Re: [PATCH v8 0/5] mac80211_hwsim: Add PMSR support
Date: Mon, 06 Mar 2023 11:42:42 +0200 [thread overview]
Message-ID: <87cz5mz04t.fsf@kernel.org> (raw)
In-Reply-To: <ZADgBqP57XcW3/tH@kroah.com> (Greg KH's message of "Thu, 2 Mar 2023 18:42:30 +0100")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Thu, Mar 02, 2023 at 04:03:05PM +0000, Jaewan Kim wrote:
>> Dear Kernel maintainers,
>>
>> First of all, thank you for spending your precious time for reviewing
>> my changes, and also sorry for my mistakes in previous patchsets.
>>
>> Let me propose series of CLs for adding PMSR support in the mac80211_hwsim.
>
> What is a "CL"?
Hehe, we are not the only ones asking for this:
https://stackoverflow.com/questions/25716920/what-does-cl-mean-in-a-commit-message-what-does-it-stand-for
Apparently this is Google terminology but in upstream we use "patch" and
"patchset". But the recommendation is to not say "in this patchset" or
"in this patch" in commit logs, everyone know they are patches anyway.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-03-06 9:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 16:03 [PATCH v8 0/5] mac80211_hwsim: Add PMSR support Jaewan Kim
2023-03-02 16:03 ` [PATCH v8 1/5] mac80211_hwsim: add PMSR capability support Jaewan Kim
2023-03-06 16:54 ` Simon Horman
2023-03-06 16:58 ` Johannes Berg
2023-03-06 17:38 ` Simon Horman
2023-03-08 8:00 ` Jaewan Kim
2023-03-08 8:06 ` Johannes Berg
2023-03-13 7:54 ` Jaewan Kim
2023-03-02 16:03 ` [PATCH v8 2/5] wifi: nl80211: make nl80211_send_chandef non-static Jaewan Kim
2023-03-02 16:03 ` [PATCH v8 3/5] mac80211_hwsim: add PMSR request support via virtio Jaewan Kim
2023-03-06 17:12 ` Simon Horman
2023-03-06 17:43 ` Simon Horman
2023-03-06 20:45 ` Johannes Berg
2023-03-06 21:11 ` Simon Horman
2023-03-02 16:03 ` [PATCH v8 4/5] mac80211_hwsim: add PMSR abort " Jaewan Kim
2023-03-06 17:37 ` Simon Horman
2023-03-07 6:56 ` Simon Horman
2023-03-02 16:03 ` [PATCH v8 5/5] mac80211_hwsim: add PMSR report " Jaewan Kim
2023-03-02 17:42 ` [PATCH v8 0/5] mac80211_hwsim: Add PMSR support Greg KH
2023-03-06 9:42 ` Kalle Valo [this message]
[not found] ` <CABZjns4xYjcn4CQzEoiozz9j7mKF0py0WE+AZ2Koi9Vz3khVLQ@mail.gmail.com>
2023-03-08 10:05 ` Kalle Valo
2023-03-13 7:56 ` Jaewan Kim
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=87cz5mz04t.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=adelva@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaewan@google.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-team@android.com \
--cc=linux-wireless@vger.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).