From: Wolfram Sang <wsa@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Jian Zhang <zhangjian.3032@bytedance.com>,
Tommy Huang <tommy_huang@aspeedtech.com>,
brendan.higgins@linux.dev, benh@kernel.crashing.org,
andrew@aj.id.au, zhangjian3032@gmail.com, yulei.sh@bytedance.com,
xiexinnan@bytedance.com,
"open list:ARM/ASPEED I2C DRIVER" <linux-i2c@vger.kernel.org>,
"moderated list:ARM/ASPEED I2C DRIVER" <openbmc@lists.ozlabs.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-aspeed@lists.ozlabs.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH] i2c: aspeed: Fix i2c bus hang in slave read
Date: Wed, 27 Sep 2023 08:18:05 +0200 [thread overview]
Message-ID: <ZRPJHQXLb0nPUjwF@ninjato> (raw)
In-Reply-To: <CACPK8XeO404ok+B+k4U_bdFE3yYebzT-UNcTqcHStJfEnDh6jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi Joel!
> Unfortunately, despite no acks from the maintainers, this patch has
> now been merged and backported to stable.
To explain my reasoning: given the list of unreviewed patches for
aspeed[1], I thought that the driver maintainers were busy or similar.
This happens all the time, so it would be no surprise. Andi is the
driver-comaintainer meanwhile, so an ack from him counts for me as well.
[1] http://patchwork.ozlabs.org/project/linux-i2c/list/?series=&submitter=&state=&q=aspeed&archive=&delegate=
> We should complete the fix, or revert it asap.
Agreed. We can always revert if you guys need more time fixing the issue
properly.
Thanks,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-09-27 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 7:21 [PATCH] i2c: aspeed: Fix i2c bus hang in slave read Jian Zhang
2023-09-22 6:47 ` Joel Stanley
2023-09-22 14:39 ` [External] " Jian Zhang
2023-09-27 2:42 ` Joel Stanley
2023-09-27 3:24 ` Tommy Huang
2023-09-27 6:18 ` Wolfram Sang [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=ZRPJHQXLb0nPUjwF@ninjato \
--to=wsa@kernel.org \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=brendan.higgins@linux.dev \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tommy_huang@aspeedtech.com \
--cc=xiexinnan@bytedance.com \
--cc=yulei.sh@bytedance.com \
--cc=zhangjian.3032@bytedance.com \
--cc=zhangjian3032@gmail.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