All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] i2c: aspeed: Acknowledge most interrupts early in interrupt handler
Date: Mon, 17 Sep 2018 18:34:01 +0200	[thread overview]
Message-ID: <20180917163401.GA1082@kunai> (raw)
In-Reply-To: <fbf54ca6-16b3-5e35-eac8-b3dab8118543@linux.intel.com>


> 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?

(and please quote only relevat parts of a message when replying)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20180917/7cb37b53/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	"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 18:34:01 +0200	[thread overview]
Message-ID: <20180917163401.GA1082@kunai> (raw)
In-Reply-To: <fbf54ca6-16b3-5e35-eac8-b3dab8118543@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 338 bytes --]


> 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?

(and please quote only relevat parts of a message when replying)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-17 16:34 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 [this message]
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
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=20180917163401.GA1082@kunai \
    --to=wsa@the-dreams.de \
    --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.