From: wim@www.linux-watchdog.org
To: Jerry Hoemann <jerry.hoemann@hpe.com>
Cc: Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [GIT PULL REQUEST] watchdog - v4.17-rc merge window
Date: Thu, 12 Apr 2018 09:19:49 +0200 [thread overview]
Message-ID: <20180412071948.GA26103@www.linux-watchdog.org> (raw)
In-Reply-To: <20180411220345.GC20346@anatevka.americas.hpqcorp.net>
Hi Jerry,
> Shouldn't there be an update to the MAINTAINERS file to reflect change
> in hpwdt? See:
>
> https://lkml.org/lkml/2018/2/21/145
Correct. It wasn't in linux-watchdog-next neither. So it seems I forgot that one. I'll add it and sent it in with some other small changes next week.
Kind regards,
Wim.
next prev parent reply other threads:[~2018-04-12 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 19:12 [GIT PULL REQUEST] watchdog - v4.17-rc merge window wim
2018-04-11 22:03 ` Jerry Hoemann
2018-04-12 7:19 ` wim [this message]
2018-04-12 16:28 ` Jerry Hoemann
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=20180412071948.GA26103@www.linux-watchdog.org \
--to=wim@www.linux-watchdog.org \
--cc=jerry.hoemann@hpe.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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