From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Brian Masney <bmasney@redhat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 07/16] clk: microchip: core: update include to use pic32.h from platform_data
Date: Fri, 16 Jan 2026 09:15:16 +0200 [thread overview]
Message-ID: <bcaa0b6c-48e7-4407-b399-cb5b998dcfa3@tuxon.dev> (raw)
In-Reply-To: <20260112-mips-pic32-header-move-v2-7-927d516b1ff9@redhat.com>
On 1/13/26 00:48, Brian Masney wrote:
> Use the linux/platform_data/pic32.h include instead of
> asm/mach-pic32/pic32.h so that the asm variant can be dropped. This
> is in preparation for allowing some drivers to be compiled on other
> architectures with COMPILE_TEST enabled.
>
> Signed-off-by: Brian Masney<bmasney@redhat.com>
Acked-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
next prev parent reply other threads:[~2026-01-16 7:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 22:47 [PATCH v2 00/16] MIPS: move pic32.h header file from asm to platform_data Brian Masney
2026-01-12 22:47 ` [PATCH v2 01/16] MIPS: pic32: include linux/io.h header on several files Brian Masney
2026-01-12 22:47 ` [PATCH v2 02/16] MIPS: pic32: include linux/types.h on pic32.h Brian Masney
2026-01-12 22:47 ` [PATCH v2 03/16] MIPS: pic32: drop unused include linux/io.h from pic32.h Brian Masney
2026-01-16 7:12 ` claudiu beznea
2026-01-16 15:14 ` Brian Masney
2026-01-12 22:47 ` [PATCH v2 04/16] MIPS: copy pic32.h header file from asm/mach-pic32/ to include/platform-data/ Brian Masney
2026-01-12 22:47 ` [PATCH v2 05/16] MAINTAINERS: add include/linux/platform_data/pic32.h to MIPS entry Brian Masney
2026-01-12 22:48 ` [PATCH v2 06/16] MIPS: update include to use pic32.h from platform_data Brian Masney
2026-01-12 22:48 ` [PATCH v2 07/16] clk: microchip: core: " Brian Masney
2026-01-16 7:15 ` claudiu beznea [this message]
2026-01-12 22:48 ` [PATCH v2 08/16] irqchip/irq-pic32-evic: " Brian Masney
2026-01-13 8:53 ` Thomas Gleixner
2026-01-12 22:48 ` [PATCH v2 09/16] mmc: sdhci-pic32: " Brian Masney
2026-01-21 6:51 ` Adrian Hunter
2026-01-22 17:26 ` Ulf Hansson
2026-01-12 22:48 ` [PATCH v2 10/16] pinctrl: pic32: " Brian Masney
2026-01-12 22:48 ` [PATCH v2 11/16] rtc: " Brian Masney
2026-01-12 22:48 ` [PATCH v2 12/16] serial: pic32_uart: " Brian Masney
2026-01-13 6:38 ` Jiri Slaby
2026-01-13 11:30 ` Brian Masney
2026-01-12 22:48 ` [PATCH v2 13/16] watchdog: pic32-dmt: " Brian Masney
2026-01-12 22:48 ` [PATCH v2 14/16] watchdog: pic32-wdt: " Brian Masney
2026-01-12 22:48 ` [PATCH v2 15/16] MIPS: drop unused pic32.h header Brian Masney
2026-01-12 22:48 ` [PATCH v2 16/16] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2026-01-13 5:48 ` Stephen Boyd
2026-01-13 11:35 ` Brian Masney
2026-01-23 0:49 ` [PATCH v2 00/16] MIPS: move pic32.h header file from asm to platform_data Brian Masney
2026-01-30 14:37 ` Thomas Bogendoerfer
2026-02-10 12:42 ` Brian Masney
2026-02-10 15:50 ` Thomas Bogendoerfer
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=bcaa0b6c-48e7-4407-b399-cb5b998dcfa3@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®