From: Brian Masney <bmasney@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 10/13] watchdog: pic32-dmt: update include to use pic32.h from platform_data
Date: Fri, 9 Jan 2026 12:11:16 -0500 [thread overview]
Message-ID: <aWE2tCUkePX8Cls-@redhat.com> (raw)
In-Reply-To: <76129cc9-345b-4866-8cb9-b36e4374cf8b@roeck-us.net>
On Fri, Jan 09, 2026 at 09:08:37AM -0800, Guenter Roeck wrote:
> On Fri, Jan 09, 2026 at 11:41:23AM -0500, 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>
> >
>
> linux/platform_data/pic32.h doesn't exist upstream, and I was not
> copied on the patch introducing it, so I'll just blindly asume that
> this works.
>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
I didn't CC everyone on all of the patches to reduce the spam in your
mailboxes.
It was introduced in patch 1 of this series when I copied it over
from the asm directory. I'll reply to the cover letter as a heads up to
everyone else.
Thanks!
Brian
next prev parent reply other threads:[~2026-01-09 17:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 16:41 [PATCH 00/13] MIPS: move pic32.h header file from asm to platform_data Brian Masney
2026-01-09 16:41 ` [PATCH 01/13] MIPS: copy pic32.h header file from asm/mach-pic32/ to include/platform-data/ Brian Masney
2026-01-09 16:41 ` [PATCH 02/13] MAINTAINERS: add include/linux/platform_data/pic32.h to MIPS entry Brian Masney
2026-01-09 16:41 ` [PATCH 03/13] MIPS: update include to use pic32.h from platform_data Brian Masney
2026-01-09 16:41 ` [PATCH 04/13] clk: microchip: core: " Brian Masney
2026-01-09 16:41 ` [PATCH 05/13] irqchip/irq-pic32-evic: " Brian Masney
2026-01-09 16:41 ` [PATCH 06/13] mmc: sdhci-pic32: " Brian Masney
2026-01-12 8:40 ` Adrian Hunter
2026-01-12 20:54 ` Brian Masney
2026-01-09 16:41 ` [PATCH 07/13] pinctrl: pic32: " Brian Masney
2026-01-09 23:25 ` Linus Walleij
2026-01-09 16:41 ` [PATCH 08/13] rtc: " Brian Masney
2026-01-09 17:42 ` Alexandre Belloni
2026-01-09 16:41 ` [PATCH 09/13] serial: pic32_uart: " Brian Masney
2026-01-09 16:41 ` [PATCH 10/13] watchdog: pic32-dmt: " Brian Masney
2026-01-09 17:08 ` Guenter Roeck
2026-01-09 17:11 ` Brian Masney [this message]
2026-01-09 16:41 ` [PATCH 11/13] watchdog: pic32-wdt: " Brian Masney
2026-01-09 17:09 ` Guenter Roeck
2026-01-09 16:41 ` [PATCH 12/13] MIPS: drop unused pic32.h header Brian Masney
2026-01-10 15:28 ` Claudiu Beznea
2026-01-12 20:41 ` Brian Masney
2026-01-09 16:41 ` [PATCH 13/13] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2026-01-09 17:14 ` [PATCH 00/13] MIPS: move pic32.h header file from asm to platform_data Brian Masney
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=aWE2tCUkePX8Cls-@redhat.com \
--to=bmasney@redhat.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tsbogend@alpha.franken.de \
--cc=wim@linux-watchdog.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