From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm: smp: remove unused variable
Date: Tue, 26 Jan 2021 13:40:57 +0000 [thread overview]
Message-ID: <20210126134057.GH1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210126130240.GA2413@kunai>
On Tue, Jan 26, 2021 at 02:02:40PM +0100, Wolfram Sang wrote:
> Hi Russell,
>
> > Those who cause breakage really should be the ones to look at patches
> > that fix their breakage.
>
> Does it mean you want an explicit ack from Thomas or that it should go
> via his tree?
What I'm saying is... don't expect me to always review patches that
are for fixing code that other people have contributed - I wish those
who introduce regressions would stick around and attend to breakage
that they cause, instead of hoping that someone else will do that
for them. It's a reasonable ask.
> > The way patches get applied is if they end up in my patch system... if
> > they don't make it there, they don't get applied.
>
> The patch itself is here:
>
> https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9047/1
Thanks - I'll get around to it in due course. Since I'm no longer
supported as 32-bit ARM maintainer, I only apply patches once or maybe
twice per kernel release. Quite how long this will be sustainable for,
I've no idea (it depends whether I get any actual paying work, and
how much.)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Marc Zyngier <maz@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: smp: remove unused variable
Date: Tue, 26 Jan 2021 13:40:57 +0000 [thread overview]
Message-ID: <20210126134057.GH1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210126130240.GA2413@kunai>
On Tue, Jan 26, 2021 at 02:02:40PM +0100, Wolfram Sang wrote:
> Hi Russell,
>
> > Those who cause breakage really should be the ones to look at patches
> > that fix their breakage.
>
> Does it mean you want an explicit ack from Thomas or that it should go
> via his tree?
What I'm saying is... don't expect me to always review patches that
are for fixing code that other people have contributed - I wish those
who introduce regressions would stick around and attend to breakage
that they cause, instead of hoping that someone else will do that
for them. It's a reasonable ask.
> > The way patches get applied is if they end up in my patch system... if
> > they don't make it there, they don't get applied.
>
> The patch itself is here:
>
> https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9047/1
Thanks - I'll get around to it in due course. Since I'm no longer
supported as 32-bit ARM maintainer, I only apply patches once or maybe
twice per kernel release. Quite how long this will be sustainable for,
I've no idea (it depends whether I get any actual paying work, and
how much.)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-26 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 12:01 [PATCH] arm: smp: remove unused variable Wolfram Sang
2020-12-28 12:01 ` Wolfram Sang
2021-01-26 10:04 ` Geert Uytterhoeven
2021-01-26 10:04 ` Geert Uytterhoeven
2021-01-26 10:41 ` Russell King - ARM Linux admin
2021-01-26 10:41 ` Russell King - ARM Linux admin
2021-01-26 13:02 ` Wolfram Sang
2021-01-26 13:02 ` Wolfram Sang
2021-01-26 13:40 ` Russell King - ARM Linux admin [this message]
2021-01-26 13:40 ` Russell King - ARM Linux admin
2021-01-26 13:52 ` Wolfram Sang
2021-01-26 13:52 ` Wolfram Sang
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=20210126134057.GH1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.