From: <Mario.Limonciello@dell.com>
To: <andy.shevchenko@gmail.com>, <stuart.w.hayes@gmail.com>
Cc: <dvhart@infradead.org>, <linux-kernel@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>
Subject: RE: [PATCH 0/5] Update and move Dell drivers dell_rbu and dcdbas
Date: Wed, 26 Sep 2018 14:50:32 +0000 [thread overview]
Message-ID: <2c21dba5f4074bc0861277ec5701d2ff@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <CAHp75Ve=ZnkBbdG3Myu1qzubr6+q74Q0u9pR7+nHXG=yAO-0rA@mail.gmail.com>
> On Tue, Sep 25, 2018 at 10:34 PM Stuart Hayes <stuart.w.hayes@gmail.com>
> wrote:
> >
> > From: Stuart Hayes <stuart.w.hayes@gmail.com>
> >
> > The dell_rbu and dcdbas drivers need some changes, and should be moved to
> > drivers/platform/x86. Additionally, dell_rbu needs a maintainer, and the
> > listed maintainer for dcdbas is inactive and needs to be changed.
>
> I pushed this series to my review and testing queue to allow bots play with.
>
> But.
> Please, add commit messages to patches 4 and 5 (I can't take w/o them).
> Collect Doug's tag that proves he is okay with the change (I remember
> he answered something to the old thread, though I don't remember the
> details except annoying footer which should not be up in open source
> mailing lists).
>
> So, while bots are playing with the code I'm waiting for v2 of this
> with above addressed.
> Thanks!
>
Just so it's extra clear, you want an "Acked-by" tag from Doug W in a public
forum? Or he should be CC to that patch and needs to give the acked-by
tag in the V2?
He already did respond in a public forum indicating this although he didn't
"generate a tag" for that:
https://www.spinics.net/lists/platform-driver-x86/msg16336.html
Can Stuart just add the "Acked-by" tag himself to the commit in V2 at this
point considering that? Or do you need patchwork to pick it up and apply it?
next prev parent reply other threads:[~2018-09-26 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:34 Stuart Hayes
2018-09-25 19:34 ` [PATCH 1/5] firmware: dell_rbu: Make payload memory uncachable Stuart Hayes
2018-09-25 19:34 ` [PATCH 2/5] firmware: dcdbas: Add support for WSMT ACPI table Stuart Hayes
2018-09-25 19:34 ` [PATCH 3/5] firmware: dell_rbu: Move dell_rbu to drivers/platform/x86 Stuart Hayes
2018-09-25 19:34 ` [PATCH 4/5] firmware: dcdbas: Move dcdbas " Stuart Hayes
2018-09-25 19:34 ` [PATCH 5/5] MAINTAINERS: Update maintainer for dcdbas and dell_rbu Stuart Hayes
2018-09-26 11:04 ` [PATCH 0/5] Update and move Dell drivers dell_rbu and dcdbas Andy Shevchenko
2018-09-26 11:05 ` Andy Shevchenko
2018-09-26 14:50 ` Mario.Limonciello [this message]
2018-09-26 16:55 ` Andy Shevchenko
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=2c21dba5f4074bc0861277ec5701d2ff@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stuart.w.hayes@gmail.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
all inboxes | Powered by JetHome®