From: Guenter Roeck <linux@roeck-us.net>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-watchdog@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] watchdog: update email address in conversion doc
Date: Sat, 2 May 2020 07:59:16 -0700 [thread overview]
Message-ID: <20200502145916.GF189389@roeck-us.net> (raw)
In-Reply-To: <20200502143103.19473-1-wsa@kernel.org>
On Sat, May 02, 2020 at 04:30:58PM +0200, Wolfram Sang wrote:
> The old one is defunct. However, I think it makes sense that I am still
> the primary contact person for updates here.
>
> Signed-off-by: Wolfram Sang <wsa@kernel.org>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
>
> ... if there will be any. Let me know if you agree.
>
> Documentation/watchdog/convert_drivers_to_kernel_api.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/watchdog/convert_drivers_to_kernel_api.rst b/Documentation/watchdog/convert_drivers_to_kernel_api.rst
> index dd934cc08e40..b972ef4c7cff 100644
> --- a/Documentation/watchdog/convert_drivers_to_kernel_api.rst
> +++ b/Documentation/watchdog/convert_drivers_to_kernel_api.rst
> @@ -2,7 +2,7 @@
> Converting old watchdog drivers to the watchdog framework
> =========================================================
>
> -by Wolfram Sang <w.sang@pengutronix.de>
> +by Wolfram Sang <wsa@kernel.org>
>
> Before the watchdog framework came into the kernel, every driver had to
> implement the API on its own. Now, as the framework factored out the common
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-05-02 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 14:30 [PATCH] watchdog: update email address in conversion doc Wolfram Sang
2020-05-02 14:59 ` Guenter Roeck [this message]
2020-05-05 15:40 ` Jonathan Corbet
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=20200502145916.GF189389@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=kernel@pengutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.org \
--cc=wsa@kernel.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 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.