LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: David Brownell <david-b@pacbell.net>, Greg KH <gregkh@suse.de>,
	stefanr@s5r6.in-berlin.de, James.Bottomley@hansenpartnership.com,
	a.zummo@towertech.it, peterz@infradead.org, cbou@mail.ru,
	linux-kernel@vger.kernel.org, stern@rowland.harvard.edu,
	dwmw2@infradead.org, davem@davemloft.net, jarkao2@gmail.com,
	cornelia.huck@de.ibm.com
Subject: Re: [PATCH 1/6] driver-core : add class iteration api
Date: Tue, 22 Jan 2008 14:25:50 -0800	[thread overview]
Message-ID: <20080122222550.GB7146@kroah.com> (raw)
In-Reply-To: <20080122072708.GB3725@darkstar.te-china.tietoenator.com>

On Tue, Jan 22, 2008 at 03:27:08PM +0800, Dave Young wrote:
> 
> Add the following class iteration functions for driver use:
> class_for_each_device
> class_find_device
> class_for_each_child
> class_find_child

As class_for_each_child() is not used by anyone in this patch series,
and we want to heavily discourage the use of class_device (only scsi and
IB are the last remaining users), I'll cut out this portion of the
patch.

Any objection?

thanks,

greg k-h

  parent reply	other threads:[~2008-01-22 22:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12  9:47 [PATCH 1/7] driver-core : add class iteration api Dave Young
2008-01-12 10:50 ` Stefan Richter
2008-01-14  1:32   ` Dave Young
2008-01-12 20:11 ` Jarek Poplawski
2008-01-14  1:36   ` Dave Young
2008-01-14  6:58     ` Jarek Poplawski
2008-01-14  7:00       ` Dave Young
2008-01-14 12:13 ` Cornelia Huck
2008-01-15  0:17   ` Dave Young
2008-01-15  9:13 ` Dave Young
2008-01-15  9:45   ` Cornelia Huck
2008-01-22  5:54 ` [PATCH 1/6] " Dave Young
2008-01-22  6:06   ` Dave Young
2008-01-22  6:24   ` David Brownell
2008-01-22  6:30     ` Dave Young
2008-01-22  7:27     ` Dave Young
2008-01-22  8:44       ` Cornelia Huck
2008-01-22 22:25       ` Greg KH [this message]
2008-01-23  1:02         ` Dave Young

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=20080122222550.GB7146@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=a.zummo@towertech.it \
    --cc=cbou@mail.ru \
    --cc=cornelia.huck@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=david-b@pacbell.net \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=hidave.darkstar@gmail.com \
    --cc=jarkao2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stern@rowland.harvard.edu \
    /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;
as well as URLs for NNTP newsgroup(s).