From: Wolfram Sang <wsa@the-dreams.de>
To: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
me@jue.yt, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH v5 0/3] i2c: at91: slave mode support
Date: Sun, 24 Mar 2019 22:44:09 +0100 [thread overview]
Message-ID: <20190324214409.GA6934@kunai> (raw)
In-Reply-To: <20190222092522.4913-1-ludovic.desroches@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
On Fri, Feb 22, 2019 at 10:25:19AM +0100, Ludovic Desroches wrote:
> [Ludovic Desroches: see Changes section]
>
> Based on the discussion we had on the i2c-linux list [1], I wrote a patch for
> AT91 hardware and tried to fulfill the Linux I2C slave interface description
> [2] as good as possible. This enables aforementioned hardware to act as an I2C
> slave that can be accessed by a remote I2C master.
After this was successfully checked by buildbot in a seperate branch:
Applied to for-next, thanks!
[-- 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: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
me@jue.yt, linux-i2c@vger.kernel.org,
andriy.shevchenko@linux.intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/3] i2c: at91: slave mode support
Date: Sun, 24 Mar 2019 22:44:09 +0100 [thread overview]
Message-ID: <20190324214409.GA6934@kunai> (raw)
In-Reply-To: <20190222092522.4913-1-ludovic.desroches@microchip.com>
[-- Attachment #1.1: Type: text/plain, Size: 520 bytes --]
On Fri, Feb 22, 2019 at 10:25:19AM +0100, Ludovic Desroches wrote:
> [Ludovic Desroches: see Changes section]
>
> Based on the discussion we had on the i2c-linux list [1], I wrote a patch for
> AT91 hardware and tried to fulfill the Linux I2C slave interface description
> [2] as good as possible. This enables aforementioned hardware to act as an I2C
> slave that can be accessed by a remote I2C master.
After this was successfully checked by buildbot in a seperate branch:
Applied to for-next, thanks!
[-- 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-03-24 21:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 9:25 [PATCH v5 0/3] i2c: at91: slave mode support Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` [PATCH v5 1/3] i2c: at91: segregate master mode specific code from probe and init func Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` [PATCH v5 2/3] i2c: at91: split driver into core and master file Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-25 10:34 ` Andy Shevchenko
2019-02-25 10:34 ` Andy Shevchenko
2019-02-22 9:25 ` [PATCH v5 3/3] i2c: at91: added slave mode support Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-22 9:25 ` Ludovic Desroches
2019-02-25 10:24 ` [PATCH v5 0/3] i2c: at91: " Andy Shevchenko
2019-02-25 10:24 ` Andy Shevchenko
2019-03-24 21:44 ` Wolfram Sang [this message]
2019-03-24 21:44 ` 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=20190324214409.GA6934@kunai \
--to=wsa@the-dreams.de \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=me@jue.yt \
--cc=nicolas.ferre@microchip.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.