From: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: 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: Sat, 1 Nov 2014 22:05:26 +0200 [thread overview]
Message-ID: <20141101200526.GA2098@localhost.localdomain> (raw)
In-Reply-To: <20141031143541.GM6890@mwanda>
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.
>
ok.
> >
> > In general, I can send a new patch to fix the aforementioned warnings.
> > Kindly let me know if you prefer that I send a second version of this
> > patch.
>
> No. The first patch was already applied so send a new patch.
>
I will fix the static errors that my patch caused. The warning concerning
the double free will require rewriting some parts of the function and was
not caused by my patch. I have a couple of ideas in mind but I need
sometime to apply them. Greg too is not happy about the coding style of
this driver in general.
> regards,
> dan carpenter
>
Kind Regards,
Aya Saif El-yazal Mahfouz
next prev parent reply other threads:[~2014-11-01 20: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 [this message]
2014-11-06 12:46 ` Sean Young
2014-11-06 13:05 ` Mauro Carvalho Chehab
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=20141101200526.GA2098@localhost.localdomain \
--to=mahfouz.saif.elyazal@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.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