From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 2/2] Print parser position on error
Date: Wed, 19 Jun 2013 12:40:29 +0200 [thread overview]
Message-ID: <1665015.Jt87nLofNI@avalon> (raw)
In-Reply-To: <20130619053054.GD32299@pengutronix.de>
Hi Sascha,
On Wednesday 19 June 2013 07:30:54 Sascha Hauer wrote:
> On Wed, Jun 19, 2013 at 02:39:48AM +0200, Laurent Pinchart wrote:
> > On Monday 10 June 2013 15:56:01 Laurent Pinchart wrote:
> > > Hi Sascha,
> > >
> > > I'm sorry for the late reply.
> > >
> > > Great patch set, thank you. It's very helpful.
> >
> > Should I got ahead and apply the patch with the proposed modifications
> > below ?
>
> That'd be nice. I'm a bit out of the loop at the moment and don't have
> a setup handy to test the changes.
Pushed, thank you.
> > > No need to cast to a char * here, end is already a char *.
> > >
> > > What would you think about adding
> > >
> > > + /* endp can be NULL. To avoid spreading NULL checks across the
> > > + * function, set endp to &end in that case.
> > > + */
> > > + if (endp == NULL)
> > > + endp = &end;
> > >
> > > at the beginning of the function and removing the endp NULL checks that
> > > are
> > > spread across the code below ?
>
> Good idea. Your other suggestions also look good.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-06-19 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 13:27 [PATCH] media-ctl error messages Sascha Hauer
2013-05-08 13:27 ` [PATCH 1/2] Print more detailed parse " Sascha Hauer
2013-05-08 13:32 ` Sascha Hauer
2013-05-08 13:27 ` [PATCH 2/2] Print parser position on error Sascha Hauer
2013-06-10 13:56 ` Laurent Pinchart
2013-06-19 0:39 ` Laurent Pinchart
2013-06-19 5:30 ` Sascha Hauer
2013-06-19 10:40 ` Laurent Pinchart [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=1665015.Jt87nLofNI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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