linux-kernel - Re: [PATCH] rtc: tps6586x: device wakeup flags correction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130522152204.d46057964fa06cc0d56f8e6b@linux-foundation.org>
Date:	Wed, 22 May 2013 15:22:04 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Dmitry Osipenko <digetx@...il.com>
Cc:	a.zummo@...ertech.it, akpm@...uxfoundation.org,
	ldewangan@...dia.com, rtc-linux@...glegroups.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rtc: tps6586x: device wakeup flags correction

On Sun, 12 May 2013 18:25:06 +0400 Dmitry Osipenko <digetx@...il.com> wrote:

> Use device_init_wakeup() instead of device_set_wakeup_capable() and move it
> before rtc dev registering. This fixes issue with alarmtimer that checks wakeup
> capability with device_may_wakeup() on device add.

Well OK, but what is this "issue"?

(form letter: When writing a changelog, please describe the
end-user-visible effects of the bug, so that others can more easily
decide which kernel version(s) should be fixed, and so that downstream
kernel maintainers can more easily work out whether this patch will fix
a problem which they or their customers are observing.)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/