linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@linux.microsoft.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Borislav Petkov <bp@alien8.de>
Cc: 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: Mon, 4 Apr 2022 16:56:40 -0500	[thread overview]
Message-ID: <20220404215640.GA626436@sequoia> (raw)
In-Reply-To: <YefnuCPwMq5V2lgl@kroah.com>

On 2022-01-19 11:28:08, Greg Kroah-Hartman wrote:
> On Wed, Jan 19, 2022 at 10:37:51AM +0100, Borislav Petkov wrote:
> > 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...
> 
> Yes, I would not take that just yet at all.  Let's let the api argument
> settle down a bit first.

The API argument seems to have fizzled out in v2:

 https://lore.kernel.org/lkml/20220212201631.12648-1-s.shtylyov@omp.ru/

Can this fix be merged since there seem to be no API changes coming
soon? Boris, feel free to strip off the cc stable tag.

Tyler

> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2022-04-04 22:45 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
2022-01-19 10:28               ` Greg Kroah-Hartman
2022-04-04 21:56                 ` Tyler Hicks [this message]
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=20220404215640.GA626436@sequoia \
    --to=tyhicks@linux.microsoft.com \
    --cc=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 \
    /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).