All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Fitschen <me@jue.yt>
To: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] i2c: at91: added slave mode support
Date: Mon, 11 Dec 2017 10:25:00 +0100	[thread overview]
Message-ID: <20171211092459.GA6350@jfi-dev> (raw)
In-Reply-To: <20171203180231.GA2843@rfolt0960.corp.atmel.com>

Hi Ludovic,

thank you for your reply and sorry for the delayed response! I'm a little bit
busy atm, as well. So I won't be able to reproduce that before the next week. I
also want to try another I2C master: A wild Arduino Uno appeared on my desk ;)

Thank you for your support for bringing this to mainline!

Best regards
  Juergen

  reply	other threads:[~2017-12-11  9:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 17:21 [PATCH v2 0/3] i2c: at91: slave mode support Juergen Fitschen
2017-11-09 17:21 ` [PATCH v2 1/3] i2c: at91: segregate master mode specific code from probe and init func Juergen Fitschen
2017-11-09 17:22 ` [PATCH v2 2/3] i2c: at91: split driver into core and master file Juergen Fitschen
2017-11-09 17:22 ` [PATCH v2 3/3] i2c: at91: added slave mode support Juergen Fitschen
2017-12-03 18:02   ` Ludovic Desroches
2017-12-03 18:02     ` Ludovic Desroches
2017-12-11  9:25     ` Juergen Fitschen [this message]
2018-06-02 21:35   ` [v2,3/3] " Wolfram Sang
2018-07-09 15:15     ` Ludovic Desroches
2018-07-09 15:15       ` Ludovic Desroches
2018-07-09 15:51       ` Wolfram Sang
2018-07-10  8:42         ` Ludovic Desroches
2018-07-10  8:42           ` Ludovic Desroches
2018-07-12 21:48           ` Wolfram Sang
2018-07-12 21:56           ` Wolfram Sang
2018-07-13  6:37             ` Ludovic Desroches
2018-07-13  6:37               ` Ludovic Desroches

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=20171211092459.GA6350@jfi-dev \
    --to=me@jue.yt \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=wsa@the-dreams.de \
    /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.