Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Abdurrahman Hussain <abdurrahman@nexthop.ai>
Cc: Michal Simek <michal.simek@amd.com>,
	 Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Raviteja Narayanam <raviteja.narayanam@xilinx.com>,
	 Wolfram Sang <wsa@kernel.org>,
	Manikanta Guntupalli <manikanta.guntupalli@amd.com>,
	 Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
	linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
	 linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [SPAM] [PATCH v7 0/3] i2c: xiic: fix SMBus block read and PEC support
Date: Sun, 27 Sep 2026 13:40:35 +0200	[thread overview]
Message-ID: <arkAZJEJTtNsCjmF@zenone.zhora.eu> (raw)
In-Reply-To: <20260924-i2c-xiic-v7-0-df7e752332ef@nexthop.ai>

Hi Abdurraham,

> Abdurrahman Hussain (3):
>       i2c: xiic: preserve PEC byte length in SMBus block read setup
>       i2c: xiic: defer RX_FULL until all trailing bytes are in FIFO
>       i2c: xiic: don't clobber msg->len to signal block-read completion

pushed to i2c/i2c-fixes-2.

Thanks,
Andi


  parent reply	other threads:[~2026-09-27 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  0:10 [PATCH v7 0/3] i2c: xiic: fix SMBus block read and PEC support Abdurrahman Hussain
2026-09-25  0:10 ` [PATCH v7 1/3] i2c: xiic: preserve PEC byte length in SMBus block read setup Abdurrahman Hussain
2026-09-25  0:10 ` [PATCH v7 2/3] i2c: xiic: defer RX_FULL until all trailing bytes are in FIFO Abdurrahman Hussain
2026-09-25  0:10 ` [PATCH v7 3/3] i2c: xiic: don't clobber msg->len to signal block-read completion Abdurrahman Hussain
2026-09-27 11:40 ` Andi Shyti [this message]
2026-09-27 18:48   ` [SPAM] [PATCH v7 0/3] i2c: xiic: fix SMBus block read and PEC support Abdurrahman Hussain

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=arkAZJEJTtNsCjmF@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=abdurrahman@nexthop.ai \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manikanta.guntupalli@amd.com \
    --cc=michal.simek@amd.com \
    --cc=raviteja.narayanam@xilinx.com \
    --cc=shubhrajyoti.datta@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@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