All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv@lists.infradead.org,
	 Charlie Jenkins <charlie@rivosinc.com>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu,  parri.andrea@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: add forwarding header for arch/riscv/include/asm/fence.h
Date: Thu, 10 Oct 2024 08:11:33 +0200	[thread overview]
Message-ID: <mvmbjzs32sq.fsf@suse.de> (raw)
In-Reply-To: <mhng-adb76a44-07c8-442c-8bcf-6f29d061c031@palmer-ri-x1c9> (Palmer Dabbelt's message of "Wed, 09 Oct 2024 10:18:40 -0700 (PDT)")

On Okt 09 2024, Palmer Dabbelt wrote:

> Happy to pick this up via the RISC-V tree if you want.  Thanks!

Please make sure to pass it on soon, since it blocks building a
full-featured kernel.

Thanks.

-- 
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."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-riscv@lists.infradead.org,
	 Charlie Jenkins <charlie@rivosinc.com>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu,  parri.andrea@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: add forwarding header for arch/riscv/include/asm/fence.h
Date: Thu, 10 Oct 2024 08:11:33 +0200	[thread overview]
Message-ID: <mvmbjzs32sq.fsf@suse.de> (raw)
In-Reply-To: <mhng-adb76a44-07c8-442c-8bcf-6f29d061c031@palmer-ri-x1c9> (Palmer Dabbelt's message of "Wed, 09 Oct 2024 10:18:40 -0700 (PDT)")

On Okt 09 2024, Palmer Dabbelt wrote:

> Happy to pick this up via the RISC-V tree if you want.  Thanks!

Please make sure to pass it on soon, since it blocks building a
full-featured kernel.

Thanks.

-- 
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."

  reply	other threads:[~2024-10-10  6:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07  7:24 [PATCH] tools: add forwarding header for arch/riscv/include/asm/fence.h Andreas Schwab
2024-10-07  7:24 ` Andreas Schwab
2024-10-09 17:18 ` Palmer Dabbelt
2024-10-09 17:18   ` Palmer Dabbelt
2024-10-10  6:11   ` Andreas Schwab [this message]
2024-10-10  6:11     ` Andreas Schwab
2024-10-29 12:29   ` Andreas Schwab
2024-10-29 12:29     ` Andreas Schwab
2024-10-29 14:46 ` Anand Moon
2024-10-29 14:46   ` Anand Moon
2024-10-30  8:33 ` Alexandre Ghiti
2024-10-30  8:33   ` Alexandre Ghiti
2024-11-04 10:02 ` Alexandre Ghiti
2024-11-04 10:02   ` Alexandre Ghiti
2024-11-11  9:41   ` Andreas Schwab
2024-11-11  9:41     ` Andreas Schwab
2024-11-11 10:28     ` Alexandre Ghiti
2024-11-11 10:28       ` Alexandre Ghiti
2024-11-11 10:31       ` Andreas Schwab
2024-11-11 10:31         ` Andreas Schwab
2024-11-12 11:36         ` Björn Töpel
2024-11-12 11:36           ` Björn Töpel

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=mvmbjzs32sq.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=parri.andrea@gmail.com \
    --cc=paul.walmsley@sifive.com \
    /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.