public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Atish Patra <atishp@atishpatra.org>,
	Anup Patel <anup@brainfault.org>, Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes
Date: Wed, 7 Jun 2023 19:20:46 +0100	[thread overview]
Message-ID: <20230607-badly-onyx-2a9013c3549b@spud> (raw)
In-Reply-To: <20230607112417.782085-1-sunilvl@ventanamicro.com>


[-- Attachment #1.1: Type: text/plain, Size: 222 bytes --]

On Wed, Jun 07, 2023 at 04:54:15PM +0530, Sunil V L wrote:

> Changes since v1:
> 	1) Added "Fixes:" tag
> 	2) Added RB tag from Conor

b4 is usually capable of picking up Fixes: tags without having to resend
the series!


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

  parent reply	other threads:[~2023-06-07 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 11:24 [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes Sunil V L
2023-06-07 11:24 ` [PATCH v2 -next 1/2] RISC-V: ACPI : Fix for usage of pointers in different address space Sunil V L
2023-06-07 11:24 ` [PATCH v2 -next 2/2] RISC-V/perf: Use standard interface to get INTC domain Sunil V L
2023-06-07 23:19   ` Atish Patra
2023-06-07 18:20 ` Conor Dooley [this message]
2023-06-19 22:07 ` [PATCH v2 -next 0/2] RISC-V ACPI: Assorted fixes Palmer Dabbelt
2023-06-20  1:00 ` patchwork-bot+linux-riscv

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=20230607-badly-onyx-2a9013c3549b@spud \
    --to=conor@kernel.org \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=will@kernel.org \
    /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