From: Todd Poynor <tpoynor@mvista.com>
To: 唐長鴻 <changhung@mail.im.tku.edu.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: where is platform_device.h header file
Date: Fri, 23 Dec 2005 09:29:53 -0800 [thread overview]
Message-ID: <43AC3411.6050604@mvista.com> (raw)
In-Reply-To: <8b6915c1bd80465b68edd5092af49f52@59.120.32.217>
唐長鴻 wrote:
> Hi, all.
> I'm a newbie on mtd. When I patched the newest snapshot in
> linux kernel 2.6.14.2 and "make" it, I received kernel complaint,
> "platform_device.h: No such file."
> I re-searched in linux-mtd archives and google, but there was no
> resolution. I wondered that it was maybe a populate problem and
> resolved.
>
> Could anyone help me to find that file?
This has been changing in mainline, can probably check the CVS logs and
find a version of the files of interest prior to converting to
platform_device.h.
--
Todd
prev parent reply other threads:[~2005-12-23 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 8:21 where is platform_device.h header file 唐長鴻
2005-12-23 17:29 ` Todd Poynor [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=43AC3411.6050604@mvista.com \
--to=tpoynor@mvista.com \
--cc=changhung@mail.im.tku.edu.tw \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.