From: Felipe Balbi <balbi@ti.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: balbi@ti.com, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] dt: remove of_alias_get_id() reference
Date: Thu, 4 Aug 2011 14:47:27 +0300 [thread overview]
Message-ID: <20110804114725.GK17540@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <CACxGe6vnspztEnUH5odGnK4x_K9Ej3Nt7BxikVQwOr9Uh_ED7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]
On Thu, Aug 04, 2011 at 12:42:41PM +0100, Grant Likely wrote:
> On Thu, Aug 4, 2011 at 11:33 AM, Felipe Balbi <balbi@ti.com> wrote:
> > On Thu, Aug 04, 2011 at 11:30:27AM +0100, Grant Likely wrote:
> >> of_alias_get_id() is broken and being reverted. Remove the reference
> >> to it and replace with a single incrementing id number.
> >>
> >> There is no risk of regression here on the imx driver since the imx
> >> change to use of_alias_get_id() is commit 22698aa2, "serial/imx: add
> >> device tree probe support" which is new for v3.1, and it won't get
> >> used unless CONFIG_OF is enabled and the board is booted using a
> >> device tree. A single incrementing integer is sufficient for now.
> >>
> >> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> >> Acked-by: Shawn Guo <shawn.guo@linaro.org>
> >> ---
> >>
> >> I'm about to ask Linus to pull this patch through the devicetree/merge
> >> branch along with the of_alias revert.
> >>
> >> drivers/tty/serial/imx.c | 13 ++++---------
> >> 1 files changed, 4 insertions(+), 9 deletions(-)
> >>
> >> diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> >> index 827db76..7e91b3d 100644
> >> --- a/drivers/tty/serial/imx.c
> >> +++ b/drivers/tty/serial/imx.c
> >> @@ -1286,22 +1286,17 @@ static int serial_imx_resume(struct platform_device *dev)
> >> static int serial_imx_probe_dt(struct imx_port *sport,
> >> struct platform_device *pdev)
> >> {
> >> + static int portnum = 0;
> >
> > would it be better to use an IDR here ?
>
> Hmmm, I've not looked at idr before. Yes, it would probably be the
> right thing to do. This patch is needed to fix a build failure, but
> when it is reworked for v3.2 I think idr should be considered.
> Thanks!
no problem ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-08-04 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:30 [PATCH] dt: remove of_alias_get_id() reference Grant Likely
2011-08-04 10:33 ` Felipe Balbi
[not found] ` <20110804103336.GE17540-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-08-04 11:42 ` Grant Likely
2011-08-04 11:47 ` Felipe Balbi [this message]
2011-08-04 17:13 ` Shawn Guo
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=20110804114725.GK17540@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.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;
as well as URLs for NNTP newsgroup(s).