From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: Remove EMEV2 header file
Date: Tue, 18 Feb 2014 02:31:06 +0000 [thread overview]
Message-ID: <20140218023103.GA17063@verge.net.au> (raw)
In-Reply-To: <20140218000926.GB4776@verge.net.au>
On Tue, Feb 18, 2014 at 09:09:29AM +0900, Simon Horman wrote:
> On Mon, Feb 17, 2014 at 04:35:08PM +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > There is no C board code left for the EMEV2 SoC, so
> > get rid of the emev2.h include file to save some lines.
> > While at it make functions static.
> >
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Thanks, I have queued this up.
I have changed my mind and decided to defer this patch
to avoid a tedious dependency of an SoC patch on a board patch.
next prev parent reply other threads:[~2014-02-18 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 7:35 [PATCH] ARM: shmobile: Remove EMEV2 header file Magnus Damm
2014-02-18 0:09 ` Simon Horman
2014-02-18 2:31 ` Simon Horman [this message]
2014-02-18 2:35 ` Magnus Damm
2014-03-07 2:38 ` Simon Horman
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=20140218023103.GA17063@verge.net.au \
--to=horms@verge.net.au \
--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).