From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sean Young <sean@mess.org>, Jarod Wilson <jwilson@redhat.com>,
Andy Walls <awalls@md.metrocast.net>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>,
linux-media@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: staging: media: lirc: lirc_zilog.c: replace custom print macros with dev_* and pr_*
Date: Thu, 6 Nov 2014 11:05:49 -0200 [thread overview]
Message-ID: <20141106110549.1812acc7@recife.lan> (raw)
In-Reply-To: <20141106124629.GA898@gofer.mess.org>
Hi Sean,
Em Thu, 06 Nov 2014 12:46:29 +0000
Sean Young <sean@mess.org> escreveu:
> On Fri, Oct 31, 2014 at 05:35:41PM +0300, Dan Carpenter wrote:
> > On Fri, Oct 31, 2014 at 04:26:45PM +0200, Aya Mahfouz wrote:
> > > On Fri, Oct 31, 2014 at 04:06:00PM +0300, Dan Carpenter wrote:
> > > > drivers/staging/media/lirc/lirc_zilog.c
> > > > 1333 /* Close the IR device */
> > > > 1334 static int close(struct inode *node, struct file *filep)
> > > > 1335 {
> > > > 1336 /* find our IR struct */
> > > > 1337 struct IR *ir = filep->private_data;
> > > > 1338
> > > > 1339 if (ir == NULL) {
> > > > ^^^^^^^^^^
> > > > 1340 dev_err(ir->l.dev, "close: no private_data attached to the file!\n");
> > > > ^^^^^^^^^
> > > >
> > > > I suggest you just delete the error message. Can "ir" actually be NULL
> > > > here anyway?
> > > >
> > >
> > > Since I'm a newbie and this is not my code, I prefer to use pr_err().
> >
> > This driver doesn't belong to anyone. Go ahead and take ownership. The
> > message is fairly worthless and no one will miss it.
>
> Speaking of ownership, what this driver really needs is to be ported to
> rc-core. In order to do this it'll need to be able to send raw IR rather
> key codes; I've been peering at the firmware but it neither looks like
> zilog z8 opcodes nor space/pulse information.
Actually, I think that all features provided by this driver were already
migrated into the ir-kbd-i2c (drivers/media/i2c/ir-kbd-i2c.c) driver.
Andy and Jarod worked on this conversion, but we decided, on that time,
to keep lirc_zilog for a while (can't remember why).
Andy/Jarod,
What's the status of the ir-kbd-i2c with regards to Zilog z8 support?
> Does anyone have any contacts at Hauppauge who could help with this?
Probably, it won't be easy to get someone there that worked on it,
as this device is too old.
Anyway, if are there anything still pending, I may be able to get
some contacts at the vendor.
Regards,
Mauro
next prev parent reply other threads:[~2014-11-06 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 13:06 staging: media: lirc: lirc_zilog.c: replace custom print macros with dev_* and pr_* Dan Carpenter
2014-10-31 14:26 ` Aya Mahfouz
2014-10-31 14:35 ` Dan Carpenter
2014-11-01 20:05 ` Aya Mahfouz
2014-11-06 12:46 ` Sean Young
2014-11-06 13:05 ` Mauro Carvalho Chehab [this message]
2014-11-06 13:21 ` Sean Young
[not found] ` <697D038C-4BD9-4113-8E7E-B89BACF09AC2@gmail.com>
2014-11-06 13:56 ` Andy Walls
2014-11-09 21:35 ` Sean Young
2014-11-17 14:59 ` Mauro Carvalho Chehab
2014-11-20 12:38 ` 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=20141106110549.1812acc7@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=awalls@md.metrocast.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwilson@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=sean@mess.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.