From: Ulrich Hecht <uli@fpond.eu>
To: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Pavel Machek <pavel@denx.de>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Ulrich Hecht <uli@kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: RE: [PATCH 5.10.y-cip] gpio: rcar: Use raw_spinlock to protect register access
Date: Sat, 23 Aug 2025 15:05:18 +0200 (CEST) [thread overview]
Message-ID: <2044519855.2076.1755954318987@webmail.strato.de> (raw)
In-Reply-To: <OSZPR01MB70191CC24A9467931A33E42CAA32A@OSZPR01MB7019.jpnprd01.prod.outlook.com>
> On 08/21/2025 7:05 PM CEST Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:
> Agreed, I've a now submitted this patch to stable [0].
>
> > Then we'll backport it to 4.19 and 4.4, provided it applies there, but I
> > assume it does? (If not, you should re-send those versions after 5.10-
> > stable accepts the patch).
> >
> For 4.4 and 4.19 the patch doesn't apply cleanly. I will resend the 4.4 and 4.19
> Versions once the patch [0] hits stable.
Since landing the patch in 5.10 is not a guarantee that it will show up in 5.4 (which is the upstream for 4.4 and 4.19 ATM), I'm inclined to pick these up as posted for 4.4 and 4.19, unless there is a compelling reason not to.
CU
Uli
next prev parent reply other threads:[~2025-08-23 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 14:13 [PATCH 5.10.y-cip] gpio: rcar: Use raw_spinlock to protect register access Lad Prabhakar
2025-08-21 10:41 ` Pavel Machek
2025-08-21 17:05 ` Prabhakar Mahadev Lad
2025-08-23 13:05 ` Ulrich Hecht [this message]
2025-08-24 18:44 ` Pavel Machek
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=2044519855.2076.1755954318987@webmail.strato.de \
--to=uli@fpond.eu \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=uli@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