From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "Enric Balletbò i Serra" <eballetbo@gmail.com>,
"Tom Rini" <trini@ti.com>,
"Russell King" <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] ARM: OMAP3: igep0020: set GPIO mode for mux mcspi1_cs2 pin
Date: Wed, 18 Jul 2012 00:20:53 -0700 [thread overview]
Message-ID: <20120718072052.GK6522@atomide.com> (raw)
In-Reply-To: <CABxcv=miEavW5Qf-Y+S4Nph+ah5gQ6QDpt-T44tdHLBxcP8pqQ@mail.gmail.com>
* Javier Martinez Canillas <javier@dowhile0.org> [120717 00:16]:
>
> Hi Tony,
>
> Just pinging to see if you have further comments on this patch or if
> it can be applied. It solves a bug on IGEPv2 boards.
>
> I know the trend is to move away from board code. I'll start working
> on an device tree for the IGEPv2 but it will take some time until is
> ready (and I'm not sure if all the OMAP3 support is already present on
> DT).
>
> So could you please take bug fixes for the board code in the meantime?
Yes seems like something for the v3.6-rc series.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP3: igep0020: set GPIO mode for mux mcspi1_cs2 pin
Date: Wed, 18 Jul 2012 00:20:53 -0700 [thread overview]
Message-ID: <20120718072052.GK6522@atomide.com> (raw)
In-Reply-To: <CABxcv=miEavW5Qf-Y+S4Nph+ah5gQ6QDpt-T44tdHLBxcP8pqQ@mail.gmail.com>
* Javier Martinez Canillas <javier@dowhile0.org> [120717 00:16]:
>
> Hi Tony,
>
> Just pinging to see if you have further comments on this patch or if
> it can be applied. It solves a bug on IGEPv2 boards.
>
> I know the trend is to move away from board code. I'll start working
> on an device tree for the IGEPv2 but it will take some time until is
> ready (and I'm not sure if all the OMAP3 support is already present on
> DT).
>
> So could you please take bug fixes for the board code in the meantime?
Yes seems like something for the v3.6-rc series.
Regards,
Tony
next prev parent reply other threads:[~2012-07-18 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 1:57 [PATCH 1/1] ARM: OMAP3: igep0020: set GPIO mode for mux mcspi1_cs2 pin Javier Martinez Canillas
2012-07-10 1:57 ` Javier Martinez Canillas
2012-07-10 7:24 ` Enric Balletbò i Serra
2012-07-10 7:24 ` Enric Balletbò i Serra
2012-07-17 7:11 ` Javier Martinez Canillas
2012-07-17 7:11 ` Javier Martinez Canillas
2012-07-18 7:20 ` Tony Lindgren [this message]
2012-07-18 7:20 ` Tony Lindgren
2012-08-03 8:06 ` Javier Martinez Canillas
2012-08-03 8:06 ` Javier Martinez Canillas
2012-08-07 7:04 ` Tony Lindgren
2012-08-07 7:04 ` Tony Lindgren
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=20120718072052.GK6522@atomide.com \
--to=tony@atomide.com \
--cc=eballetbo@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=trini@ti.com \
/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.