From: "wsa@kernel.org" <wsa@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shubhraj@xilinx.com" <shubhraj@xilinx.com>,
"michal.simek@amd.com" <michal.simek@amd.com>,
"marex@denx.de" <marex@denx.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>
Subject: Re: [PATCH] i2c: xiic: Don't try to handle more interrupt events after error
Date: Tue, 27 Jun 2023 23:25:18 +0200 [thread overview]
Message-ID: <ZJtTvleO7JURiBCQ@sai> (raw)
In-Reply-To: <71637721f64b877255264d36293208402ef1a873.camel@calian.com>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
> Just checking on this patch, was it merged? It shows accepted in
> Patchwork, but I'm not seeing it in the Git tree.
Sorry, it seems I forgot to apply it? I will make sure it will go in
this merge window now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "wsa@kernel.org" <wsa@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shubhraj@xilinx.com" <shubhraj@xilinx.com>,
"michal.simek@amd.com" <michal.simek@amd.com>,
"marex@denx.de" <marex@denx.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>
Subject: Re: [PATCH] i2c: xiic: Don't try to handle more interrupt events after error
Date: Tue, 27 Jun 2023 23:25:18 +0200 [thread overview]
Message-ID: <ZJtTvleO7JURiBCQ@sai> (raw)
In-Reply-To: <71637721f64b877255264d36293208402ef1a873.camel@calian.com>
[-- Attachment #1.1: Type: text/plain, Size: 214 bytes --]
> Just checking on this patch, was it merged? It shows accepted in
> Patchwork, but I'm not seeing it in the Git tree.
Sorry, it seems I forgot to apply it? I will make sure it will go in
this merge window now.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-27 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 18:25 [PATCH] i2c: xiic: Don't try to handle more interrupt events after error Robert Hancock
2023-06-06 18:25 ` Robert Hancock
2023-06-06 19:24 ` Andi Shyti
2023-06-06 19:24 ` Andi Shyti
2023-06-06 19:40 ` Robert Hancock
2023-06-06 19:40 ` Robert Hancock
2023-06-06 21:20 ` Andi Shyti
2023-06-06 21:20 ` Andi Shyti
2023-06-09 15:32 ` wsa
2023-06-09 15:32 ` wsa
2023-06-09 21:25 ` Andi Shyti
2023-06-09 21:25 ` Andi Shyti
2023-06-27 16:13 ` Robert Hancock
2023-06-27 16:13 ` Robert Hancock
2023-06-27 21:25 ` wsa [this message]
2023-06-27 21:25 ` wsa
2023-07-06 19:33 ` Wolfram Sang
2023-07-06 19:33 ` Wolfram Sang
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=ZJtTvleO7JURiBCQ@sai \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=michal.simek@amd.com \
--cc=robert.hancock@calian.com \
--cc=shubhraj@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.