From: Wolfram Sang <wsa@the-dreams.de>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: Brendan Higgins <brendanhiggins@google.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
James Feist <james.feist@linux.intel.com>,
Vernon Mauery <vernon.mauery@linux.intel.com>
Subject: Re: [PATCH] i2c: aspeed: Add multi-master use case support
Date: Mon, 11 Feb 2019 19:16:58 +0100 [thread overview]
Message-ID: <20190211181658.u55ggc2xi4nsxxvy@katana> (raw)
In-Reply-To: <d26a95ac-41ab-91eb-bbae-e4143235e531@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 108 bytes --]
> Can you please apply above changes on top of this patch? Or I can submit
> v2 with it.
Please send v2.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
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: linux-aspeed@lists.ozlabs.org,
James Feist <james.feist@linux.intel.com>,
Andrew Jeffery <andrew@aj.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
openbmc@lists.ozlabs.org,
Brendan Higgins <brendanhiggins@google.com>,
linux-kernel@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Joel Stanley <joel@jms.id.au>,
Vernon Mauery <vernon.mauery@linux.intel.com>,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: aspeed: Add multi-master use case support
Date: Mon, 11 Feb 2019 19:16:58 +0100 [thread overview]
Message-ID: <20190211181658.u55ggc2xi4nsxxvy@katana> (raw)
In-Reply-To: <d26a95ac-41ab-91eb-bbae-e4143235e531@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 108 bytes --]
> Can you please apply above changes on top of this patch? Or I can submit
> v2 with it.
Please send v2.
[-- 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:[~2019-02-11 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 19:39 [PATCH] i2c: aspeed: Add multi-master use case support Jae Hyun Yoo
2019-01-16 19:39 ` Jae Hyun Yoo
2019-01-31 18:20 ` Jae Hyun Yoo
2019-01-31 18:20 ` Jae Hyun Yoo
2019-02-07 19:48 ` Brendan Higgins
2019-02-07 19:48 ` Brendan Higgins
2019-02-07 19:48 ` Brendan Higgins
2019-02-08 21:48 ` Wolfram Sang
2019-02-08 21:48 ` Wolfram Sang
2019-02-11 18:09 ` Jae Hyun Yoo
2019-02-11 18:09 ` Jae Hyun Yoo
2019-02-11 18:16 ` Wolfram Sang [this message]
2019-02-11 18:16 ` Wolfram Sang
2019-02-11 18:29 ` Jae Hyun Yoo
2019-02-11 18:29 ` Jae Hyun Yoo
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=20190211181658.u55ggc2xi4nsxxvy@katana \
--to=wsa@the-dreams.de \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=james.feist@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.intel.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.