public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: wsa@kernel.org, linux-i2c@vger.kernel.org,
	Yicong Yang <yangyicong@huawei.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	yangyicong@hisilicon.com, f.fangjian@huawei.com,
	linuxarm@huawei.com
Subject: Re: [PATCH] i2c: hisi: Only handle the interrupt of the driver's transfer
Date: Wed,  9 Aug 2023 22:43:00 +0200	[thread overview]
Message-ID: <169161372323.1170957.8776252018393427661.b4-ty@kernel.org> (raw)
In-Reply-To: <20230801124625.63587-1-yangyicong@huawei.com>

Hi

On Tue, 01 Aug 2023 20:46:25 +0800, Yicong Yang wrote:
> The controller may be shared with other port, for example the firmware.
> Handle the interrupt from other sources will cause crash since some
> data are not initialized. So only handle the interrupt of the driver's
> transfer and discard others.
> 
> 

With the Fixes tag added, applied to i2c/andi-for-current on

https://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Please note that this patch may still undergo further evaluation
and the final decision will be made in collaboration with
Wolfram.

Thank you,
Andi

Patches applied
===============
[1/1] i2c: hisi: Only handle the interrupt of the driver's transfer
      commit: 9a5adaf694f5ae8ba8f8e6178d01b5950fc7222a

  parent reply	other threads:[~2023-08-09 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 12:46 [PATCH] i2c: hisi: Only handle the interrupt of the driver's transfer Yicong Yang
2023-08-01 22:15 ` Andi Shyti
2023-08-02  2:39   ` Yicong Yang
2023-08-04 23:30     ` Andi Shyti
2023-08-08 13:11       ` Yicong Yang
2023-08-09 20:08         ` Andi Shyti
2023-08-09 20:43 ` Andi Shyti [this message]
2023-08-14 13:42 ` Wolfram Sang
2023-08-15  8:41   ` Geert Uytterhoeven

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=169161372323.1170957.8776252018393427661.b4-ty@kernel.org \
    --to=andi.shyti@kernel.org \
    --cc=f.fangjian@huawei.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=wsa@kernel.org \
    --cc=yangyicong@hisilicon.com \
    --cc=yangyicong@huawei.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