From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
"Timo Kokkonen" <timo.t.kokkonen@iki.fi>,
"Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>
Subject: Re: [PATCH 1/5] [media] ir-rx51: port to rc-core
Date: Fri, 30 Dec 2016 13:30:01 +0200 [thread overview]
Message-ID: <5878d916-6a60-d5c3-b912-948b5b970661@gmail.com> (raw)
In-Reply-To: <f5262cc638a494f238ef96a80d8f45265ca2fd02.1482255894.git.sean@mess.org>
Hi,
On 20.12.2016 19:50, Sean Young wrote:
> This driver was written using lirc since rc-core did not support
> transmitter-only hardware at that time. Now that it does, port
> this driver.
>
> Compile tested only.
>
I guess after that change, there will be no more /dev/lircN device,
right? Neither will LIRC_XXX IOCTL codes be supported?
That looks to me as a completely new driver, not a port to new API.
Right now there are applications using the current behaviour (pierogi
for example), which will be broken by the change.
Ivo
next prev parent reply other threads:[~2016-12-30 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 17:50 [PATCH 0/5] Lirc staging drivers Sean Young
2016-12-20 17:50 ` [PATCH 1/5] [media] ir-rx51: port to rc-core Sean Young
2016-12-30 11:30 ` Ivaylo Dimitrov [this message]
2016-12-30 13:07 ` Sean Young
2016-12-30 13:30 ` Sean Young
2016-12-30 13:50 ` Ivaylo Dimitrov
2016-12-30 15:46 ` Sean Young
2017-01-16 10:10 ` Sean Young
2017-01-16 16:34 ` Ivaylo Dimitrov
2017-01-16 20:13 ` Pavel Machek
2017-01-30 16:26 ` Mauro Carvalho Chehab
2016-12-20 17:50 ` [PATCH 2/5] [media] staging: lirc_sir: " Sean Young
2016-12-20 17:50 ` [PATCH 3/5] [media] staging: lirc_parallel: remove Sean Young
2016-12-20 17:50 ` [PATCH 4/5] [media] staging: lirc_bt829: remove Sean Young
2016-12-20 17:50 ` [PATCH 5/5] [media] staging: lirc_imon: port remaining usb ids to imon and remove Sean Young
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=5878d916-6a60-d5c3-b912-948b5b970661@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sean@mess.org \
--cc=timo.t.kokkonen@iki.fi \
/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
all inboxes | Powered by JetHome®