Linux I2C development
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Mingyu Wang <25181214217@stu.xidian.edu.cn>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	w15303746062@163.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] i2c: i801: fix hardware state machine corruption in error path
Date: Wed, 29 Jul 2026 09:21:34 +0200	[thread overview]
Message-ID: <20260729092134.455c06a2@endymion> (raw)
In-Reply-To: <ca6fbfb1-1e08-4b4f-b823-8312327d5b38@stu.xidian.edu.cn>

Hi Andi, Mingyu,

On Wed, 24 Jun 2026 09:20:09 +0800, Mingyu Wang wrote:
> >> Fixes: 1f760b87e54c ("i2c: i801: Call i801_check_pre() from i801_access()")
> >> Cc: stable@vger.kernel.org # v6.3+  
> > Please, next time don't leave a blank space in the tag section.  
> I apologize for that; it was an oversight on my part. I'll be more 
> careful in future submissions.
> > The patch looks correct to me, although I'd have liked an ack
> > from Jean.
> >
> > I merged it to i2c/i2c-fixes.  
> 
> I understand.
> 
> If Jean has any concerns, I'm happy to provide a follow-up fix if needed.
> 
> I'll also keep an eye on the thread in case he comments.

No concerns, this v2 of the patch addresses all my comments from v1.
Thanks for applying this fix and sorry for not commenting earlier.

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2026-07-29  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  9:35 [PATCH v2] i2c: i801: fix hardware state machine corruption in error path w15303746062
2026-06-04 12:14 ` w15303746062
2026-06-08 20:01 ` [PATCH " Andi Shyti
2026-06-21  2:01   ` Mingyu Wang
2026-06-23 15:59 ` Andi Shyti
2026-06-24  1:20   ` Mingyu Wang
2026-07-29  7:21     ` Jean Delvare [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=20260729092134.455c06a2@endymion \
    --to=jdelvare@suse.de \
    --cc=25181214217@stu.xidian.edu.cn \
    --cc=andi.shyti@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=w15303746062@163.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