From: Lars-Peter Clausen <lars@metafoo.de>
To: Martin Kepplinger <martink@posteo.de>,
Michael.Hennerich@analog.com, jic23@kernel.org, knaack.h@gmx.de,
pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: dac: ad5504: leave sysfs naming to the core
Date: Fri, 25 Sep 2015 11:51:00 +0200 [thread overview]
Message-ID: <56051904.3060804@metafoo.de> (raw)
In-Reply-To: <1443174310-20428-1-git-send-email-martink@posteo.de>
On 09/25/2015 11:45 AM, Martin Kepplinger wrote:
> This shouldn't actually change anything since the core calls the events
> sysfs folder "events" anyways.
>
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
Acked-by: Lars-Peter Clausen <lars@metafoo.de>
Thanks.
next prev parent reply other threads:[~2015-09-25 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 9:45 [PATCH 1/3] iio: dac: ad5504: leave sysfs naming to the core Martin Kepplinger
2015-09-25 9:46 ` Martin Kepplinger
2015-09-25 9:51 ` Lars-Peter Clausen [this message]
2015-09-27 13:57 ` Jonathan Cameron
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=56051904.3060804@metafoo.de \
--to=lars@metafoo.de \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=pmeerw@pmeerw.net \
/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).