public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Ulrich Hecht <uli@fpond.eu>
Cc: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"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: Sun, 24 Aug 2025 20:44:13 +0200	[thread overview]
Message-ID: <aKtdfcOn0vpmMYZf@duo.ucw.cz> (raw)
In-Reply-To: <2044519855.2076.1755954318987@webmail.strato.de>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hi!

> > 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.
>

I believe we should not take patches to 4.19-cip unless they are in
5.10-cip. Greg just took the patch to 5.10, so that really should not
be problem, but I'd be inclined to wait until it hits 5.10-cip.

Best regards,
								Pavel
-- 
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2025-08-24 18:46 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
2025-08-24 18:44       ` Pavel Machek [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=aKtdfcOn0vpmMYZf@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=uli@fpond.eu \
    --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