From: Kalle Valo <kvalo@codeaurora.org>
To: "Coelho\, Luciano" <luciano.coelho@intel.com>
Cc: "tiwai\@suse.de" <tiwai@suse.de>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/2] iwlwifi: dbg: Don't touch the tlv data
Date: Thu, 14 Jan 2021 09:14:33 +0200 [thread overview]
Message-ID: <878s8wrnvq.fsf@codeaurora.org> (raw)
In-Reply-To: <3022a89080907456096ef137ffad525fa134b081.camel@intel.com> (Luciano Coelho's message of "Tue, 12 Jan 2021 17:08:22 +0000")
"Coelho, Luciano" <luciano.coelho@intel.com> writes:
>> BTW, I thought network people don't want to have Cc-to-stable in the
>> patch, so I didn't put it by myself. Is this rule still valid?
>
> In the wireless side of network, we've always used Cc stable when
> needed
Yeah, we handle stable patches differently from the main network tree.
> but the Fixes tag itself will almost always trigger the stable
> people to take it anyway.
BTW, this is now clarified in the documentation:
https://lkml.kernel.org/r/20210113163315.1331064-1-lee.jones@linaro.org
So cc stable should be added even if there's already a Fixes tag.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-01-14 7:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 13:24 [PATCH 0/2] iwlwifi: Fix a crash at loading Takashi Iwai
2021-01-12 13:24 ` [PATCH 1/2] iwlwifi: dbg: Don't touch the tlv data Takashi Iwai
2021-01-12 15:48 ` Kalle Valo
2021-01-12 16:02 ` Takashi Iwai
2021-01-12 17:08 ` Coelho, Luciano
2021-01-14 7:14 ` Kalle Valo [this message]
2021-01-14 16:57 ` [1/2] " Kalle Valo
2021-01-12 13:24 ` [PATCH 2/2] iwlwifi: dbg: Mark ucode tlv data as const Takashi Iwai
2021-01-12 15:50 ` Kalle Valo
2021-01-12 16:05 ` Takashi Iwai
2021-01-12 17:13 ` Coelho, Luciano
2021-01-13 6:50 ` Kalle Valo
2021-02-10 11:35 ` Luca Coelho
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=878s8wrnvq.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tiwai@suse.de \
/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).