linux-kernel - Re: [PATCH] timeconst: update path in comment

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: <CAHmME9oBwntBginfmMpS1VP8sb48VNJqf=hO8E9Ra-gmfNz5dQ@mail.gmail.com>
Date:	Thu, 22 Oct 2015 17:31:17 +0200
From:	"Jason A. Donenfeld" <Jason@...c4.com>
To:	hofrat@...dl.org, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] timeconst: update path in comment

It's understandable nobody really cares about applying this patch,
since it's mostly just cosmetic. But it would be nice to know that
somebody out there cares about consistency like I do. It would also
help out the next person who's debugging time things and says "where
is that darn .bc file?".

On Tue, Jul 14, 2015 at 7:24 PM, Jason A. Donenfeld <Jason@...c4.com> wrote:
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
> ---
>  kernel/time/timeconst.bc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/time/timeconst.bc b/kernel/time/timeconst.bc
> index c7388de..c486889 100644
> --- a/kernel/time/timeconst.bc
> +++ b/kernel/time/timeconst.bc
> @@ -39,7 +39,7 @@ define fmuls(b,n,d) {
>  }
>
>  define timeconst(hz) {
> -       print "/* Automatically generated by kernel/timeconst.bc */\n"
> +       print "/* Automatically generated by kernel/time/timeconst.bc */\n"
>         print "/* Time conversion constants for HZ == ", hz, " */\n"
>         print "\n"
>
> --
> 2.4.5
>
--
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/