linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexander Potapenko <glider@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andrey Konovalov <andreyknvl@google.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	mm-commits@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.1-rc1
Date: Tue, 11 Oct 2022 10:11:11 -0700	[thread overview]
Message-ID: <CAHk-=wj-_peVY71FK7nX7p36VYacf2mFD5i4fKQpqk77J8K9Aw@mail.gmail.com> (raw)
In-Reply-To: <CAG_fn=WuMUKjdNwpcc7Msh6wrXFEkigYJJv9rS9+iMJO2d5Y-w@mail.gmail.com>

On Tue, Oct 11, 2022 at 2:03 AM Alexander Potapenko <glider@google.com> wrote:
>
> Small nit:
>
>      - Dmitry Vyukov introduces KMSAN: the Kernel Memory Sanitizer. It uses
>        clang-generated instrumentation to detect used-unintialized bugs down
>        to the single bit level.
>
> s/Dmitry Vyukov/Alexander Potapenko/ ;)

Uhhuh. I just took what Andrew told me for the commit message, so we
have that error in the history now.

Then when I reported my conflict resolution, at that point I actually
looked at the commit that introduced it, which is why I cc'd you.

So you got all the blame, and none of the glory. Sorry about that,

                   Linus

  reply	other threads:[~2022-10-11 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 20:21 [GIT PULL] MM updates for 6.1-rc1 Andrew Morton
2022-10-11  1:20 ` Linus Torvalds
2022-10-11  8:24   ` Peter Zijlstra
2022-10-11 17:08     ` Linus Torvalds
2022-10-11 18:44     ` Josh Poimboeuf
2022-10-11 18:59       ` Josh Poimboeuf
2022-10-11 19:05         ` [PATCH] kasan: disable stackleak plugin in report code Josh Poimboeuf
2022-10-11 22:00           ` Linus Torvalds
2022-10-11  9:02   ` [GIT PULL] MM updates for 6.1-rc1 Alexander Potapenko
2022-10-11 17:11     ` Linus Torvalds [this message]
2022-10-11  1:23 ` pr-tracker-bot

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='CAHk-=wj-_peVY71FK7nX7p36VYacf2mFD5i4fKQpqk77J8K9Aw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=glider@google.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).