From: Kalle Valo <kvalo@kernel.org>
To: "Grumbach\, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"luca\@coelho.fi" <luca@coelho.fi>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH] iwlwifi: mei: fix linking when tracing is not enabled
Date: Wed, 01 Dec 2021 14:28:09 +0200 [thread overview]
Message-ID: <87bl20o6g6.fsf@codeaurora.org> (raw)
In-Reply-To: <SA1PR11MB5825B46CCB4DF4207F4D5B4DF2689@SA1PR11MB5825.namprd11.prod.outlook.com> (Emmanuel Grumbach's message of "Wed, 1 Dec 2021 12:23:48 +0000")
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com> writes:
>>
>> Emmanuel Grumbach <emmanuel.grumbach@intel.com> writes:
>>
>> > I forgot to add stubs in case tracing is disabled.
>> >
>> > Reported-by: Jiri Slaby <jirislaby@kernel.org>
>> > Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
>>
>> Fixes tag? I can add that.
>
> I skipped that because it's not merged in Linus's tree yet, so, no
> stable consideration.
> I didn't know we need a Fixes tag for patches that are just in next as well.
I don't rebase my trees and neither does Dave&Jakub, so the commit ids
won't change. What commit id should I use? I can then add the 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-12-01 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 11:34 [PATCH] iwlwifi: mei: fix linking when tracing is not enabled Emmanuel Grumbach
2021-12-01 12:21 ` Kalle Valo
2021-12-01 12:23 ` Grumbach, Emmanuel
2021-12-01 12:28 ` Kalle Valo [this message]
2021-12-01 12:32 ` Grumbach, Emmanuel
2021-12-01 12:24 ` Coelho, Luciano
2021-12-05 11:55 ` Kalle Valo
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=87bl20o6g6.fsf@codeaurora.org \
--to=kvalo@kernel.org \
--cc=emmanuel.grumbach@intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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