From: Greg KH <gregkh@linuxfoundation.org>
To: Manali K Shukla <manashuk@cisco.com>
Cc: bp@alien8.de, linux-edac@vger.kernel.org, mchehab@kernel.org,
linux-kernel@vger.kernel.org, xe-linux-external@cisco.com,
Borislav Petkov <bp@suse.de>,
Aristeu Rozanski Filho <arozansk@redhat.com>,
Justin Ernst <justin.ernst@hpe.com>, Russ Anderson <rja@hpe.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [ PATCH stable v4.19] EDAC: Drop per-memory controller buses
Date: Tue, 17 Mar 2020 11:22:49 +0100 [thread overview]
Message-ID: <20200317102249.GC1130294@kroah.com> (raw)
In-Reply-To: <20200312052201.49456-1-manashuk@cisco.com>
On Wed, Mar 11, 2020 at 10:22:01PM -0700, Manali K Shukla wrote:
> From: Borislav Petkov <bp@suse.de>
>
> upstream 861e6ed667c83d64a42b0db41a22d6b4de4e913f commit
>
> ... and use the single edac_subsys object returned from
> subsys_system_register(). The idea is to have a single bus
> and multiple devices on it.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Acked-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> CC: Aristeu Rozanski Filho <arozansk@redhat.com>
> CC: Greg KH <gregkh@linuxfoundation.org>
> CC: Justin Ernst <justin.ernst@hpe.com>
> CC: linux-edac <linux-edac@vger.kernel.org>
> CC: Mauro Carvalho Chehab <mchehab@kernel.org>
> CC: Russ Anderson <rja@hpe.com>
> Cc: Tony Luck <tony.luck@intel.com>
> Link: https://lkml.kernel.org/r/20180926152752.GG5584@zn.tnic
> [Manali: backport to v4.19 -stable :
> - removing per-MC bus, this enables to get rid of memory controllers
> maximum number notion
> - value of max number of memory controllers is 2 * MAX_NUMNODES. On two nodes system MAX_NUMNODES value is ‘1’ and
> so value of max number of memory controller becomes ‘2’, this patch fixes this issue when there are only 2 nodes on the system
> and number of memory controllers are more than ‘2’]
> (cherry picked from commit 861e6ed667c83d64a42b0db41a22d6b4de4e913f)
> Signed-off-by: Manali K Shukla <manashuk@cisco.com>
Why is this a patch for the stable trees? What problem does it solve?
thanks,
greg k-h-
next prev parent reply other threads:[~2020-03-17 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 5:22 [ PATCH stable v4.19] EDAC: Drop per-memory controller buses Manali K Shukla
2020-03-17 10:22 ` Greg KH [this message]
2020-04-05 18:01 ` Manali Shukla (manashuk)
2020-04-05 18:06 ` Borislav Petkov
2020-04-05 19:26 ` Manali Shukla (manashuk)
2020-06-16 10:37 ` Greg KH
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=20200317102249.GC1130294@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arozansk@redhat.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=justin.ernst@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manashuk@cisco.com \
--cc=mchehab@kernel.org \
--cc=rja@hpe.com \
--cc=tony.luck@intel.com \
--cc=xe-linux-external@cisco.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).