linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, airlied@linux.ie,
	davej@codemonkey.org.uk, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: kobject_register failed for intelfb (-EACCES) (Re: 2.6.12-rc4-mm1)
Date: Thu, 12 May 2005 20:20:29 +0400	[thread overview]
Message-ID: <200505122020.29290.adobriyan@gmail.com> (raw)
In-Reply-To: <20050512085933.03dc0d10.akpm@osdl.org>

On Thursday 12 May 2005 19:59, Andrew Morton wrote:
> Greg KH <greg@kroah.com> wrote:
> >  On Thu, May 12, 2005 at 04:58:01PM +0400, Alexey Dobriyan wrote:
> >  > kobject Intel(R) 830M/845G/852GM/855GM/865G/915G Framebuffer Driver:
> >  > registering. parent: <NULL>, set: drivers
> >  > kobject_register failed for Intel(R) 830M/845G/852GM/855GM/865G/915G
> > 
> >  Someone tried to put a "/" in a kobject name, which is not allowed.
> >  Actually the name seems to be set to:
> >  	"Intel(R) 830M/845G/852GM/855GM/865G/915G Framebuffer Driver"
> >  which is a bit verbous if you want to create a directory name :)

> Seems like a fix such as this will be needed:

> -	.name =		"Intel(R) " SUPPORTED_CHIPSETS " Framebuffer Driver",
> +	.name =		"intelfb",

It works.

      parent reply	other threads:[~2005-05-12 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050512033100.017958f6.akpm@osdl.org>
     [not found] ` <200505121658.02019.adobriyan@gmail.com>
     [not found]   ` <20050512154335.GD21765@kroah.com>
2005-05-12 15:59     ` kobject_register failed for intelfb (-EACCES) (Re: 2.6.12-rc4-mm1) Andrew Morton
2005-05-12 16:04       ` Greg KH
2005-05-12 16:20       ` Alexey Dobriyan [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=200505122020.29290.adobriyan@gmail.com \
    --to=adobriyan@gmail.com \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).