mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Law <hlcj1234567@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>
Subject: Re: [PATCH] lib/uuid: fix typo "reversion" to "revision" in comment
Date: Fri, 6 Mar 2026 11:15:15 -0800	[thread overview]
Message-ID: <20260306111515.84bd9a300e9a310ab374c772@linux-foundation.org> (raw)
In-Reply-To: <52447e87-f013-4dc9-8abf-a52acaf6304a@gmail.com>

On Fri, 6 Mar 2026 19:03:57 +0000 Josh Law <hlcj1234567@gmail.com> wrote:

> 6 Mar 2026 19:00:09 Andy Shevchenko <andriy.shevchenko@linux.intel.com>:
> 
> > On Fri, Mar 06, 2026 at 04:12:50PM +0000, Josh Law wrote:
> >> Fix a typo in __uuid_gen_common() where "reversion" (meaning to revert)
> >> was used instead of "revision" when describing the UUID variant field.
> >
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > --
> > With Best Regards,
> > Andy Shevchenko
> 
> Hello Andy, Andrew has already merged this patch, you will have to inquire with him to add your reviewed by

I hold patches in quilt form for at least a few weeks before committing
them to non-rebasing git.  One of the many reasons for this is make
changelog alterations super easy.

Btw, I rewrote all your patches to be From: objecting@objecting.org. 
Please use an explicit From: line at the top-of-changelog to
communicate this.  All receiving tools understand this convention.


      parent reply	other threads:[~2026-03-06 19:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:12 Josh Law
2026-03-06 19:00 ` Andy Shevchenko
2026-03-06 19:03   ` Josh Law
2026-03-06 19:07     ` Andy Shevchenko
2026-03-06 19:15     ` Andrew Morton [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=20260306111515.84bd9a300e9a310ab374c772@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hlcj1234567@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=objecting@objecting.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

all inboxes | Powered by JetHome®