mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Shaohua <shaohua.li@intel.com>
To: Greg KH <greg@kroah.com>
Cc: ACPI-DEV <acpi-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>,
	Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: [PATCH/RFC 1/4]device core changes
Date: Wed, 10 Nov 2004 09:45:37 +0800	[thread overview]
Message-ID: <1100051137.7825.6.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20041110012443.GA9496@kroah.com>

On Wed, 2004-11-10 at 09:24, Greg KH wrote:
> > > 
> > > Hm, hopefully Pat will chime in about what would be best for this, as he
> > > created the platform_notify interface.
> > Ok, an updated version. Use 'platform_notify', but add a 'type' in 
> > 'struct bus_type'. Using bus_type->name to identify the bus type is
> > pretty much ugly and slow. 
> 
> No, no "type" for a bus, sorry.
> 
> Maybe your other patches weren't so bad...  If we implement them, can we
> drop the platform notify stuff?
Currently only ARM use 'platform_notify', and we can easily convert it
to use per-bus 'platform_bind'. One concern of per-bus 'platform_bind'
is we will have many '#ifdef ..' if many platforms implement their
per-bus 'platform_bind'.

Thanks,
Shaohua


  reply	other threads:[~2004-11-10  1:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  4:11 Li Shaohua
2004-11-08 22:58 ` Greg KH
2004-11-09  0:50   ` Li Shaohua
2004-11-09  3:35     ` Li Shaohua
2004-11-09  4:58       ` Greg KH
2004-11-09  9:03         ` Li Shaohua
2004-11-10  1:24           ` Greg KH
2004-11-10  1:45             ` Li Shaohua [this message]
2004-11-10  4:28               ` Russell King
2004-11-11  7:03                 ` Li Shaohua
2004-11-11  8:44                   ` Russell King
2004-11-11  8:46                     ` Li Shaohua
2004-11-12  0:30                   ` 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=1100051137.7825.6.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.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
all inboxes | Powered by JetHome®