From: Peter Zijlstra <peterz@infradead.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jason Baron <jbaron@akamai.com>, Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] static_call: Fix unused variable warning
Date: Thu, 22 Apr 2021 18:13:32 +0200 [thread overview]
Message-ID: <YIGgrMeudHobfDYQ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <552a3a35-43c6-348e-ad46-1abb298cbfbc@roeck-us.net>
On Thu, Apr 22, 2021 at 07:01:47AM -0700, Guenter Roeck wrote:
> On 4/22/21 12:20 AM, Peter Zijlstra wrote:
> > On Wed, Apr 21, 2021 at 08:41:39PM -0400, Steven Rostedt wrote:
> >>
> >> Second patch with the exact same update. Perhaps we should take one
> >> before we get more of them ;-)
> >>
> >
> > I thought we already fixed that...
>
> Not in v5.12-rc8-6-g4bdafe832681, which is ToT right now.
>
> Ah, I do see it in -next, but that doesn't help me in mainline,
> nor in stable branches where the patch introducing the problem
> has been backported to.
Given it's a silly warning I didn't figure it was urgent material. I
suppose we can backport it if someone (you apperntly) cares.
next prev parent reply other threads:[~2021-04-22 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 0:33 Guenter Roeck
2021-04-22 0:41 ` Steven Rostedt
2021-04-22 1:24 ` Guenter Roeck
2021-04-22 1:33 ` Steven Rostedt
2021-04-22 1:45 ` Guenter Roeck
2021-04-22 2:38 ` Steven Rostedt
2021-04-22 7:20 ` Peter Zijlstra
2021-04-22 14:01 ` Guenter Roeck
2021-04-22 16:13 ` Peter Zijlstra [this message]
2021-04-22 18:01 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2021-04-16 19:43 [PATCH] static_call: fix " Carlos Llamas
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=YIGgrMeudHobfDYQ@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ardb@kernel.org \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®