linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Arvind Sankar <nivedita@alum.mit.edu>,
	x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-sh@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	sparclinux@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Drop unused MAX_PHYSADDR_BITS
Date: Fri, 24 Jul 2020 08:04:41 -0700	[thread overview]
Message-ID: <e6747427-30a9-7e5c-2693-5e3d770d578a@intel.com> (raw)
In-Reply-To: <20200723231544.17274-1-nivedita@alum.mit.edu>

On 7/23/20 4:15 PM, Arvind Sankar wrote:
> This #define is not used anywhere, and has the wrong value on x86_64.

Yeah, it certainly is unused.

> I tried digging into the history a bit, but it seems to have been unused
> even in the initial merge of sparsemem in v2.6.13, when it was first
> defined.

Yep, I don't even remember why we thought we needed it back then.  Feel
free to add my ack on these, or at least the x86 one.

  parent reply	other threads:[~2020-07-24 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 23:15 [PATCH 0/3] Drop unused MAX_PHYSADDR_BITS Arvind Sankar
2020-07-23 23:15 ` [PATCH 1/3] x86/mm: " Arvind Sankar
2020-07-24  7:56   ` [tip: x86/cleanups] " tip-bot2 for Arvind Sankar
2020-07-24  8:22   ` [PATCH 1/3] " David Hildenbrand
2020-07-23 23:15 ` [PATCH 2/3] sh/mm: " Arvind Sankar
2020-07-24  8:22   ` David Hildenbrand
2020-07-23 23:15 ` [PATCH 3/3] sparc: " Arvind Sankar
2020-07-24  8:22   ` David Hildenbrand
2020-07-24 23:37   ` David Miller
2020-07-24 15:04 ` Dave Hansen [this message]
2020-07-26  6:48 ` [PATCH 0/3] " Mike Rapoport

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=e6747427-30a9-7e5c-2693-5e3d770d578a@intel.com \
    --to=dave.hansen@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=nivedita@alum.mit.edu \
    --cc=peterz@infradead.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=x86@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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).