All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] use of struct platform_device vs struct device in
Date: Sat, 04 Feb 2006 10:51:14 +0000	[thread overview]
Message-ID: <20060204115114.67845ad2.khali@linux-fr.org> (raw)
In-Reply-To: <43E12BDF.1020805@gmail.com>

Hi Jim,

> WRT waiting for 2.9.2,  it would take some months to get updates
> thru -mm and then into mainline.   Certainly drivers could sit in -mm
> until the time is right.

Bad idea from a maintenance point of view. Converting i2c-isa drivers to
platform drivers will be very intrusive, so it's likely that other
patches (bug fixes etc...) with conflict with them, effectively
doubling the amount of work.

I'd better postpone any work related to such conversions until we are
ready to merge them. This also gives us some time to make sure that the
choices I made for the f71805f driver were correct. See the recent
thread started by Hans de Goede for example.

> Actually though, the question I posed was twisted from an OT one;
> Im working on pc8736x_gpio, which is an adaptation of scx200_gpio,
> so its a char-dev.  I was looking for a way to get a struct device that
> I could use in dev_dbg() and friends,
> 
> I may imitate your work in pc87360, just to get some familiarity
> with platform_device, (along with on-topic help ;-), then apply that
> to my gpio project.

You can still do this in your private sandbox if it helps you.

Thanks,
-- 
Jean Delvare


      parent reply	other threads:[~2006-02-04 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 21:45 [lm-sensors] use of struct platform_device vs struct device in Jim Cromie
2006-02-02 21:53 ` Jean Delvare
2006-02-03  1:13 ` Jim Cromie
2006-02-04 10:51 ` Jean Delvare [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=20060204115114.67845ad2.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 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.