mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Foxie Flakey <foxieflakey@gmail.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Foxie Flakey <foxieflakey@gmail.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	rppt@kernel.org,  peterx@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] userfaultfd: reset err to be 0 when move_pages_ptes succeeded
Date: Wed, 19 Aug 2026 10:04:10 +0700 (WIB)	[thread overview]
Message-ID: <b66af965-5bee-1c20-d5b9-ce77b0c8b117@gmail.com> (raw)
In-Reply-To: <CAJuCfpFzcpqG+g9f-m+-B6yk=pOU+PKgKRLVowOE65S127NWzA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

On Tue, 18 Aug 2026, Suren Baghdasaryan wrote:

> On Tue, Aug 18, 2026 at 9:50 AM Foxie Flakey <foxieflakey@gmail.com> wrote:
> >
> > On Tue, 18 Aug 2026, Suren Baghdasaryan wrote:
> >
> > > On Mon, Aug 17, 2026 at 6:13 PM Foxie Flakey <foxieflakey@gmail.com> wrote:
> > > >
> > > > On Mon, 17 Aug 2026, Andrew Morton wrote:
> > > >
> > > > > On Sat, 15 Aug 2026 17:42:12 +0700 (WIB) Foxie Flakey <foxieflakey@gmail.com> wrote:
> > > > >
> > > > > > Fixes: 50944692052b ("userfaultfd: opportunistic TLB-flush batching for present pages in MOVE")
> > > > > > Signed-off-by: Foxie Flakey <foxieflakey@gmail.com>
> > > > >
> > > > > Yes, the pseudonym is problematic - it is contrary to our written
> > > > > rules.  But I'm a sucker for fixes, sigh.  Perhaps if someone else were
> > > > > to send me your patch with their signoff also, the rules would be less
> > > > > offended.
> > > >
> > > > I see, I'll post the updated patch and work on signoff issue later (there
> > > > has been updates, I haven't posted v2 which updates the patch and
> > > > description following a feedback. Why I didn't? mainly I'm not sure with
> > > > answer for signoff)
> > >
> > > Yeah, please follow Mike's advise.
> >
> > Okay, thank you! I'll re-ask Mike again due I'm not receiving sufficient
> > answer.
>
> His advice was to use something that identifies you. When you meet
> someone at a conference you do not identify yourself as Foxie Flakey
> (unless maybe you are at some anime convention). Use the same
> reasoning here please.
>

Thank you. Its clearer now. After thinking for a while, I'll replace the
name on Signed-off-by with my legal name (yes I'm aware legal is not
required but I don't have other name which would meet under that reasoning)
following the rule. I'll update the patch once again with proper signoff.

      reply	other threads:[~2026-08-19  3:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 10:42 Foxie Flakey
2026-08-16  9:15 ` Mike Rapoport
2026-08-16  9:41   ` Foxie Flakey
2026-08-16 11:45     ` Mike Rapoport
2026-08-16 13:58       ` Foxie Flakey
2026-08-18 17:07       ` Foxie Flakey
2026-08-16 15:43   ` Suren Baghdasaryan
2026-08-16 15:58     ` Foxie Flakey
2026-08-17 22:26 ` Andrew Morton
2026-08-17 22:35   ` Andrew Morton
2026-08-18  1:29     ` Foxie Flakey
2026-08-18  1:13   ` Foxie Flakey
2026-08-18 15:07     ` Suren Baghdasaryan
2026-08-18 16:50       ` Foxie Flakey
2026-08-18 17:11         ` Suren Baghdasaryan
2026-08-19  3:04           ` Foxie Flakey [this message]

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=b66af965-5bee-1c20-d5b9-ce77b0c8b117@gmail.com \
    --to=foxieflakey@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    /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

all inboxes | Powered by JetHome®