From: Borislav Petkov <bp@alien8.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tyler Hicks <tyhicks@linux.microsoft.com>,
Sasha Levin <sashal@kernel.org>, Lei Wang <lewan@microsoft.com>,
Tony Luck <tony.luck@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sinan Kaya <okaya@kernel.org>,
Shiping Ji <shiping.linux@gmail.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC/dmc520: Don't print an error for each unconfigured interrupt line
Date: Wed, 19 Jan 2022 10:37:51 +0100 [thread overview]
Message-ID: <Yefb7zO9p1iPF3Jm@zn.tnic> (raw)
In-Reply-To: <YefXQHXNlsxk8yUc@kroah.com>
On Wed, Jan 19, 2022 at 10:17:52AM +0100, Greg Kroah-Hartman wrote:
> For this specific change, I do NOT think it should be backported at all,
> mostly for the reason that people are still arguing over the whole
> platform_get_*_optional() mess that we currently have. Let's not go and
> backport anything right now to stable trees until we have all of that
> sorted out, as it looks like it all might be changing again. See:
> https://lore.kernel.org/r/20220110195449.12448-1-s.shtylyov@omp.ru
> for all of the gory details and the 300+ emails written on the topic so
> far.
It sounds to me I should not even take this patch upstream yet,
considering that's still ongoing...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-19 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:38 [PATCH] EDAC/dmc520: Don't print an error for each unconfigured interrupt line Tyler Hicks
2022-01-12 17:19 ` Lei Wang (DPLAT)
2022-01-16 18:29 ` Borislav Petkov
2022-01-18 15:28 ` Tyler Hicks
2022-01-18 17:28 ` Borislav Petkov
2022-01-18 19:54 ` Tyler Hicks
2022-01-18 21:04 ` Borislav Petkov
2022-01-19 9:17 ` Greg Kroah-Hartman
2022-01-19 9:37 ` Borislav Petkov [this message]
2022-01-19 10:28 ` Greg Kroah-Hartman
2022-04-04 21:56 ` Tyler Hicks
2022-04-18 20:40 ` Tyler Hicks
2022-04-18 21:13 ` Borislav Petkov
2022-04-18 21:34 ` Tyler Hicks
2022-04-19 9:36 ` Borislav Petkov
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=Yefb7zO9p1iPF3Jm@zn.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=okaya@kernel.org \
--cc=rric@kernel.org \
--cc=sashal@kernel.org \
--cc=shiping.linux@gmail.com \
--cc=tony.luck@intel.com \
--cc=tyhicks@linux.microsoft.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.