From: Kumar Gala <kumar.gala@freescale.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Kumar Gala" <galak@linen.sps.mot.com>,
<linux-kernel@vger.kernel.org>, <rmk@arm.linux.org.uk>,
<akpm@osdl.org>
Subject: Re: [RFC][PATCH] Add platform_get_resource_byname & platform_get_resource_byirq
Date: Tue, 4 Jan 2005 09:53:35 -0600 [thread overview]
Message-ID: <CACE2CCC-5E68-11D9-BC22-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <20041217221129.GA22885@kroah.com>
Greg,
Any update on when these patches will go to linus or akpm.
thanks
- kumar
On Dec 17, 2004, at 4:11 PM, Greg KH wrote:
> On Wed, Dec 08, 2004 at 05:16:16PM -0600, Kumar Gala wrote:
> > Adds the ability to find a resource or irq on a platform device by
> its
> > resource name. This patch also tweaks how resource names get set.
> > Before, resources names were set to pdev->dev.bus_id, now that only
> > happens if the resource name has not been previous set.
> >
> > All of this allows us to find a resource without assuming what order
> the
> > resources are in.
> >
> > Signed-off-by; Kumar Gala <kumar.gala@freescale.com>
>
> Thanks, I've applied this (minus the bogus .h file, and plus the proper
> .h file change.)
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-01-04 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 23:16 [RFC][PATCH] Add platform_get_resource_byname & platform_get_resource_byirq Kumar Gala
2004-12-08 23:26 ` [PATCH] Add prototypes for " Kumar Gala
2004-12-09 0:03 ` [RFC][PATCH] Add " Kumar Gala
2004-12-17 22:11 ` Greg KH
2005-01-04 15:53 ` Kumar Gala [this message]
2005-01-11 1:19 ` 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=CACE2CCC-5E68-11D9-BC22-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=galak@linen.sps.mot.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).