From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Benoit Cousson <b-cousson@ti.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] Documentation: dt: update TI GPMC ethernet binding properties
Date: Tue, 9 Apr 2013 09:58:00 -0700 [thread overview]
Message-ID: <20130409165759.GO10155@atomide.com> (raw)
In-Reply-To: <51644151.2080200@ti.com>
* Jon Hunter <jon-hunter@ti.com> [130409 09:31]:
>
> On 04/09/2013 07:11 AM, Javier Martinez Canillas wrote:
> > The GPMC timing properties for device-tree have been updated
> > by adding a "-ns" or "-ps" suffix to indicate the units of
> > time the property represents. Therefore, update the timing
> > property names for TI GPMC ethernet binding.
> >
> > Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > ---
> >
> > Jon, Benoit:
> >
> > Sorry that I didn't send this patch before but I just realized
> > that the GPMC timing properties changed after
> >
> > commit 5330dc16 ("ARM: OMAP2+: Add GPMC DT support for Ethernet child nodes")
> >
> > got queued.
>
> Thanks, I missed this one too. Looks like I need to update the gpmc-nand
> documentation as well :-(
>
> > Tony,
> >
> > Is still possible to queue this patch on your omap-for-v3.10/gpmc branch
> > or it is too late?
>
> If it is I think that this could be queued as a fix. Tony?
Yes let's plan on making this a fix. Then it can be merged during
the merge window or right after it.
Regards,
Tony
prev parent reply other threads:[~2013-04-09 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 12:11 [PATCH 1/1] Documentation: dt: update TI GPMC ethernet binding properties Javier Martinez Canillas
2013-04-09 16:26 ` Jon Hunter
2013-04-09 16:58 ` Tony Lindgren [this message]
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=20130409165759.GO10155@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=javier.martinez@collabora.co.uk \
--cc=jon-hunter@ti.com \
--cc=linux-omap@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.