From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jakub Kicinski <kuba@kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Kalle Valo <kvalo@kernel.org>,
Colin Ian King <colin.i.king@gmail.com>,
linux-wireless@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] wifi: ath9k: Don't mark channelmap stack variable read-only in ath9k_mci_update_wlan_channels()
Date: Thu, 20 Apr 2023 17:56:26 +0200 [thread overview]
Message-ID: <87354utumt.fsf@toke.dk> (raw)
In-Reply-To: <20230420075027.6852197a@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
>> > He doesn't
>> > mind doing that for an occasional regression fix. And then he can decide
>> > himself if the change is worth the risk -- and obviously can take into
>> > account if he'll release and rc8 or not.
>>
>> I'm OK with doing it that way; I'll do so later tonight unless Kalle or
>> Jakub complains before then...
>
> Ah, just after our last(?) 6.3 PR was submitted :(
> No objections to you posting this directly to Linus...
Heh, yeah :( In retrospect, just asking you to take it directly into
-net might have been the expedient thing to do here.
> That said it is a 6.2 regression AFAICT so it's not exactly in the
> "must be fixed in 6.3" category. Assuming Kalle doesn't want a PR -
> should we take it into net and have it reach Linus either next Tue
> (assuming no -rc8) or Thu (if -rc8)?
How about I ping Linus and if he doesn't want to take it directly, you
can pull it into -net?
-Toke
next prev parent reply other threads:[~2023-04-20 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 21:41 [PATCH] wifi: ath9k: Don't mark channelmap stack variable read-only in ath9k_mci_update_wlan_channels() Toke Høiland-Jørgensen
2023-04-14 10:00 ` Kalle Valo
2023-04-14 10:32 ` Toke Høiland-Jørgensen
2023-04-14 12:38 ` Kalle Valo
2023-04-18 10:14 ` Toke Høiland-Jørgensen
2023-04-19 4:54 ` Kalle Valo
2023-04-20 13:50 ` Thorsten Leemhuis
2023-04-20 14:24 ` Toke Høiland-Jørgensen
2023-04-20 14:50 ` Jakub Kicinski
2023-04-20 15:56 ` Toke Høiland-Jørgensen [this message]
2023-04-20 16:39 ` Jakub Kicinski
2023-04-20 15:59 ` Thorsten Leemhuis
2023-04-20 16:55 ` Jakub Kicinski
2023-04-20 18:27 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-19 14:24 ` Kalle Valo
2023-04-19 15:18 ` Colin King (gmail)
2023-04-20 21:09 ` One-off regression fix for 6.3 [was: Re: [PATCH] wifi: ath9k: Don't mark channelmap stack variable read-only in ath9k_mci_update_wlan_channels()] Toke Høiland-Jørgensen
2023-04-20 22:27 ` Linus Torvalds
2023-04-20 22:38 ` Toke Høiland-Jørgensen
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=87354utumt.fsf@toke.dk \
--to=toke@toke.dk \
--cc=colin.i.king@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).