From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] pwm: tegra: Check for match_data being NULL
Date: Wed, 30 Sep 2026 19:05:31 +0200 [thread overview]
Message-ID: <ar1AKd2_V8FX_3V1@monoceros> (raw)
In-Reply-To: <ar0JBTAxcXVmTx1b@orome>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
Hello Thierry,
On Wed, Sep 30, 2026 at 03:14:35PM +0200, Thierry Reding wrote:
> On Wed, Sep 30, 2026 at 01:55:59PM +0200, Uwe Kleine-König wrote:
> > On Tue, Sep 22, 2026 at 12:06:14PM +0200, Thierry Reding wrote:
> > > I have a prototype patch that I'm going to send out shortly (after
> > > testing that it actually works). The problem ended up being that the
> > > driver_override is a device attribute, so there's no good way to drop it
> > > based on a driver flag.
> >
> > Did you see that I sent such a patch already.
> > https://lore.kernel.org/lkml/0f7446324f6a0c8f0153d6532d92a6eeecd6a308.1790612298.git.u.kleine-koenig@baylibre.com/ .
> > You were on Cc:, I thought this to be enough to make you aware and
> > didn't mention it in this thread here.
> >
> > I hope to not have provoked much duplicate work.
>
> Well, from the looks of it you ended up hijacking my earlier attempt
> while it was being discussed. It's customary to ask before you do so,
> specifically in order to avoid duplication of work. Or at least answer
> on the original thread that you plan to take this in a different
> direction so that people know what's going on.
Yeah, sorry about that. On that other thread where we were discussing
taints in context of driver_overrides the topics overlapped, so my idea
was to get all the suggestions into a single place. It seems I failed to
make you notice that in time. Mea culpa.
> Anyway, I was still waiting for any conclusions on the original thread
> and didn't spend any more time revisiting my original series, so no harm
> done.
😅
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-30 17:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 14:33 [PATCH v2 0/3] pwm: tegra: Cleanups and .get_state() Uwe Kleine-König
2026-09-18 14:33 ` [PATCH v2 1/3] pwm: tegra: Make use of dev_err_probe() Uwe Kleine-König
2026-09-21 9:38 ` Thierry Reding
2026-09-21 12:46 ` Uwe Kleine-König
2026-09-21 16:14 ` Thierry Reding
2026-09-18 14:33 ` [PATCH v2 2/3] pwm: tegra: Check for match_data being NULL Uwe Kleine-König
2026-09-21 9:47 ` Thierry Reding
2026-09-21 14:34 ` Uwe Kleine-König
2026-09-21 16:24 ` Thierry Reding
2026-09-21 20:10 ` Uwe Kleine-König
2026-09-22 8:33 ` Uwe Kleine-König
2026-09-22 10:06 ` Thierry Reding
2026-09-30 11:55 ` Uwe Kleine-König
2026-09-30 13:14 ` Thierry Reding
2026-09-30 17:05 ` Uwe Kleine-König [this message]
2026-09-18 14:33 ` [PATCH v2 3/3] pwm: tegra: Implement .get_state() Uwe Kleine-König
2026-09-21 10:18 ` Thierry Reding
2026-09-21 14:26 ` Uwe Kleine-König
2026-09-22 10:07 ` Thierry Reding
2026-09-30 9:54 ` Uwe Kleine-König
2026-09-30 10:29 ` Thierry Reding
2026-09-21 10:22 ` [PATCH v2 0/3] pwm: tegra: Cleanups and .get_state() Thierry Reding
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=ar1AKd2_V8FX_3V1@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=p.zabel@pengutronix.de \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®