From: Peter Meerwald <pmeerw@pmeerw.net>
To: linux-iio@vger.kernel.org
Cc: Peter Meerwald <pmeerw@pmeerw.net>
Subject: [PATCH 2/5] iio: fix typo, Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
Date: Sun, 7 Jul 2013 22:24:03 +0200 [thread overview]
Message-ID: <1373228646-5356-2-git-send-email-pmeerw@pmeerw.net> (raw)
In-Reply-To: <1373228646-5356-1-git-send-email-pmeerw@pmeerw.net>
Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
---
Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
index d89aded..1254457 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
+++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
@@ -18,4 +18,4 @@ Description:
adjust the reference frequency accordingly.
The value written has no effect until out_altvoltageY_frequency
is updated. Consider to use out_altvoltageY_powerdown to power
- down the PLL and it's RFOut buffers during REFin changes.
+ down the PLL and its RFOut buffers during REFin changes.
--
1.8.3.2
next prev parent reply other threads:[~2013-07-07 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 20:24 [PATCH 1/5] iio: staging: fix device.txt documentation Peter Meerwald
2013-07-07 20:24 ` Peter Meerwald [this message]
2013-07-09 21:15 ` [PATCH 2/5] iio: fix typo, Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350 Jonathan Cameron
2013-07-07 20:24 ` [PATCH 3/5] iio: staging: fix typo in ade758_ring.c Peter Meerwald
2013-07-09 21:15 ` Jonathan Cameron
2013-07-07 20:24 ` [PATCH 4/5] iio staging: fix lis3l02dq, read error handling Peter Meerwald
2013-07-09 21:14 ` Jonathan Cameron
2013-07-07 20:24 ` [PATCH 5/5] iio: fix semicolon in io_core_trigger.h Peter Meerwald
2013-07-09 21:16 ` Jonathan Cameron
2013-07-09 21:15 ` [PATCH 1/5] iio: staging: fix device.txt documentation 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=1373228646-5356-2-git-send-email-pmeerw@pmeerw.net \
--to=pmeerw@pmeerw.net \
--cc=linux-iio@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 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).