From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: OMAP3: Remove legacy support for EMA-Tech Stalker board
Date: Wed, 18 Mar 2015 10:41:03 -0700 [thread overview]
Message-ID: <20150318174102.GT31346@atomide.com> (raw)
In-Reply-To: <018901d06150$fbbd27a0$f33776e0$@ema-tech.com>
* Jason <lzg@ema-tech.com> [150318 00:59]:
> Hi Tony,
> I think it's good to remove this legacy code.
> Will let u know once I got the booting dst.
OK I'm planning to queue it for v4.1 merge window then unless
we hear from people using it.
Regards,
Tony
next prev parent reply other threads:[~2015-03-18 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 0:25 [PATCH 0/3] Remove few inactive omap3 legacy board-*.c files Tony Lindgren
2015-03-17 0:25 ` [PATCH 1/3] ARM: OMAP3: Remove legacy support for EMA-Tech Stalker board Tony Lindgren
2015-03-18 7:56 ` Jason
2015-03-18 17:41 ` Tony Lindgren [this message]
2015-03-17 0:25 ` [PATCH 2/3] ARM: OMAP3: Remove legacy support for devkit8000 Tony Lindgren
2015-03-17 0:25 ` [PATCH 3/3] ARM: OMAP2+: Remove legacy support for omap3 TouchBook 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=20150318174102.GT31346@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).