From: Peter Rosin <peda@axentia.se>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 2/2] i2c: move locking operations to their own struct
Date: Wed, 24 Aug 2016 09:47:19 +0200 [thread overview]
Message-ID: <4ff4bdab-a322-8cf2-aec8-bfd4ae4c2f34@axentia.se> (raw)
In-Reply-To: <20160823211600.GF20872@katana>
On 2016-08-23 23:16, Wolfram Sang wrote:
> On Fri, Jul 29, 2016 at 10:17:57AM +0200, Peter Rosin wrote:
>> This makes it trivial to constify them, so do that.
>>
>> Signed-off-by: Peter Rosin <peda@axentia.se>
>
> Looks good. Could you rebase to i2c/for-next?
Right, no problem!
Cheers,
Peter
The following changes since commit 00f0ea70d2b82b7d7afeb1bdedc9169eb8ea6675:
eeprom: at24: check if the chip is functional in probe() (2016-08-22 08:19:58 +0200)
are available in the git repository at:
https://github.com/peda-r/i2c-mux.git i2c-lock-op
for you to fetch changes up to 4b42b8c2e3233671e49deee71458edb6737a38bf:
i2c: move locking operations to their own struct (2016-08-24 06:38:58 +0200)
----------------------------------------------------------------
Peter Rosin (2):
i2c: add i2c_trylock_bus wrapper, use it
i2c: move locking operations to their own struct
drivers/i2c/i2c-core.c | 15 +++++++++------
drivers/i2c/i2c-mux.c | 29 ++++++++++++++++++-----------
include/linux/i2c.h | 37 +++++++++++++++++++++++++++++++------
3 files changed, 58 insertions(+), 23 deletions(-)
next prev parent reply other threads:[~2016-08-24 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 8:17 [PATCH 0/2] i2c: move adapter locking ops to struct, constify Peter Rosin
2016-07-29 8:17 ` [PATCH 1/2] i2c: add i2c_trylock_bus wrapper, use it Peter Rosin
2016-08-25 16:04 ` Wolfram Sang
2016-07-29 8:17 ` [PATCH 2/2] i2c: move locking operations to their own struct Peter Rosin
2016-08-23 21:16 ` Wolfram Sang
2016-08-24 7:47 ` Peter Rosin [this message]
2016-08-25 16:05 ` 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=4ff4bdab-a322-8cf2-aec8-bfd4ae4c2f34@axentia.se \
--to=peda@axentia.se \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®