From: Greg KH <greg@kroah.com>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: Li Shaohua <shaohua.li@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
rmk@arm.linux.org.uk
Subject: Re: [PATCH]change 'struct device' -> platform_data to firmware_data
Date: Tue, 11 Jan 2005 21:06:17 -0800 [thread overview]
Message-ID: <20050112050617.GB976@kroah.com> (raw)
In-Reply-To: <20050112035446.GA11251@plexity.net>
On Tue, Jan 11, 2005 at 07:54:46PM -0800, Deepak Saxena wrote:
>
> So the question I have is whether we are using the field as intended
> or we have overloaded it with our own purposes?
You have used it for your own purposes :)
But I would argue that you used it in a way that works, and solves a
real need. As the intent of this field was never really properly
conveyed, and since you were here first, hey, your implementation gets
to stay!
> If we are doing things incorrectly, I am not argueing that our usage
> has to the way it sits. We could create a new generic serial_device and
> flash_device structures and subsystems for these, but that requires
> rewriting drivers and board ports; however, we need enough time
> to work with appropriate subsystem maintainers to do so. My suggestion
> is to add a new firmware_data field for use by ACPI ATM while we
> clean things up in ARM world if so required. Since ACPI is non-existent
> on ARM systems, another option is that we keep using the renamed data
> structure as we have been doing. /me votes for this option
I like the "just add a firmware_data" field option too. It doesn't
break any existing code, and the term "firmware" tells driver authors to
back away from it and not touch it (and we need to add the proper
documentation saying this.)
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-12 5:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 2:57 [PATCH]change 'struct device' -> platform_data to firmware_data Li Shaohua
2005-01-12 3:54 ` Deepak Saxena
2005-01-12 5:06 ` Greg KH [this message]
2005-01-12 5:15 ` Li Shaohua
2005-01-12 6:07 ` Kumar Gala
2005-01-12 6:37 ` Li Shaohua
2005-01-12 5:02 ` 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=20050112050617.GB976@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=dsaxena@plexity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=shaohua.li@intel.com \
/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