linux-kernel - Re: [GIT PULL] RTC for 5.18

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: <CAHk-=wjuUZWMeUaTGtfivNQYeuqsQb2C4HnbbPLe+qFXU5Y70Q@mail.gmail.com>
Date:   Fri, 1 Apr 2022 09:50:30 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc:     linux-rtc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] RTC for 5.18

On Thu, Mar 31, 2022 at 3:21 PM Alexandre Belloni
<alexandre.belloni@...tlin.com> wrote:
>
> Here is the RTC subsystem pull request for 5.18. The bulk of the patches
> are about replacing the uie_unsupported struct rtc_device member by a
> feature bit.

Hmm.

I've pulled this, but I don't see the point of the ALARM_RES_2S bit.

In particular, I don't see it used anywhere, and the two drivers that
now set it clear both the UPDATE_INTERRUPT and ALARM features.

So what's the point of that feature bit?

                Linus