From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for v4.8-rc1] media updates part II: documentation
Date: Wed, 27 Jul 2016 10:52:10 -0300 [thread overview]
Message-ID: <20160727105210.1e1233c2@recife.lan> (raw)
In-Reply-To: <d3a51c25-fe71-46b1-1274-d24da9f8d3c5@xs4all.nl>
Em Wed, 27 Jul 2016 11:53:16 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> Hi Mauro, Linus,
>
> On 07/27/2016 11:23 AM, Mauro Carvalho Chehab wrote:
> > Hi Linus,
> >
> > Please pull from:
> > git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v4.8-4
> >
> > For media documentation updates.
> >
> > This patch series does the conversion of all media documentation stuff
> > to Restrutured Text markup format and add them to the Documentation/index.rst
> > file. The media documentation was grouped into 4 books:
> > - media uAPI;
> > - media kAPI;
> > - V4L driver-specific documentation;
> > - DVB driver-specific documentation.
> >
> > It also contains several documentation improvements and one fixup patch for
> > a core issue with cropcap.
>
> FYI: the cropcap fixup patch (v4l2-ioctl: fix stupid mistake in cropcap condition)
> is already upstream (it got merged just before 4.7 was released).
>
> So that patch can be dropped.
True. Will resend the pull request without that patch.
>
> Regards,
>
> Hans
--
Thanks,
Mauro
next prev parent reply other threads:[~2016-07-27 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 9:23 [GIT PULL for v4.8-rc1] media updates part II: documentation Mauro Carvalho Chehab
2016-07-27 9:53 ` Hans Verkuil
2016-07-27 13:52 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 14:01 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=20160727105210.1e1233c2@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=torvalds@linux-foundation.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