From: Randy Dunlap <rdunlap@xenotime.net>
To: Alan Ott <alan@signal11.us>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
jkosina@suse.cz, ospite@studenti.unina.it,
linux-input@vger.kernel.org, linux-bluetooth@vger.kernel.org,
bgood@velocity.net
Subject: Re: [PATCH v4 1/2] HID: Documentation for hidraw
Date: Wed, 16 Feb 2011 16:56:03 -0800 [thread overview]
Message-ID: <20110216165603.fe8c342d.rdunlap@xenotime.net> (raw)
In-Reply-To: <4D5C202B.5030403@signal11.us>
On Wed, 16 Feb 2011 14:06:19 -0500 Alan Ott wrote:
> On 02/16/2011 09:12 AM, Jonathan Corbet wrote:
> >> Documentation/hid/Makefile | 8 ++
> >> Documentation/hid/hid-example.c | 167 +++++++++++++++++++++++++++++++++++++++
> >>
> > I believe we're trying to get code - especially runnable code - out of the
> > Documentation tree. Should this go under samples/ or, if it's useful
> > enough, under tools/?
> >
>
> Hi Jon,
>
> Not a problem. I'd say samples/ over tools/ for this stuff. I'll re-spin
> and re-submit.
and then
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-02-17 0:56 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 [this message]
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
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=20110216165603.fe8c342d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alan@signal11.us \
--cc=bgood@velocity.net \
--cc=corbet@lwn.net \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ospite@studenti.unina.it \
/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).