mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v4 4/5] i3c: mipi-i3c-hci: use parity8 helper instead of open coding it
Date: Wed, 8 Jan 2025 17:32:20 +0200	[thread overview]
Message-ID: <cbd9bbf3-843f-42ea-9651-c35071089210@linux.intel.com> (raw)
In-Reply-To: <Z3515cBvz3yChGoL@ninjato>

On 1/8/25 2:56 PM, Wolfram Sang wrote:
> 
>> Stable rules allow also cherry picking additional patches. To me picking
>> patch 1 and 4 sounds better than an intermediate fix since bug has been here
>> from the beginning. IMHO not so urgent than a regression.
> 
> Even then, doesn't that mean that the series needs to be applied
> upstream first before it can go to stable? How to describe the
> dependency commit id otherwise? Either Alexandre adds this when
> applying, or some interested party ;) sends a backport request to
> stable. Or am I missing something?
> 
Yes, the latter case was in my mind that whoever runs this driver on 
earlier stable kernel and has enough devices on the bus where previous 
code will calculate wrong can request the backport or at least be vocal 
about it :-)

I'd say backporting back to 9ad9a52cce28 ("i3c/master: introduce the 
mipi-i3c-hci driver") is also needless because driver needs other fixes 
in order to be really usable.

  reply	other threads:[~2025-01-08 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07  9:01 [PATCH v4 0/5] i3c: introduce and use generic parity helper Wolfram Sang
2025-01-07  9:01 ` [PATCH v4 1/5] bitops: add generic parity calculation for u8 Wolfram Sang
2025-01-07  9:02 ` [PATCH v4 2/5] hwmon: (spd5118) Use generic parity calculation Wolfram Sang
2025-01-07  9:02 ` [PATCH v4 3/5] i3c: dw: use parity8 helper instead of open coding it Wolfram Sang
2025-01-07  9:02 ` [PATCH v4 4/5] i3c: mipi-i3c-hci: " Wolfram Sang
2025-01-08 12:09   ` Jarkko Nikula
2025-01-08 12:56     ` Wolfram Sang
2025-01-08 15:32       ` Jarkko Nikula [this message]
2025-01-07  9:02 ` [PATCH v4 5/5] i3c: cdns: " Wolfram Sang
2025-01-08  7:23 ` [PATCH v4 0/5] i3c: introduce and use generic parity helper Wolfram Sang
2025-01-12 23:05 ` Alexandre Belloni

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=cbd9bbf3-843f-42ea-9651-c35071089210@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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®