linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Xujun Leng <lengxujun2007@126.com>, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: mm: fix comment typo of pud_offset_phys()
Date: Thu, 26 Aug 2021 12:07:29 +0100	[thread overview]
Message-ID: <162997601443.30374.4843361649013969123.b4-ty@arm.com> (raw)
In-Reply-To: <20210825150526.12582-1-lengxujun2007@126.com>

On Wed, 25 Aug 2021 23:05:26 +0800, Xujun Leng wrote:
> Fix a typo in the comment of macro pud_offset_phys().

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: mm: fix comment typo of pud_offset_phys()
      https://git.kernel.org/arm64/c/5845e703f9b5

-- 
Catalin


      reply	other threads:[~2021-08-26 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 15:05 [PATCH] arm64: mm: fix comment typo of pud_offset_phys() Xujun Leng
2021-08-26 11:07 ` Catalin Marinas [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=162997601443.30374.4843361649013969123.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=lengxujun2007@126.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@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 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).