linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Jan Henrik Weinstock <jan.weinstock@rwth-aachen.de>
Cc: geert@linux-m68k.org, jonas@southpole.se,
	stefan.kristiansson@saunalahti.fi, openrisc@lists.librecores.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] openrisc: use device tree to determine present cpus
Date: Fri, 5 Feb 2021 23:43:17 +0900	[thread overview]
Message-ID: <20210205144317.GK2002709@lianli.shorne-pla.net> (raw)
In-Reply-To: <6dbc27f8-5261-59c5-acba-70f6c6a74ba1@rwth-aachen.de>

On Mon, Feb 01, 2021 at 12:49:31PM +0100, Jan Henrik Weinstock wrote:
> Use the device tree to determine the present cpus instead of assuming all
> CONFIG_NRCPUS are actually present in the system.
> 
> Signed-off-by: Jan Henrik Weinstock <jan.weinstock@rwth-aachen.de>

Hi Jan,

I cannot apply this patch, it seems you somehow sent it signed as a multipart
message via Thunderbird.

This causes errors when trying to apply, even after I tried to manually fix the
patch mail:

    Applying: openrisc: use device tree to determine present cpus
    error: sha1 information is lacking or useless (arch/openrisc/kernel/smp.c).
    error: could not build fake ancestor
    Patch failed at 0001 openrisc: use device tree to determine present cpus

Can you send this using 'git send-email?'

If not I can get it applied with some work, otherwise you can point me to a git
repo which I can pull it from.

-Stafford

  reply	other threads:[~2021-02-05 23:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 18:29 [PATCH] openrisc: use device tree to determine present cpus Jan Henrik Weinstock
2021-01-29 22:16 ` Stafford Horne
2021-01-30 11:00   ` Jan Henrik Weinstock
2021-01-30 23:03     ` Stafford Horne
2021-01-30 23:11       ` Stafford Horne
2021-01-31  8:22       ` Jan Henrik Weinstock
2021-01-31 21:27         ` Stafford Horne
2021-02-01 11:49           ` [PATCH v2] " Jan Henrik Weinstock
2021-02-05 14:43             ` Stafford Horne [this message]
2021-02-05 16:07               ` Geert Uytterhoeven
2021-02-05 22:36                 ` Stafford Horne
2021-02-06  9:33                   ` Geert Uytterhoeven
     [not found]                     ` <20210208121648.GN2002709@lianli.shorne-pla.net>
2021-02-08 12:22                       ` Geert Uytterhoeven
2021-01-30 10:37 ` [PATCH] " Geert Uytterhoeven

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=20210205144317.GK2002709@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=jan.weinstock@rwth-aachen.de \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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).