All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: overlapping resources for platform devices?
Date: Wed, 23 Nov 2005 11:52:59 +0000	[thread overview]
Message-ID: <20051123115259.GA9560@flint.arm.linux.org.uk> (raw)
In-Reply-To: <322E3172-BDF9-40BC-A5EC-444C8C33C450@kernel.crashing.org>

On Wed, Nov 23, 2005 at 12:57:40AM -0600, Kumar Gala wrote:
> Any update?

It should be okay, but I'll step back from saying "safe" because
I don't particularly like the insert_resource() concept.

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

  reply	other threads:[~2005-11-23 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 23:31 overlapping resources for platform devices? Kumar Gala
2005-11-16  6:41 ` Greg KH
2005-11-17 15:36   ` Kumar Gala
2005-11-17 15:49     ` Russell King
2005-11-23  6:57       ` Kumar Gala
2005-11-23 11:52         ` Russell King [this message]
2005-11-23 18:48           ` Kumar Gala
2005-11-23 22:30             ` Russell King

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=20051123115259.GA9560@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=galak@kernel.crashing.org \
    --cc=greg@kroah.com \
    --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 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.