From: Evgeniy Polyakov <zbr@ioremap.net>
To: Jan Kandziora <jjj@gmx.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Linux-I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] wire: export w1_touch_bit
Date: Sun, 27 Aug 2017 10:21:30 +0300 [thread overview]
Message-ID: <1192111503818490@web4g.yandex.ru> (raw)
In-Reply-To: <20170719201409.5968-1-jjj@gmx.de>
Hi
19.07.2017, 23:14, "Jan Kandziora" <jjj@gmx.de>:
> The w1_ds28e17 driver from the next part of this patch needs to emit
> single-bit read timeslots to the DS28E17. The w1 subsystem already
> has this function but it is not exported outside drivers/w1/w1_io.c
>
> This subpatch exports the w1_touch_bit symbol with EXPORT_SYMBOL_GPL,
> same as the other exported symbols in drivers/w1/w1_io.c
>
> May be also useful later for writing drivers for other Onewire chips
> which do single-bit communication.
>
> Signed-off-by: Jan Kandziora <jjj@gmx.de>
> ---
> Changes in v4 against v3 in this subpatch:
> - adapted to linux-4.12.0
Greg, please pull this patch series into the tree, it has been adopted to the latest vanilla tree to date.
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
next prev parent reply other threads:[~2017-08-27 7:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 20:14 [PATCH v4 1/2] wire: export w1_touch_bit Jan Kandziora
2017-07-19 20:14 ` [PATCH v4 2/2] add w1_ds28e17 driver for the DS28E17 Onewire to I2C master bridge Jan Kandziora
2017-09-05 13:19 ` Evgeniy Polyakov
2017-09-18 10:57 ` GregKH
2017-09-18 13:05 ` Jan Kandziora
2017-08-27 7:21 ` Evgeniy Polyakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 13:03 [PATCH v4 1/2] wire: export w1_touch_bit Jan Kandziora
2017-09-18 14:19 ` GregKH
2017-09-18 19:34 ` Jan Kandziora
2017-09-18 19:37 ` GregKH
2017-09-20 21:54 ` Jan Kandziora
2017-07-10 22:59 Jan Kandziora
2017-07-13 15:13 ` Evgeniy Polyakov
2017-07-17 14:47 ` Greg Kroah-Hartman
2017-07-17 22:56 ` Jan Kandziora
2017-07-18 4:59 ` Greg Kroah-Hartman
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=1192111503818490@web4g.yandex.ru \
--to=zbr@ioremap.net \
--cc=jjj@gmx.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.