From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Dan Carpenter <error27@gmail.com>
Cc: JosephChan@via.com.tw, Andrew Morton <akpm@linux-foundation.org>,
ScottFang@viatech.com.cn,
"linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [patch] fix oops with no /proc
Date: Wed, 25 Nov 2009 18:46:41 +0100 [thread overview]
Message-ID: <4B0D6D81.8010702@gmx.de> (raw)
In-Reply-To: <20091122142111.GA28155@bicker>
Hi,
nice catch. Your patch is obviously correct.
Please send it to Andrew Morton <akpm@linux-foundation.org> to get it
into mainline.
Dan Carpenter schrieb:
> Fixed a typo: missing *. This would lead to a kernel oops if the kernel
> was compiled without support for the /proc file system.
>
> Found with a static checker. Compile tested.
>
> regards,
> dan carpenter
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Acked-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
>
> --- orig/drivers/video/via/viafbdev.c 2009-11-21 14:44:33.000000000 +0200
> +++ devel/drivers/video/via/viafbdev.c 2009-11-21 14:44:43.000000000 +0200
> @@ -1797,7 +1797,7 @@ static const struct file_operations viaf
> static void viafb_init_proc(struct proc_dir_entry **viafb_entry)
> {
> *viafb_entry = proc_mkdir("viafb", NULL);
> - if (viafb_entry) {
> + if (*viafb_entry) {
Thanks,
Florian Tobias Schandinat
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
prev parent reply other threads:[~2009-11-25 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 14:21 [patch] fix oops with no /proc Dan Carpenter
2009-11-25 17:46 ` Florian Tobias Schandinat [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=4B0D6D81.8010702@gmx.de \
--to=florianschandinat@gmx.de \
--cc=JosephChan@via.com.tw \
--cc=ScottFang@viatech.com.cn \
--cc=akpm@linux-foundation.org \
--cc=error27@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).