public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-kernel@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
	Andreas Schwab <schwab@suse.de>, Anup Patel <anup@brainfault.org>,
	Dmitriy Cherkasov <dmitriy@oss-tech.org>,
	Johan Hovold <johan@kernel.org>,
	linux-riscv@lists.infradead.org,
	Palmer Dabbelt <palmer@sifive.com>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2 1/4] RISC-V: Add RISC-V specific arch_match_cpu_phys_id
Date: Wed, 10 Apr 2019 23:58:09 -0700	[thread overview]
Message-ID: <20190411065809.GB29422@infradead.org> (raw)
In-Reply-To: <20190410230443.15729-2-atish.patra@wdc.com>

On Wed, Apr 10, 2019 at 04:04:40PM -0700, Atish Patra wrote:
> OF/DT core has a hook for architecture specific logical cpuid to hartid
> mapping. By implementing this, we can pass the logical cpu id to cpu
> node parsing functions.

But that also means we must pass it that way.  So as-is this would
break existing setups, wouldn't it?

  reply	other threads:[~2019-04-11  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 23:04 [PATCH v2 0/4] Miscellaneous kernel command line fixes Atish Patra
2019-04-10 23:04 ` [PATCH v2 1/4] RISC-V: Add RISC-V specific arch_match_cpu_phys_id Atish Patra
2019-04-11  6:58   ` Christoph Hellwig [this message]
2019-04-10 23:04 ` [PATCH v2 2/4] RISC-V: Fix of_get_cpu_node usage Atish Patra
2019-04-11  6:59   ` Christoph Hellwig
2019-04-11 18:14     ` Atish Patra
2019-04-10 23:04 ` [PATCH v2 3/4] RISC-V: Implement nosmp commandline option Atish Patra
2019-04-11  7:01   ` Christoph Hellwig
2019-04-11 18:42     ` Atish Patra
2019-04-10 23:04 ` [PATCH v2 4/4] RISC-V: Support nr_cpus command line option Atish Patra

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=20190411065809.GB29422@infradead.org \
    --to=hch@infradead.org \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=dmitriy@oss-tech.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@suse.de \
    /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