From: Randy Dunlap <rdunlap@xenotime.net>
To: Alan Ott <alan@signal11.us>
Cc: Jonathan Corbet <corbet@lwn.net>,
Antonio Ospite <ospite@studenti.unina.it>,
Jiri Kosina <jkosina@suse.cz>,
Jason Wessel <jason.wessel@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stefani Seibold <stefani@seibold.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Documentation and Sample for hidraw
Date: Mon, 21 Mar 2011 13:17:32 -0700 [thread overview]
Message-ID: <20110321131732.8e8906a8.rdunlap@xenotime.net> (raw)
In-Reply-To: <1300580985-10726-1-git-send-email-alan@signal11.us>
On Sat, 19 Mar 2011 20:29:43 -0400 Alan Ott wrote:
> Sorry I've been slack in getting v5 of this patch out. Because
> it's been so long, I'll recap what happened last time:
>
> * Jon Corbet suggested that the example programs be moved into samples/ .
> * Randy Dunlap indicated his acked-by when this was done.
>
> These patches add hidraw.txt to a new Documentation/hid/ directory.
>
> It creates an example program which is now in samples/ with a Kconfig item.
>
> The existing hiddev.txt has been moved from Documentation/usb/ to
> Documentation/hid/
Jiri,
I suppose that you will merge these patches?
or did you want me to do it?
> This is based on .38+
>
> Alan Ott (2):
> HID: Documentation for hidraw
> HID: Move hiddev.txt to the new Documentation/HID directory
>
> Documentation/{usb => hid}/hiddev.txt | 0
> Documentation/hid/hidraw.txt | 119 +++++++++++++++++++++++
> samples/Kconfig | 6 +
> samples/Makefile | 2 +-
> samples/hidraw/Makefile | 8 ++
> samples/hidraw/hid-example.c | 167 +++++++++++++++++++++++++++++++++
> 6 files changed, 301 insertions(+), 1 deletions(-)
> rename Documentation/{usb => hid}/hiddev.txt (100%)
> create mode 100644 Documentation/hid/hidraw.txt
> create mode 100644 samples/hidraw/Makefile
> create mode 100644 samples/hidraw/hid-example.c
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-doc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-03-21 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 4:06 [PATCH v4 0/2] HID: hidraw Documentation Alan Ott
2011-02-16 4:06 ` [PATCH v4 1/2] HID: Documentation for hidraw Alan Ott
2011-02-16 14:12 ` Jonathan Corbet
2011-02-16 19:06 ` Alan Ott
2011-02-16 19:10 ` Jiri Kosina
2011-02-17 0:56 ` Randy Dunlap
2011-02-16 4:06 ` [PATCH v4 2/2] HID: Move hiddev.txt to the new Documentation/HID directory Alan Ott
2011-03-20 0:29 ` [PATCH v5 0/2] Documentation and Sample for hidraw Alan Ott
2011-03-21 20:17 ` Randy Dunlap [this message]
2011-03-22 10:44 ` Jiri Kosina
2011-03-20 0:29 ` [PATCH v5 1/2] HID: Documentation " Alan Ott
2011-03-20 0:29 ` [PATCH v5 2/2] HID: Move hiddev.txt to the new Documentation/HID directory Alan Ott
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=20110321131732.8e8906a8.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=alan@signal11.us \
--cc=corbet@lwn.net \
--cc=jason.wessel@windriver.com \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ospite@studenti.unina.it \
--cc=stefani@seibold.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).