public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
	linux-kernel@vger.kernel.org, eric.piel@tremplin-utc.net,
	pali.rohar@gmail.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: misc-devices: Rename freefall.c from hpfall.c in lis2lv02d
Date: Sun, 31 Aug 2014 16:21:36 -0700	[thread overview]
Message-ID: <5403AE00.2030901@infradead.org> (raw)
In-Reply-To: <1409491133-14402-1-git-send-email-standby24x7@gmail.com>

On 08/31/14 06:18, Masanari Iida wrote:
> hpfall.c was renamed to freefall.c in 3.16.
> But this file still refer to hpfall.c instead of freefall.c
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  Documentation/misc-devices/lis3lv02d | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/misc-devices/lis3lv02d b/Documentation/misc-devices/lis3lv02d
> index af815b9..f89960a 100644
> --- a/Documentation/misc-devices/lis3lv02d
> +++ b/Documentation/misc-devices/lis3lv02d
> @@ -59,7 +59,7 @@ acts similar to /dev/rtc and reacts on free-fall interrupts received
>  from the device. It supports blocking operations, poll/select and
>  fasync operation modes. You must read 1 bytes from the device.  The
>  result is number of free-fall interrupts since the last successful
> -read (or 255 if number of interrupts would not fit). See the hpfall.c
> +read (or 255 if number of interrupts would not fit). See the freefall.c
>  file for an example on using the device.
>  
>  
> 

Applied.  Thanks.

-- 
~Randy

      reply	other threads:[~2014-08-31 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 13:18 [PATCH] Documentation: misc-devices: Rename freefall.c from hpfall.c in lis2lv02d Masanari Iida
2014-08-31 23:21 ` Randy Dunlap [this message]

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=5403AE00.2030901@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=eric.piel@tremplin-utc.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=standby24x7@gmail.com \
    /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