linux-kernel - Re: [PATCH] rtc: add in ability to push out an existing wakealarm using sysfs

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: <20130522145529.a03f3344f58b4b9ddacb25b7@linux-foundation.org>
Date:	Wed, 22 May 2013 14:55:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Bernie Thompson <bhthompson@...omium.org>
Cc:	rtc-linux@...glegroups.com,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Rob Landley <rob@...dley.net>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, dianders@...omium.org
Subject: Re: [PATCH] rtc: add in ability to push out an existing wakealarm
 using sysfs

On Fri, 10 May 2013 17:53:31 -0700 Bernie Thompson <bhthompson@...omium.org> wrote:

> This adds in the ability for the rtc sysfs code to handle += characters
> at the beginning of a wakealarm setting string. This will allow the user to
> attempt to push out an existing wakealarm by a provided amount.
> 
> In the case that the += characters are provided but the alarm is not active
> -EVINVAL is returned.
> 

Well that sounds useful, but I'm not personally in a position to
confidently judge whether it's useful enough to merge the patch.  The
changelog doesn't make a compelling case and everybody else has chosen
to sit on their hands.

So I really don't know what to do with this patch.

--
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/