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

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFznZnY_1-puQms6jm9nonAooDvTbvUqZjZ8bC0PGboLmg@mail.gmail.com>
Date:   Wed, 22 Nov 2017 21:05:27 -1000
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc:     linux-rtc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] RTC for 4.15

On Tue, Nov 21, 2017 at 5:28 AM, Alexandre Belloni
<alexandre.belloni@...e-electrons.com> wrote:
>
> The last minute change is only a documentation update to avoid further
> bug reports. (And also a small commit message reword).

This is _really_ annoying.

I'm checking that pull requests have been in linux-next, and that
rewording of the commit message just means that now that  commit
doesn't trigger as being in commit-next and I have to go chase it down
or just say "screw this, it adds a whole new driver that wasn't in
linux-next".

Guess which one is easier for me to do?

So don't do this crap.

I ended up looking up the original commit, but dammit, I'm not happy
about this. Why wasn't the RTC stuff sent last week like I asked
people to do? Now I'm in the middle of travels, and having to figure
out what parts were in linux-next to verify that it actually has
gotten at least some real test coverage, and that I'm not pulling
random stuff.

                Linus