From: Guenter Roeck <linux@roeck-us.net>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] i2c: aspeed: Acknowledge most interrupts early in interrupt handler
Date: Mon, 17 Sep 2018 11:48:09 -0700 [thread overview]
Message-ID: <20180917184809.GA16057@roeck-us.net> (raw)
In-Reply-To: <037b4cf8-5dfa-d554-b126-a2462ba9c803@linux.intel.com>
On Mon, Sep 17, 2018 at 10:16:59AM -0700, Jae Hyun Yoo wrote:
> On 9/17/2018 9:34 AM, Wolfram Sang wrote:
> >
> >>Looks good to me. Thanks! :)
> >>
> >>Acked-by: Jae Hyun Yoo <jae.hyun.yoo@linux.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?
> >
>
> 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.
>
Yes, sorry, I should have tagged the patch as for-next.
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: "Wolfram Sang" <wsa@the-dreams.de>,
"Brendan Higgins" <brendanhiggins@google.com>,
linux-aspeed@lists.ozlabs.org, "Andrew Jeffery" <andrew@aj.id.au>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
"Cédric Le Goater" <clg@kaod.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: aspeed: Acknowledge most interrupts early in interrupt handler
Date: Mon, 17 Sep 2018 11:48:09 -0700 [thread overview]
Message-ID: <20180917184809.GA16057@roeck-us.net> (raw)
In-Reply-To: <037b4cf8-5dfa-d554-b126-a2462ba9c803@linux.intel.com>
On Mon, Sep 17, 2018 at 10:16:59AM -0700, Jae Hyun Yoo wrote:
> On 9/17/2018 9:34 AM, Wolfram Sang wrote:
> >
> >>Looks good to me. Thanks! :)
> >>
> >>Acked-by: Jae Hyun Yoo <jae.hyun.yoo@linux.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?
> >
>
> 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.
>
Yes, sorry, I should have tagged the patch as for-next.
Guenter
next prev parent reply other threads:[~2018-09-17 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 3:30 [PATCH] i2c: aspeed: Acknowledge most interrupts early in interrupt handler Guenter Roeck
2018-09-14 3:30 ` Guenter Roeck
2018-09-14 16:28 ` Jae Hyun Yoo
2018-09-14 16:28 ` Jae Hyun Yoo
2018-09-17 16:34 ` Wolfram Sang
2018-09-17 16:34 ` Wolfram Sang
2018-09-17 17:16 ` Jae Hyun Yoo
2018-09-17 17:16 ` Jae Hyun Yoo
2018-09-17 18:48 ` Guenter Roeck [this message]
2018-09-17 18:48 ` Guenter Roeck
2018-09-18 1:11 ` Joel Stanley
2018-09-18 1:11 ` Joel Stanley
2018-09-18 1:28 ` Brendan Higgins
2018-09-18 1:28 ` Brendan Higgins
2018-09-24 21:45 ` Wolfram Sang
2018-09-24 21:45 ` 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=20180917184809.GA16057@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-aspeed@lists.ozlabs.org \
/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.