From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: shmobile: r7s72100: genmai: CONFIG_MACH_GENMAI
Date: Wed, 16 Jul 2014 13:59:42 +0200 [thread overview]
Message-ID: <1741462.gsq1khyh60@avalon> (raw)
In-Reply-To: <1405509309.4408.36.camel@x220>
Hi Paul,
On Wednesday 16 July 2014 13:15:09 Paul Bolle wrote:
> Commit bec652e2fbfe ("ARM: shmobile: r7s72100: genmai: Remove legacy
> board file") is included in linux-next as of next-20140716.
>
> It removed the Kconfig symbol MACH_GENMAI (twice!). It also removed its
> macro from a Makefile. It did not touch its macro from
> arch/arm/mach-shmobile/Makefile.boot.
That was a mistake, sorry.
> Is the trivial patch to remove CONFIG_MACH_GENMAI from that Makefile
> queued somewhere?
Not yet. I've just sent "[PATCH] ARM: shmobile: Remove MACH_GENMAI from
Makefile.boot" to the linux-sh mailing list.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2014-07-16 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 11:15 ARM: shmobile: r7s72100: genmai: CONFIG_MACH_GENMAI Paul Bolle
2014-07-16 11:59 ` Laurent Pinchart [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=1741462.gsq1khyh60@avalon \
--to=laurent.pinchart@ideasonboard.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).