From: Hans Verkuil <hansverk@cisco.com>
To: Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>
Cc: Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH v2 0/2] moves samples out of Documentation directory
Date: Tue, 26 Apr 2016 12:28:42 +0200 [thread overview]
Message-ID: <571F42DA.60005@cisco.com> (raw)
In-Reply-To: <20160426035939.51649686@lwn.net>
On 04/26/2016 11:59 AM, Jonathan Corbet wrote:
> On Mon, 25 Apr 2016 18:03:07 +0200
> Arnd Bergmann <arnd@arndb.de> wrote:
>
>> As suggested by Nicolas Pitre, here is a resend of two patches to
>> move the kernel modules from Documentation/*/ to samples/*/.
>>
>> With Nico's changes in place, it's no longer necessary to do this,
>> but it seems like a good idea anyway for consistency.
>> Not sure who would be the best person to pick up the patches, I'd
>> probably either the Documentation or the kbuild maintainers.
>>
>> Arnd
>>
>> [PATCH v2 1/2] samples: connector: from Documentation to samples
>> [PATCH v2 2/2] samples: v4l: from Documentation to samples directory
>
> I can take them through the docs tree.
>
> Hans [added], are you OK with moving v4l2-pci-skeleton.c over to
> the samples directory?
Yes, that's fine. For the record:
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Regards,
Hans
next prev parent reply other threads:[~2016-04-26 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 16:03 [PATCH v2 0/2] moves samples out of Documentation directory Arnd Bergmann
2016-04-25 16:03 ` [PATCH v2 1/2] samples: connector: from Documentation to samples directory Arnd Bergmann
2016-04-25 16:03 ` [PATCH v2 2/2] samples: v4l: " Arnd Bergmann
2016-04-26 9:59 ` [PATCH v2 0/2] moves samples out of Documentation directory Jonathan Corbet
2016-04-26 10:28 ` Hans Verkuil [this message]
2016-04-26 10:55 ` Mauro Carvalho Chehab
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=571F42DA.60005@cisco.com \
--to=hansverk@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=hans.verkuil@cisco.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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