From: Conor Dooley <conor@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Emil Renner Berthing <kernel@esmil.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] soc: sifive: shunt ccache driver to drivers/cache
Date: Wed, 22 Nov 2023 11:52:48 +0000 [thread overview]
Message-ID: <20231122-reanalyze-modified-9e59bbc89864@spud> (raw)
In-Reply-To: <d94d54d2-50a3-4dc8-9178-e69c118aeefe@sifive.com>
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
On Tue, Nov 21, 2023 at 07:25:20PM -0600, Samuel Holland wrote:
> > +if ARCH_SIFIVE || ARCH_STARFIVE
>
> Since this is now in a file grouped/sorted by subsystem instead of by platform,
> maybe it makes sense to convert this to a "depends on" line?
I did that on application, thanks.
> > -source "drivers/soc/sifive/Kconfig"
> > source "drivers/soc/starfive/Kconfig"
>
> This file has a conflict and needs to be rebased, but otherwise:
am -3 took care of it :)
> Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
> Tested-by: Samuel Holland <samuel.holland@sifive.com>
Cheers,
Conor.
[-- 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
next prev parent reply other threads:[~2023-11-22 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 9:22 [PATCH v1] soc: sifive: shunt ccache driver to drivers/cache Conor Dooley
2023-11-22 1:25 ` Samuel Holland
2023-11-22 11:52 ` Conor Dooley [this message]
2023-11-22 11:50 ` Conor Dooley
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=20231122-reanalyze-modified-9e59bbc89864@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=kernel@esmil.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox