From: Hans Verkuil <hverkuil@xs4all.nl>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-media@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] input: add support for HDMI CEC
Date: Sat, 18 Jun 2016 18:56:24 +0200 [thread overview]
Message-ID: <57657D38.9080007@xs4all.nl> (raw)
In-Reply-To: <20160618162655.GC12210@dtor-ws>
On 06/18/2016 06:26 PM, Dmitry Torokhov wrote:
> Hi Hans,
>
> On Sat, Jun 18, 2016 at 04:50:26PM +0200, Hans Verkuil wrote:
>> From: Hans Verkuil <hans.verkuil@cisco.com>
>>
>> Hi Dmitry,
>>
>> This patch series adds input support for the HDMI CEC bus through which
>> remote control keys can be passed from one HDMI device to another.
>>
>> This has been posted before as part of the HDMI CEC patch series. We are
>> going to merge that in linux-media for 4.8, but these two patches have to
>> go through linux-input.
>>
>> Only the rc-cec keymap file depends on this, and we will take care of that
>> dependency (we'll postpone merging that until both these input patches and
>> our own CEC patches have been merged in mainline).
>
> If it would be easier for you I am perfectly fine with these patches
> going through media tree; you have my acks on them.
You're not expecting any changes to these headers for 4.8 that might
cause merge conflicts? That was Mauro's concern.
If not, then I would prefer it to go through the media tree to simplify
the dependencies, but it's up to Mauro.
Regards,
Hans
next prev parent reply other threads:[~2016-06-18 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 14:50 [PATCH 0/2] input: add support for HDMI CEC Hans Verkuil
2016-06-18 14:50 ` [PATCH 1/2] input.h: add BUS_CEC type Hans Verkuil
2016-06-18 14:50 ` [PATCH 2/2] HID: add HDMI CEC specific keycodes Hans Verkuil
2016-06-18 16:26 ` [PATCH 0/2] input: add support for HDMI CEC Dmitry Torokhov
2016-06-18 16:56 ` Hans Verkuil [this message]
2016-06-18 17:44 ` Mauro Carvalho Chehab
2016-06-18 17:56 ` Dmitry Torokhov
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=57657D38.9080007@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).