From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 4/4] hwmon: ina209: move binding docs to proper place
Date: Sat, 08 Aug 2015 13:48:39 -0700 [thread overview]
Message-ID: <55C66B27.2070308@roeck-us.net> (raw)
In-Reply-To: <1439058636-3082-5-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
On 08/08/2015 11:30 AM, Wolfram Sang wrote:
> The I2C dir is not for I2C client devices! Move it to the proper folder.
>
> Signed-off-by: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
> Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Acked-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
next prev parent reply other threads:[~2015-08-08 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 18:30 [PATCH 0/4] i2c: move client binding docs to proper place Wolfram Sang
2015-08-08 18:30 ` [PATCH 1/4] rtc: bq32k: move " Wolfram Sang
[not found] ` <1439058636-3082-2-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 21:50 ` Pavel Machek
[not found] ` <1439058636-3082-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 18:30 ` [PATCH 2/4] hwmon: max6697: " Wolfram Sang
[not found] ` <1439058636-3082-3-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 20:47 ` Guenter Roeck
2015-08-08 18:30 ` [PATCH 3/4] hwmon: ina2xx: " Wolfram Sang
[not found] ` <1439058636-3082-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 20:48 ` Guenter Roeck
2015-08-08 18:30 ` [PATCH 4/4] hwmon: ina209: " Wolfram Sang
[not found] ` <1439058636-3082-5-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 20:48 ` Guenter Roeck [this message]
2015-08-09 7:09 ` [PATCH 0/4] i2c: move client " 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=55C66B27.2070308@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).