From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Evan Benn <evanbenn@chromium.org>
Cc: Julius Werner <jwerner@chromium.org>,
Guenter Roeck <linux@roeck-us.net>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: rectify entry in ARM SMC WATCHDOG DRIVER
Date: Tue, 30 Jun 2020 21:59:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2006302156120.3966@felia> (raw)
In-Reply-To: <CAKz_xw3KuWFSkcz-9hLHGZ2=S7nJ=K=AN6j2FJ6afZBFowJO7g@mail.gmail.com>
On Fri, 5 Jun 2020, Evan Benn wrote:
> AFAICT this has now been merged upstream, I'm not sure what action to take:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5c24a28b4eb842ad1256496be6ae01bab15f1dcb
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=72a9e7fea5866fc471fda78f05f166595c8c6ba6
This patch is still fully valid and still applies to next-20200630; it can
be simply applied as any other bug fix to your driver code.
Evan, can you please ask Wim as linux-watchdog maintainer to pick-up this
patch, with the reviews below?
Lukas
>
> On Wed, Jun 3, 2020 at 9:22 AM Evan Benn <evanbenn@chromium.org> wrote:
> >
> > Apologies for that slip up.
> >
> > Reviewed-by: Evan Benn <evanbenn@chromium.org>
> >
> > On Wed, Jun 3, 2020 at 6:16 AM Julius Werner <jwerner@chromium.org> wrote:
> > >
> > > Reviewed-by: Julius Werner <jwerner@chromium.org>
>
next prev parent reply other threads:[~2020-06-30 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 5:21 [PATCH] MAINTAINERS: rectify entry in ARM SMC WATCHDOG DRIVER Lukas Bulwahn
2020-06-02 5:34 ` Guenter Roeck
2020-06-02 20:16 ` Julius Werner
2020-06-02 23:22 ` Evan Benn
2020-06-05 1:42 ` Evan Benn
2020-06-30 19:59 ` Lukas Bulwahn [this message]
2020-06-30 20:32 ` Guenter Roeck
2020-06-30 20:37 ` Lukas Bulwahn
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=alpine.DEB.2.21.2006302156120.3966@felia \
--to=lukas.bulwahn@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=evanbenn@chromium.org \
--cc=joe@perches.com \
--cc=jwerner@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
/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).