From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-aspeed@lists.ozlabs.org,
Peter Zijlstra <peterz@infradead.org>,
David Brown <david.brown@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-i2c@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Daniel Drake <dsd@laptop.org>,
linux-scsi@vger.kernel.org, Jens Frederich <jfrederich@gmail.com>,
openbmc@lists.ozlabs.org, Ingo Molnar <mingo@redhat.com>,
Andy Gross <andy.gross@linaro.org>,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk>,
dou_liyang@163.com, Rob Herring <robh+dt@kernel.org>,
bp@alien8.de, Vincent Guittot <vincent.guittot@linaro.org>,
linux-arm-kernel@lists.infradead.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Andrew Jeffery <andrew@aj.id.au>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Rob Clark <robdclark@gmail.com>,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH 0/7] v4.19-stable randconfig fixes
Date: Tue, 18 Dec 2018 16:12:30 +0100 [thread overview]
Message-ID: <20181218151230.GA30844@kroah.com> (raw)
In-Reply-To: <20181218002028.GX2746@sasha-vm>
On Mon, Dec 17, 2018 at 07:20:28PM -0500, Sasha Levin wrote:
> On Fri, Dec 14, 2018 at 11:10:05PM +0100, Arnd Bergmann wrote:
> > Hi Greg,
> >
> > I did some randconfig testing on linux-4.19 arm/arm64/x86. So far I needed
> > 27 patches, most of which are also still needed in mainline Linux. I
> > had submitted some before, and others were not submitted previously
> > for some reason. I'll try to get those fixed in mainline and then
> > make sure we get them into 4.19 as well.
> >
> > This series for now contains four patches that did make it into mainline:
> >
> > 2e6ae11dd0d1 ("slimbus: ngd: mark PM functions as __maybe_unused")
> > 33f49571d750 ("staging: olpc_dcon: add a missing dependency")
> > 0eeec01488da ("scsi: raid_attrs: fix unused variable warning")
> > 11d4afd4ff66 ("sched/pelt: Fix warning and clean up IRQ PELT config")
> >
> > Feel free to either cherry-pick those from mainline or apply the
> > patch from this series, whichever works best for you.
> >
> > The other three patches are for warnings in code that got removed in
> > mainline kernels:
> >
> > 3e9efc3299dd ("i2c: aspeed: Handle master/slave combined irq events properly")
> > 972910948fb6 ("ARM: dts: qcom: Remove Arrow SD600 eval board")
> > effec874792f ("drm/msm/dpu: Remove dpu_dbg")
> >
> > My feeling was that it's safer to just address the warning by fixing
> > the code correctly in each of these cases, but if you disagree,
> > applying the mainline change should work equally well, so decide
> > for yourself.
>
> Thanks Arnd, I took the series as is.
>
> We really need to discuss how -stable deals with removed code upstream.
> For some cases, we should probably follow suit and remove it from
> -stable as well (I'm mostly thinking dodgy code with potential security
> issues).
It would be nice to do that at times (like lustre and ipx), but it's
good to keep that code around as maybe someone is using it? I don't
know, it's a tough call...
thanks,
greg k-h
_______________________________________________
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:[~2018-12-18 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 22:10 [PATCH 0/7] v4.19-stable randconfig fixes Arnd Bergmann
2018-12-18 0:20 ` Sasha Levin
2018-12-18 15:12 ` Greg Kroah-Hartman [this message]
2018-12-18 16:20 ` Sasha Levin
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=20181218151230.GA30844@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@aj.id.au \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dou_liyang@163.com \
--cc=dsd@laptop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jfrederich@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhat.com \
--cc=openbmc@lists.ozlabs.org \
--cc=peterz@infradead.org \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sashal@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).