mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andrew Davis <afd@ti.com>, Peter Rosin <peda@axentia.se>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	<linux-kernel@vger.kernel.org>,
	"Rob Herring (Arm)" <robh@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] mux: mmio: Do not use syscon helper to build regmap
Date: Fri, 24 Jan 2025 08:33:01 -0600	[thread overview]
Message-ID: <20250124143301.om526lwkvcw2hmq5@shaping> (raw)
In-Reply-To: <2025012446-unturned-frugality-7a20@gregkh>

On 06:26-20250124, Greg Kroah-Hartman wrote:
[...]
> > Greg, Peter,
> > 
> > This is part of the fixes TI K3 platforms boot issues reported in
> > https://lore.kernel.org/all/b2413460-ec8b-4c77-99b8-4c32b262439a@ti.com/
> > on the latest linus master v6.13-5001-gd0d106a2bd21 + linux
> > next-20250123
> > 
> > Total set of patches tested with:
> > https://lore.kernel.org/all/20250119182121.3956546-1-vaishnav.a@ti.com/
> > https://lore.kernel.org/r/20250123181726.597144-1-afd@ti.com
> > https://lore.kernel.org/r/20250123181913.597304-1-afd@ti.com
> > https://lore.kernel.org/r/20250123182059.597491-1-afd@ti.com
> > https://lore.kernel.org/r/20250123182234.597665-1-afd@ti.com
> > 
> > Could we get this routed to master as fixes asap please to get a sane 6.14?
> 
> Our trees are of course closed right now due to the merge window, you
> know that :)

Yes, of course.

> 
> So we can take things after -rc1 is out, and route bugfixes for
> 6.14-final and new stuff for 6.15-rc1, like always.  It's hard to see
> that this is just a bugfix, but if it is, it needs a Fixes: tag at the
> very least, right?

I am not entirely sure which commit to use for fixes.

On one hand, we can use
https://lore.kernel.org/all/b2413460-ec8b-4c77-99b8-4c32b262439a@ti.com/
as the cause of the Fixes. Since, the change in behavior of the subsystem late
in the merge cycle caused this side effect, but, we could argue that
this patch fixes the subsystem for it's intended behavior and
unfortunately exposed issues in users of the syscon subsystem depending
on the "wrong" behavior.

OR

The code introduced long back which depended on the older syscon
behavior. but, then, we can argue that it was working fine at that
point.. and if we cherry-pick the fixup for stable, it is probably
inaccurate for the syscon behavior in older kernels?

Lee, Rob: Could you chime in with your suggestion?

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2025-01-24 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 18:20 Andrew Davis
2025-01-23 20:04 ` Nishanth Menon
2025-01-24  5:26   ` Greg Kroah-Hartman
2025-01-24 14:33     ` Nishanth Menon [this message]
2025-01-24 22:16     ` Nishanth Menon
2025-05-01 17:56 ` Krzysztof Kozlowski

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=20250124143301.om526lwkvcw2hmq5@shaping \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=robh@kernel.org \
    --cc=vigneshr@ti.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

all inboxes | Powered by JetHome®