All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 0/3] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
Date: Tue, 24 Feb 2026 12:43:17 -0500	[thread overview]
Message-ID: <aZ3jNaDR5eaCtX7p@redhat.com> (raw)
In-Reply-To: <20260224-gotten-showing-f5f276daa541@spud>

On Tue, Feb 24, 2026 at 05:36:25PM +0000, Conor Dooley wrote:
> On Tue, Feb 24, 2026 at 12:27:27PM -0500, Brian Masney wrote:
> > On Tue, Feb 24, 2026 at 05:10:42PM +0000, Conor Dooley wrote:
> > > On Sun, Feb 22, 2026 at 06:51:03PM -0500, Brian Masney wrote:
> > > > Here's a small series that lets us enable COMPILE_TEST for the pic32 clk
> > > > driver so that this driver can be compiled on all architectures in the
> > > > future to help avoid breakage.
> > > 
> > > Why do you care about this platform? Originally I thought you cared cos
> > > you were getting involved in clock subsystem stuff, but I see you doing
> > > stuff with it in pinctrl etc. Is that just general cleanup work, or do
> > > you actually have an interest in the platform?
> > 
> > My sole interest is to clean up the clk driver, which spilled into
> > larger work to clean the include header to allow this driver to be
> > compiled on other architectures. If I was going to do this for the
> > clk driver, it wasn't that much work to do the other pic32 driver
> > cleanups while I was there.
> > 
> > Honestly, I hope to done with all of these pic32 drivers after what I
> > posted this week has been merged.
> 
> Not to pooh pooh your efforts, but I asking as I am wondering whether
> the whole platform should be deleted. I'm gonna ask internally about it,
> but none of the authors are around anymore and seeing
> | git log --grep "pic32" --author="@microchip.com" --pretty="%h%x09%an%x09%ad%x09%s" -n 2 --date=short
> | 5e972ac119c87   Conor Dooley    2026-02-24      clk: microchip: rename clk-core to clk-pic32
> | a726f1d2dd4fe   Purna Chandra Mandal    2016-06-02      MIPS: pic32mzda: Fix linker error for pic32_get_pbclk()
> is bad omen.

Yea, that's not a good sign. No objections from me.

Brian


      reply	other threads:[~2026-02-24 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 23:51 [PATCH 0/3] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2026-02-22 23:51 ` [PATCH 1/3] clk: microchip: core: update to use div64_ul() instead of do_div() Brian Masney
2026-02-23  9:09   ` David Laight
2026-02-24 16:56     ` Brian Masney
2026-02-24 22:50       ` David Laight
2026-02-22 23:51 ` [PATCH 2/3] clk: microchip: core: change asm nop calls to nop() Brian Masney
2026-02-22 23:51 ` [PATCH 3/3] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2026-02-24 17:10 ` [PATCH 0/3] " Conor Dooley
2026-02-24 17:27   ` Brian Masney
2026-02-24 17:36     ` Conor Dooley
2026-02-24 17:43       ` Brian Masney [this message]

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=aZ3jNaDR5eaCtX7p@redhat.com \
    --to=bmasney@redhat.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 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.