linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Miguel Ojeda <maxextreme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Luming Yu <Luming.yu@intel.com>,
	Andrew Zabolotny <zap@homelink.ru>,
	linux-acpi@vger.kernel.org, kernel-discuss@handhelds.org
Subject: Re: Display class
Date: Fri, 29 Dec 2006 22:32:43 -0500	[thread overview]
Message-ID: <200612292232.44122.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612051740250.2925@pentafluge.infradead.org>

Hi,

On Tuesday 05 December 2006 13:03, James Simmons wrote:
> +int probe_edid(struct display_device *dev, void *data)
> +{
> +       struct fb_monspecs spec;
> +       ssize_t size = 45;

const ssize_t size = 45? 

> +
> +       dev->name = kzalloc(size, GFP_KERNEL);

Why do you need kzalloc here?

> +       fb_edid_to_monspecs((unsigned char *) data, &spec);
> +       strcpy(dev->name, spec.manufacturer);

You seem to be overwriting dev->name in the very next line?

> +       return snprintf(dev->name, size, "%s %s %s\n", spec.manufacturer, spec.monitor, spec.ascii);
> 

Is result of snprintf interesting to the callers?

-- 
Dmitry

  parent reply	other threads:[~2006-12-30  3:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 19:41 ACPI output/lcd/auxdisplay mess James Simmons
2006-11-14 22:26 ` Miguel Ojeda
2006-11-15  0:54   ` James Simmons
2006-11-16  8:45     ` Miguel Ojeda
2006-11-16 15:38       ` James Simmons
2006-11-16 21:48         ` Miguel Ojeda
2006-12-05 18:03     ` Display class James Simmons
2006-12-06  1:14       ` Randy Dunlap
2006-12-06 15:10         ` James Simmons
2006-12-06 18:14           ` Randy Dunlap
2006-12-06 18:24             ` James Simmons
2006-12-06 18:57               ` Randy Dunlap
2006-12-06 19:13                 ` James Simmons
     [not found]           ` <Pine.LNX.4.64.0612061443180.28745-nGpKsS7K33UUkNsaar8edxWb9i9o6OzJ@public.gmane.org>
2006-12-06 20:28             ` Randy Dunlap
2006-12-06 13:19       ` Miguel Ojeda
2006-12-30  3:32       ` Dmitry Torokhov [this message]
2007-01-13 22:40         ` James Simmons
2007-01-13 22:47           ` [Linux-fbdev-devel] " James Simmons
2007-01-14  7:54           ` Greg KH
2007-01-14  7:55           ` Greg KH

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=200612292232.44122.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=Luming.yu@intel.com \
    --cc=jsimmons@infradead.org \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@gmail.com \
    --cc=zap@homelink.ru \
    /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).