All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: linux-sh@vger.kernel.org, "Magnus Damm" <magnus.damm@gmail.com>,
	"Simon Horman" <horms@verge.net.au>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: [PATCH v2 0/4] i2c: slave: API updates
Date: Mon, 23 Mar 2015 08:26:35 +0000	[thread overview]
Message-ID: <1427099199-3628-1-git-send-email-wsa@the-dreams.de> (raw)

So, after some more thoughts and people using the slave framework, some API
updates seemed in place. Also, the documentation is now here. Please read the
patch description for details. Thanks to all people joining the discussion,
especially Uwe and Geert!

Changes since V1:

* added acks, except for patch 2 which has too many changes to keep them IMO
* reworded/updated the issues found in patch 2
* added patch 4

Wolfram Sang (4):
  i2c: slave: rework the slave API
  Documentation: i2c: describe the new slave mode
  i2c: slave: add documentation for i2c-slave-eeprom
  i2c: slave-eeprom: add more info when to increase the pointer

 Documentation/i2c/slave-eeprom-backend |  14 +++
 Documentation/i2c/slave-interface      | 179 +++++++++++++++++++++++++++++++++
 Documentation/i2c/summary              |   4 -
 drivers/i2c/busses/i2c-rcar.c          |  10 +-
 drivers/i2c/i2c-slave-eeprom.c         |  18 ++--
 include/linux/i2c.h                    |   8 +-
 6 files changed, 213 insertions(+), 20 deletions(-)
 create mode 100644 Documentation/i2c/slave-eeprom-backend
 create mode 100644 Documentation/i2c/slave-interface

-- 
2.1.4


WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: linux-sh@vger.kernel.org, "Magnus Damm" <magnus.damm@gmail.com>,
	"Simon Horman" <horms@verge.net.au>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: [PATCH v2 0/4] i2c: slave: API updates
Date: Mon, 23 Mar 2015 09:26:35 +0100	[thread overview]
Message-ID: <1427099199-3628-1-git-send-email-wsa@the-dreams.de> (raw)

So, after some more thoughts and people using the slave framework, some API
updates seemed in place. Also, the documentation is now here. Please read the
patch description for details. Thanks to all people joining the discussion,
especially Uwe and Geert!

Changes since V1:

* added acks, except for patch 2 which has too many changes to keep them IMO
* reworded/updated the issues found in patch 2
* added patch 4

Wolfram Sang (4):
  i2c: slave: rework the slave API
  Documentation: i2c: describe the new slave mode
  i2c: slave: add documentation for i2c-slave-eeprom
  i2c: slave-eeprom: add more info when to increase the pointer

 Documentation/i2c/slave-eeprom-backend |  14 +++
 Documentation/i2c/slave-interface      | 179 +++++++++++++++++++++++++++++++++
 Documentation/i2c/summary              |   4 -
 drivers/i2c/busses/i2c-rcar.c          |  10 +-
 drivers/i2c/i2c-slave-eeprom.c         |  18 ++--
 include/linux/i2c.h                    |   8 +-
 6 files changed, 213 insertions(+), 20 deletions(-)
 create mode 100644 Documentation/i2c/slave-eeprom-backend
 create mode 100644 Documentation/i2c/slave-interface

-- 
2.1.4


             reply	other threads:[~2015-03-23  8:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  8:26 Wolfram Sang [this message]
2015-03-23  8:26 ` [PATCH v2 0/4] i2c: slave: API updates Wolfram Sang
2015-03-23  8:26 ` [PATCH v2 1/4] i2c: slave: rework the slave API Wolfram Sang
2015-03-23  8:26   ` Wolfram Sang
     [not found] ` <1427099199-3628-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-23  8:26   ` [PATCH v2 2/4] Documentation: i2c: describe the new slave mode Wolfram Sang
2015-03-23  8:26     ` Wolfram Sang
     [not found]     ` <1427099199-3628-3-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-23  8:45       ` Uwe Kleine-König
2015-03-23  8:45         ` Uwe Kleine-König
     [not found]         ` <20150323084510.GL5664-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-03-23  9:04           ` Wolfram Sang
2015-03-23  9:04             ` Wolfram Sang
2015-04-01 12:17       ` Geert Uytterhoeven
2015-04-01 12:17         ` Geert Uytterhoeven
2015-04-02  3:38         ` Wolfram Sang
2015-04-02  3:38           ` Wolfram Sang
2015-03-23  8:26   ` [PATCH v2 3/4] i2c: slave: add documentation for i2c-slave-eeprom Wolfram Sang
2015-03-23  8:26     ` Wolfram Sang
2015-03-23  8:26   ` [PATCH v2 4/4] i2c: slave-eeprom: add more info when to increase the pointer Wolfram Sang
2015-03-23  8:26     ` Wolfram Sang
     [not found]     ` <1427099199-3628-5-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-03-23  8:32       ` Uwe Kleine-König
2015-03-23  8:32         ` Uwe Kleine-König
2015-03-27  8:55   ` [PATCH v2 0/4] i2c: slave: API updates Wolfram Sang
2015-03-27  8:55     ` 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=1427099199-3628-1-git-send-email-wsa@the-dreams.de \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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.