From: Borislav Petkov <bp@alien8.de>
To: Scott Branden <scott.branden@broadcom.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Yuqing Shen <yuqing.shen@broadcom.com>,
Lei Wang <lewan@microsoft.com>, James Morse <james.morse@arm.com>,
Robert Richter <rrichter@marvell.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: EDAC driver for DMC520
Date: Tue, 7 Jan 2020 19:49:26 +0100 [thread overview]
Message-ID: <20200107184926.GL29542@zn.tnic> (raw)
In-Reply-To: <bdb29d6d-bc63-cf68-0e32-556740537cd8@broadcom.com>
On Tue, Jan 07, 2020 at 09:57:26AM -0800, Scott Branden wrote:
> Hello EDAC Maintainers,
>
> Could somebody have a look at the DMC520 patch series that has been waiting
> for a response since November:
> https://patchwork.kernel.org/patch/11248785/
Well, the dt bindings stuff is still being discussed:
https://patchwork.kernel.org/patch/11248783/
Also, looking at this again, the patch authorship looks really fishy:
Sender is
From: Shiping Ji <shiping.linux@gmail.com>
however, he doesn't have his SOB in there and previous iterations were
done with Lei Wang whose SOB *is* there so I dunno what's going on.
*Especially* if Lei Wang is being added as a maintainer of that driver
by the second patch but he's not sending this driver himself. If this
driver is going to be orphaned the moment it lands upstream, I'm not
going to take it.
So at least those two things need to be fixed/clarified first.
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-01-07 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:57 EDAC driver for DMC520 Scott Branden
2020-01-07 18:49 ` Borislav Petkov [this message]
2020-01-07 18:55 ` Scott Branden
2020-01-07 19:01 ` Shiping Ji
2020-01-07 19:13 ` Scott Branden
2020-01-07 19:18 ` Shiping Ji
2020-01-07 19:56 ` Borislav Petkov
2020-01-07 19:59 ` Shiping Ji
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=20200107184926.GL29542@zn.tnic \
--to=bp@alien8.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rrichter@marvell.com \
--cc=scott.branden@broadcom.com \
--cc=tony.luck@intel.com \
--cc=yuqing.shen@broadcom.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