public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux-i3c@lists.infradead.org,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions < 1.1
Date: Sun, 23 Jun 2024 00:35:20 +0200	[thread overview]
Message-ID: <202406222235206676ddeb@mail.local> (raw)
In-Reply-To: <171909557751.2164405.18080145631407814648.b4-ty@bootlin.com>

On 23/06/2024 00:34:01+0200, Alexandre Belloni wrote:
> On Fri, 14 Jun 2024 17:02:08 +0300, Jarkko Nikula wrote:
> > I was wrong about the TABLE_SIZE field description in the
> > commit 0676bfebf576 ("i3c: mipi-i3c-hci: Fix DAT/DCT entry sizes").
> > 
> > For the MIPI I3C HCI versions 1.0 and earlier the TABLE_SIZE field in
> > the registers DAT_SECTION_OFFSET and DCT_SECTION_OFFSET is indeed defined
> > in DWORDs and not number of entries like it is defined in later versions.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/1] i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions < 1.1
>       https://git.kernel.org/abelloni/c/17bebfeab08b
> 

Obviously, v2 is the one that has been applied...

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

      reply	other threads:[~2024-06-22 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 14:02 [PATCH] i3c: mipi-i3c-hci: Fix number of DAT/DCT entries for HCI versions < 1.1 Jarkko Nikula
2024-06-14 14:14 ` Greg KH
2024-06-22 22:34 ` Alexandre Belloni
2024-06-22 22:35   ` Alexandre Belloni [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=202406222235206676ddeb@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=stable@vger.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