All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Busch <mbsh@google.com>
To: jackmanb@google.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
	 peterz@infradead.org, tglx@kernel.org, x86@kernel.org,
	 Marcel Busch <mbsh@google.com>
Subject: Re: [PATCH v2 3/3] x86/mm: drop unused returns from direct map setup functions
Date: Tue, 23 Jun 2026 14:18:59 +0000	[thread overview]
Message-ID: <20260623141859.1407784-1-mbsh@google.com> (raw)
In-Reply-To: <20260503-x86-init-cleanup-v2-3-bb690bd2477c@google.com>

Checked all callers again. Return value removed consistently, local variables
adjusted accordingly.
Tested using qemu-system-x86_64 (11.0.1) -machine q35.

Reviewed-by: Marcel Busch <mbsh@google.com>
Tested-by: Marcel Busch <mbsh@google.com>

  parent reply	other threads:[~2026-06-23 14:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 13:04 [PATCH v2 0/3] x86/mm: some cleanups for pagetable setup code Brendan Jackman
2026-05-03 13:04 ` [PATCH v2 1/3] x86/mm: drop unused return from init_memory_mapping() Brendan Jackman
2026-06-02 21:30   ` Dave Hansen
2026-06-23 14:12   ` Marcel Busch
2026-05-03 13:04 ` [PATCH v2 2/3] x86/mm: simplify calculation of max_pfn_mapped Brendan Jackman
2026-06-02 21:39   ` Dave Hansen
2026-06-03 10:20     ` Brendan Jackman
2026-06-24 12:36       ` Brendan Jackman
2026-06-23 14:17   ` Marcel Busch
2026-05-03 13:04 ` [PATCH v2 3/3] x86/mm: drop unused returns from direct map setup functions Brendan Jackman
2026-06-02 21:40   ` Dave Hansen
2026-06-23 14:18   ` Marcel Busch [this message]
2026-05-27 12:40 ` [PATCH v2 0/3] x86/mm: some cleanups for pagetable setup code Brendan Jackman
2026-06-02 21:53 ` Dave Hansen

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=20260623141859.1407784-1-mbsh@google.com \
    --to=mbsh@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --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.