[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171017150812.187a6816af791519294897b6@linux-foundation.org>
Date: Tue, 17 Oct 2017 15:08:12 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrey Smirnov <andrew.smirnov@...il.com>
Cc: linux-watchdog@...r.kernel.org, Chris Healy <cphealy@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Wim Van Sebroeck <wim@...ana.be>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH v2] watchdog: core: Make use of
devm_register_reboot_notifier()
On Tue, 17 Oct 2017 08:50:12 -0700 Andrey Smirnov <andrew.smirnov@...il.com> wrote:
> On Sat, Apr 15, 2017 at 11:11 PM, Guenter Roeck <linux@...ck-us.net> wrote:
> > On 04/11/2017 09:06 AM, Andrey Smirnov wrote:
> >>
> >> Save a bit of cleanup code by leveraging newly added
> >> devm_register_reboot_notifier().
> >>
> >> Cc: cphealy@...il.com
> >> Cc: linux-kernel@...r.kernel.org
> >> Cc: Wim Van Sebroeck <wim@...ana.be>
> >> Cc: Guenter Roeck <linux@...ck-us.net>
> >> Cc: Andy Shevchenko <andy.shevchenko@...il.com>
> >> Cc: Andrew Morton <akpm@...ux-foundation.org>
> >> Signed-off-by: Andrey Smirnov <andrew.smirnov@...il.com>
> >
> >
> > Acked-by: Guenter Roeck <linux@...ck-us.net>
> >
>
> Andrew,
>
> This patch can't go in via watchdog tree because it depends on
> devm_register_reboot_notifier() which is still present only in
> linux-next, any change you can pull this into linux-next as well?
That's because I've been sitting on
kernel-reboot-add-devm_register_reboot_notifier.patch since March
because it has no users.
This patch adds a user. Have you identified other sites which
can/should use devm_register_reboot_notifier()? I guess quite a lot,
so it's a matter of alerting developers to the new interface. I
wonder how. A checkpatch rule would do it, but that's new ground for
checkpatch.
Powered by blists - more mailing lists