From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>,
linux-tip-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@kernel.org>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's
Date: Sun, 8 Nov 2020 10:05:21 +0100 [thread overview]
Message-ID: <20201108090521.GA108695@gmail.com> (raw)
In-Reply-To: <20201107160444.GB30275@zn.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Sat, Nov 07, 2020 at 03:13:58PM -0000, tip-bot2 for Ingo Molnar wrote:
> > The following commit has been merged into the perf/kprobes branch of tip:
> >
> > Commit-ID: a70a04b3844f59c29573a8581d5c263225060dd6
> > Gitweb: https://git.kernel.org/tip/a70a04b3844f59c29573a8581d5c263225060dd6
> > Author: Ingo Molnar <mingo@kernel.org>
> > AuthorDate: Sat, 07 Nov 2020 12:54:49 +01:00
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitterDate: Sat, 07 Nov 2020 13:20:41 +01:00
> >
> > locking/atomics: Regenerate the atomics-check SHA1's
> >
> > The include/asm-generic/atomic-instrumented.h checksum got out
> > of sync, so regenerate it. (No change to actual code.)
> >
> > Also make scripts/atomic/gen-atomics.sh executable, to make
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > it easier to use.
^^^^^^^^^^^^^^^^^
> > mode change 100644 => 100755 scripts/atomic/gen-atomics.sh
> ^^^^^^^^^^^^^^^
>
> That looks like it snuck in but it shouldn't have...
So that mode change to executable was intentional, as mentioned in the
changelog.
Or did I miss something?
Thanks,
Ingo
next prev parent reply other threads:[~2020-11-08 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 15:13 [tip: perf/kprobes] locking/atomics: Regenerate the atomics-check SHA1's tip-bot2 for Ingo Molnar
2020-11-07 16:04 ` Borislav Petkov
2020-11-08 9:05 ` Ingo Molnar [this message]
2020-11-08 9:23 ` Borislav Petkov
2020-11-08 17:35 ` Linus Torvalds
2020-11-09 7:41 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201108090521.GA108695@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.