From: "Ramón Rey Vicente" <ramon.rey@hispalinux.es>
To: Adam Belay <ambx1@neo.rr.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [2.6.0-test3-current] drivers/pnp/core.c:72: error: structure has no member named `name'
Date: Sun, 17 Aug 2003 01:20:07 +0200 [thread overview]
Message-ID: <1061076005.1304.34.camel@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
Hi.
It seems the struct dev.name was removed from include/linux/device.h and
should be implemented for every susbsystem.
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
------------------------------------------------------------
gpg public key ID 0xBEBD71D5 # http://pgp.escomposlinux.org/
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-08-16 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 23:20 Ramón Rey Vicente [this message]
2003-08-16 22:16 ` [2.6.0-test3-current] drivers/pnp/core.c:72: error: structure has no member named `name' Adam Belay
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=1061076005.1304.34.camel@debian \
--to=ramon.rey@hispalinux.es \
--cc=ambx1@neo.rr.com \
--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