[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <037b4cf8-5dfa-d554-b126-a2462ba9c803@linux.intel.com>
Date: Mon, 17 Sep 2018 10:16:59 -0700
From: Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Guenter Roeck <linux@...ck-us.net>,
Brendan Higgins <brendanhiggins@...gle.com>,
linux-aspeed@...ts.ozlabs.org, Andrew Jeffery <andrew@...id.au>,
openbmc@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Cédric Le Goater <clg@...d.org>,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH] i2c: aspeed: Acknowledge most interrupts early in
interrupt handler
On 9/17/2018 9:34 AM, Wolfram Sang wrote:
>
>> Looks good to me. Thanks! :)
>>
>> Acked-by: Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>
>
> Does that mean I need to revert "[PATCH i2c-next v6] i2c: aspeed: Handle
> master/slave combined irq events properly" in i2c/for-next? And apply
> this to i2c/for-current?
>
> (and please quote only relevat parts of a message when replying)
>
No need to revert "[PATCH i2c-next v6] i2c: aspeed: Handle master/slave
combined irq events properly". This patch should be applied on top of
the patch.
(Will reduce message size when replying. Thanks!)
Jae
Powered by blists - more mailing lists