From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Andrey Utkin <andrey.utkin@corp.bluecherry.net>,
"hans.verkuil" <hans.verkuil@cisco.com>,
khalasa <khalasa@piap.pl>,
Ismael Luceno <ismael.luceno@corp.bluecherry.net>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] drivers/media/pci/solo6x10/solo6x10-disp.c: check kzalloc() result
Date: Sat, 26 Jul 2014 10:21:51 -0300 [thread overview]
Message-ID: <20140726102151.239386d8.m.chehab@samsung.com> (raw)
In-Reply-To: <20140726061311.GB25880@mwanda>
Em Sat, 26 Jul 2014 09:13:12 +0300
Dan Carpenter <dan.carpenter@oracle.com> escreveu:
> On Fri, Jul 25, 2014 at 09:32:36PM +0300, Andrey Utkin wrote:
> > Please ignore. I didn't notice that Hans has already posted a patch
> > fixing that and more.
> >
>
> Heh. I was just about to send my fix for this bug as well.
>
> I don't follow linux-media so I didn't realize this driver was getting
> promoted out of staging. I wish there was a way to go over drivers and
> fix any basic static checker fixes before promotion.
When I promote a driver out of staging, I run checkpatch again, in
order to check if everything is fine. It would be nice to have a
checkpatch-like script that would also run the static checker
checks for that particular patch. With that, I could, instead,
use such script when promoting patches or handling patches adding
new files to the Kernel.
Regards,
Mauro
prev parent reply other threads:[~2014-07-26 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:30 Andrey Utkin
2014-07-25 18:32 ` Andrey Utkin
2014-07-26 6:13 ` Dan Carpenter
2014-07-26 13:21 ` 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=20140726102151.239386d8.m.chehab@samsung.com \
--to=m.chehab@samsung.com \
--cc=andrey.utkin@corp.bluecherry.net \
--cc=dan.carpenter@oracle.com \
--cc=hans.verkuil@cisco.com \
--cc=ismael.luceno@corp.bluecherry.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=khalasa@piap.pl \
--cc=linux-kernel@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 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®