linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-riscv@lists.infradead.org, Alan Kao <alankao@andestech.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Anup Patel <anup@brainfault.org>,
	Dmitriy Cherkasov <dmitriy@oss-tech.org>,
	Johan Hovold <johan@kernel.org>,
	linux-kernel@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.
Date: Mon, 04 Mar 2019 09:36:33 +0100	[thread overview]
Message-ID: <mvmpnr711f2.fsf@suse.de> (raw)
In-Reply-To: <1550864500-13652-7-git-send-email-atish.patra@wdc.com> (Atish Patra's message of "Fri, 22 Feb 2019 11:41:40 -0800")

s/comman/common/ in the subject.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  parent reply	other threads:[~2019-03-04  8:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 19:41 [v6 PATCH 0/6] Various SMP related fixes Atish Patra
2019-02-22 19:41 ` [v6 PATCH 1/6] RISC-V: Do not wait indefinitely in __cpu_up Atish Patra
2019-02-22 19:41 ` [v6 PATCH 2/6] RISC-V: Move cpuid to hartid mapping to SMP Atish Patra
2019-02-22 19:41 ` [v6 PATCH 3/6] RISC-V: Remove NR_CPUs check during hartid search from DT Atish Patra
2019-02-22 19:41 ` [v6 PATCH 4/6] RISC-V: Allow hartid-to-cpuid function to fail Atish Patra
2019-02-22 19:41 ` [v6 PATCH 5/6] RISC-V: Compare cpuid with NR_CPUS before mapping Atish Patra
2019-02-22 19:41 ` [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities Atish Patra
2019-02-25  3:35   ` Anup Patel
2019-02-25  8:34   ` Johan Hovold
2019-03-04  8:36   ` Andreas Schwab [this message]
2019-03-04 19:06 ` [v6 PATCH 0/6] Various SMP related fixes Palmer Dabbelt

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=mvmpnr711f2.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=alankao@andestech.com \
    --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=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).