From: Wolfram Sang <wsa@kernel.org>
To: Jan Bottorff <janb@os.amperecomputing.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] i2c: designware: Fix corrupted memory seen in the ISR
Date: Wed, 15 Nov 2023 13:52:28 -0500 [thread overview]
Message-ID: <ZVUTbJfQXbXi9V2c@shikoro> (raw)
In-Reply-To: <16668165-adcd-4cd6-8c50-83b992f8e880@os.amperecomputing.com>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
> Any chance we could get the "Cc: stable@vger.kernel.org" tag added to this
> patch? More than one large cloud company would like to see this in the
Well, no, it is already pushed out...
> stable kernel, as it significantly improves the reliability of IPMI
> transactions on platforms that use i2c for this communication.
... but with that commit desc it will surely be backported nonetheless.
If all fails, it can be manually requested to go to stable, but I am
sure this will not be needed.
> Sorry for not including this tag in the submission.
No worries.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-11-15 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 3:19 [PATCH v4] i2c: designware: Fix corrupted memory seen in the ISR Jan Bottorff
2023-11-09 18:00 ` Andy Shevchenko
2023-11-10 12:02 ` Jarkko Nikula
2023-11-13 1:54 ` Wolfram Sang
2023-11-13 9:48 ` Serge Semin
2023-11-13 9:51 ` Wolfram Sang
2023-11-13 10:01 ` Serge Semin
2023-11-15 18:25 ` Jan Bottorff
2023-11-15 18:52 ` 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=ZVUTbJfQXbXi9V2c@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fancer.lancer@gmail.com \
--cc=janb@os.amperecomputing.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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