From: Guenter Roeck <linux@roeck-us.net>
To: Tomas Winkler <tomas.winkler@intel.com>,
Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [watchdog-next] watchdog: kill unref/ref ops
Date: Sun, 3 Jan 2016 07:48:15 -0800 [thread overview]
Message-ID: <568942BF.2090402@roeck-us.net> (raw)
In-Reply-To: <1451820757-8840-1-git-send-email-tomas.winkler@intel.com>
On 01/03/2016 03:32 AM, Tomas Winkler wrote:
> ref/unref ops are not called at all so even marked them as deprecated
> is misleading, we need to just drop the API.
>
One the other side, the functions are now no-ops, so they don't hurt either.
Only reason for not dropping the functions as part of my series was that
the mei watchdog code was starting to implement them, and I didn't want
to create dependencies for that code. Maybe my thinking was too conservative.
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
... of course that is no concern anymore since this patch is from its
maintainer.
Acked-by: Guenter Roeck <linux@roeck-us.net>
Thanks!
Guenter
> ---
> include/linux/watchdog.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
> index 850af04fe0c7..aaabd4703b46 100644
> --- a/include/linux/watchdog.h
> +++ b/include/linux/watchdog.h
> @@ -47,8 +47,6 @@ struct watchdog_ops {
> int (*set_timeout)(struct watchdog_device *, unsigned int);
> unsigned int (*get_timeleft)(struct watchdog_device *);
> int (*restart)(struct watchdog_device *);
> - void (*ref)(struct watchdog_device *) __deprecated;
> - void (*unref)(struct watchdog_device *) __deprecated;
> long (*ioctl)(struct watchdog_device *, unsigned int, unsigned long);
> };
>
>
next prev parent reply other threads:[~2016-01-03 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 11:32 [watchdog-next] watchdog: kill unref/ref ops Tomas Winkler
2016-01-03 15:48 ` Guenter Roeck [this message]
2016-01-04 23:38 ` Winkler, Tomas
2016-01-04 23:58 ` Guenter Roeck
2016-01-11 21:28 ` Wim Van Sebroeck
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=568942BF.2090402@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=wim@iguana.be \
/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.