From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: lukasz.anaczkowski@intel.com
Cc: dougthompson@xmission.com, bp@alien8.de,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>,
Aristeu Rozanski <aris@redhat.com>
Subject: Re: [PATCH 0/3] EDAC: add DDR4 flag, misc improvements
Date: Tue, 9 Jun 2015 08:54:42 -0300 [thread overview]
Message-ID: <20150609085442.4ce53e78@recife.lan> (raw)
In-Reply-To: <1433850192-9866-1-git-send-email-lukasz.anaczkowski@intel.com>
Hi Lukasz,
Em Tue, 9 Jun 2015 13:43:09 +0200
lukasz.anaczkowski@intel.com escreveu:
> From: Lukasz Anaczkowski <lukasz.anaczkowski@intel.com>
>
> Series of patches that makes sb_edac more flexible for adding
> support for future platforms.
>
> Jim Snow (3):
> EDAC: add DDR4 flag
> sb_edac: virtualize several hard-coded functions
> sb_edac: support for duplicate device IDs
>
> drivers/edac/sb_edac.c | 95 ++++++++++++++++++++++++++++++++++++++++----------
> include/linux/edac.h | 6 ++--
> 2 files changed, 80 insertions(+), 21 deletions(-)
The patches look interesting, but, specially in the case of patch 3/3,
it is hard to review them without the patches that add support for
future platforms that require multi-bus. I can't, for example,
understand, so far, the need of "allow_dups" function parameter for
sbridge_get_all_devices().
So, I'd like to see this patch series together with the patches
adding support for those new "multi-bus" platforms.
Thanks,
Mauro
prev parent reply other threads:[~2015-06-09 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 11:43 [PATCH 0/3] EDAC: add DDR4 flag, misc improvements lukasz.anaczkowski
2015-06-09 11:43 ` [PATCH 1/3] EDAC: add DDR4 flag lukasz.anaczkowski
2015-06-09 11:43 ` [PATCH 2/3] sb_edac: virtualize several hard-coded functions lukasz.anaczkowski
2015-06-12 13:30 ` Aristeu Rozanski
2015-06-15 8:06 ` Anaczkowski, Lukasz
2015-06-09 11:43 ` [PATCH 3/3] sb_edac: support for duplicate device IDs lukasz.anaczkowski
2015-06-09 11:50 ` [PATCH 0/3] EDAC: add DDR4 flag, misc improvements Borislav Petkov
2015-06-09 11:54 ` Mauro Carvalho Chehab [this message]
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=20150609085442.4ce53e78@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.anaczkowski@intel.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 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.