From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Antti Palosaari <crope@iki.fi>,
Guennadi Liakhovetski <guennadi.liakhovetski@intel.com>,
Helen Mae Koike Fornazier <helen.koike@collabora.co.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
Shuah Khan <shuahkh@osg.samsung.com>,
linux-media <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] [media] Documentation: Add HSV format
Date: Fri, 15 Jul 2016 12:53:12 -0300 [thread overview]
Message-ID: <20160715125312.481aa36b@recife.lan> (raw)
In-Reply-To: <CAPybu_077ZkW3_SnPLqkMMgUUrrBDYH+8WzSEnSHAkyTkE525w@mail.gmail.com>
Em Fri, 15 Jul 2016 17:36:15 +0200
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> escreveu:
> Hi Mauro
>
> On Fri, Jul 15, 2016 at 5:28 PM, Mauro Carvalho Chehab
> <mchehab@osg.samsung.com> wrote:
> > Hi Ricardo,
> >
> > I'm not seeing patch 1.
>
> That is because you blacklisted me :P
> https://lkml.org/lkml/2016/7/15/45
>
> I resend it to you right away.
Thanks.
> >
> > Anyway, please send documentation patches against the rst files. They're
> > at the "docs-next" branch and will be merged upstream on this merge window.
> >
>
> you are absolutely right, I read about it in lwn. Sorry about that.
>
>
> How do you prefer it:
> - 2 patchset : One on top of media/master with the code changes, and
> one on top of docs-next with the doc changes.
> or
> -1 patchset on top of doc-next and we will figure out later if there
> is a merge conflict with media
IMHO, the best would be to wait for it to be merged. I'm finishing
handling patches for 4.7 in a few, and applying only on more trivial
patches and bug fixes.
Yet, I suspect that there won't be conflicts if you base your
patches against docs-next, as most of the media stuff is merged
there.
Thanks,
Mauro
next prev parent reply other threads:[~2016-07-15 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 15:16 [PATCH 0/6] Add HSV format Ricardo Ribalda Delgado
2016-07-15 15:16 ` [PATCH 1/6] [media] videodev2.h Add HSV formats Ricardo Ribalda Delgado
2016-07-15 15:16 ` [PATCH 2/6] [media] Documentation: Add HSV format Ricardo Ribalda Delgado
2016-07-15 15:28 ` Mauro Carvalho Chehab
2016-07-15 15:36 ` Ricardo Ribalda Delgado
2016-07-15 15:53 ` Mauro Carvalho Chehab [this message]
2016-07-15 15:16 ` [PATCH 3/6] [media] Documentation: Add Ricardo Ribalda as author Ricardo Ribalda Delgado
2016-07-15 15:16 ` [PATCH 4/6] [media] vivid: code refactor for color representation Ricardo Ribalda Delgado
2016-07-15 15:16 ` [PATCH 5/6] [media] vivid: Add support for HSV formats Ricardo Ribalda Delgado
2016-07-15 15:16 ` [PATCH 6/6] [media] vivid: Rename variable Ricardo Ribalda Delgado
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=20160715125312.481aa36b@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=crope@iki.fi \
--cc=guennadi.liakhovetski@intel.com \
--cc=helen.koike@collabora.co.uk \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.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