From: Fabio Estevam <festevam@gmail.com>
To: Subodh Nijsure <snijsure@grid-net.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
marex@denx.de, kernel@pengutronix.de, rob.herring@calxeda.com,
Grant Likely <grant.likely@secretlab.ca>,
linux-serial@vger.kernel.org, shawn.guo@linaro.org,
"Matt@grid-net.com" <Matt@grid-net.com>,
linux-arm-kernel@lists.infradead.org,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH v4 2/2] serial: mxs-auart: Allow device tree probing
Date: Mon, 18 Jun 2012 17:50:49 -0300 [thread overview]
Message-ID: <CAOMZO5CHJGCE0fwh=u65gO7P8c8hT9Yd5+3__rFtmNMLstTwEQ@mail.gmail.com> (raw)
In-Reply-To: <4FDF929B.7000809@grid-net.com>
On Mon, Jun 18, 2012 at 5:42 PM, Subodh Nijsure <snijsure@grid-net.com> wrote:
>
> If one were to try run console on one of the /dev/ttyAPP* ports, as is the
> case for hardware I am working with, console output wouldn't show up without
> the following diff:
>
> Let me know if should send formal patch or we can include it as part of v5?
Please send a formal patch. Shawn has already applied my patch into his tree:
http://git.linaro.org/gitweb?p=people/shawnguo/linux-2.6.git;a=shortlog;h=refs/heads/mxs/for-next
next prev parent reply other threads:[~2012-06-18 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1339774557-23588-1-git-send-email-fabio.estevam@freescale.com>
2012-06-15 15:35 ` [PATCH v3 2/2] serial: mxs-auart: Allow device tree probing Fabio Estevam
2012-06-15 15:48 ` Marek Vasut
2012-06-15 16:06 ` Shawn Guo
2012-06-15 16:11 ` Fabio Estevam
2012-06-15 16:16 ` Marek Vasut
2012-06-15 16:18 ` Fabio Estevam
2012-06-15 17:00 ` Marek Vasut
2012-06-16 2:01 ` Shawn Guo
2012-06-16 1:59 ` Shawn Guo
2012-06-18 13:06 ` [PATCH v4 " Fabio Estevam
2012-06-18 13:33 ` Shawn Guo
2012-06-18 13:36 ` Marek Vasut
2012-06-18 15:25 ` Greg Kroah-Hartman
2012-06-18 20:42 ` Subodh Nijsure
2012-06-18 20:50 ` Fabio Estevam [this message]
2012-07-13 10:33 ` Marc Kleine-Budde
2012-07-13 10:35 ` Marc Kleine-Budde
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='CAOMZO5CHJGCE0fwh=u65gO7P8c8hT9Yd5+3__rFtmNMLstTwEQ@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=Matt@grid-net.com \
--cc=alan@linux.intel.com \
--cc=fabio.estevam@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=marex@denx.de \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=snijsure@grid-net.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 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).