All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] V4L/DVB: ir: Add a link to associate /sys/class/ir/irrcv with the input device
Date: Sun, 14 Mar 2010 15:22:36 -0300	[thread overview]
Message-ID: <4B9D296C.1090901@redhat.com> (raw)
In-Reply-To: <20100314063704.GB24684@core.coreip.homeip.net>

Dmitry Torokhov wrote:
> On Sat, Mar 13, 2010 at 05:59:34PM -0300, Mauro Carvalho Chehab wrote:

>> It is representing it right:
>>
>> usb1/1-3 -> irrcv -> irrcv0 -> input7 -> event7
>>
>> The only extra attribute there is the class name "irrcv", but this seems
>> coherent with the other classes on this device (dvb, sound, power, video4linux).
>>
> 
> Ah, yes, I saw where you take input device's parent and use it as
> irrcv's parent but missed the piece where you substitute original
> input device's parent with irrcv. I bit sneaky to my taste but I guess
> can be cleaned up later.

Yes. I opted to do this little trick to avoid changing the interfaces
on the other modules, and to minimize the needs when porting from input.
We can later clean it if/when needed.

-- 

Cheers,
Mauro

      reply	other threads:[~2010-03-14 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 15:46 [PATCH] V4L/DVB: ir: Add a link to associate /sys/class/ir/irrcv with the input device Mauro Carvalho Chehab
2010-03-11 17:52 ` Dmitry Torokhov
2010-03-11 22:05   ` Mauro Carvalho Chehab
2010-03-12  4:32   ` Mauro Carvalho Chehab
2010-03-13  8:41     ` Dmitry Torokhov
2010-03-13 20:59       ` Mauro Carvalho Chehab
2010-03-14  6:37         ` Dmitry Torokhov
2010-03-14 18:22           ` Mauro Carvalho Chehab [this message]

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=4B9D296C.1090901@redhat.com \
    --to=mchehab@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.