public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kumar Gala <galak@gate.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: platform_device_add_resources doesn't request the resources?
Date: Wed, 4 Jan 2006 17:27:12 +0000	[thread overview]
Message-ID: <20060104172712.GA3119@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0601041104560.32358-100000@gate.crashing.org>

On Wed, Jan 04, 2006 at 11:07:51AM -0600, Kumar Gala wrote:
> Is there any reason that platform_device_add_resources doesn't process the 
> resources that are passed to it like platform_device_add does?

Yes.  Please dig out the example usage in the change comments which
introduced it.  The use is clearly explained in there.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-01-04 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 17:07 platform_device_add_resources doesn't request the resources? Kumar Gala
2006-01-04 17:27 ` Russell King [this message]
2006-01-04 17:25   ` Kumar Gala

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=20060104172712.GA3119@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=galak@gate.crashing.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox