From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: lpc32xx: updates to lpc32xx_defconfig
Date: Mon, 25 Apr 2016 04:04:20 +0300 [thread overview]
Message-ID: <571D6D14.10108@mleia.com> (raw)
In-Reply-To: <1461545845-25338-1-git-send-email-vz@mleia.com>
On 25.04.2016 03:57, Vladimir Zapolskiy wrote:
> The changeset updates lpc32xx_defconfig to match savedefconfig
> and adds ARM PrimeCell PL175 memory controller driver to a build.
>
> Vladimir Zapolskiy (2):
> ARM: LPC32xx: defconfig update
> ARM: LPC32xx: add PL175 memory controller driver to defconfig
>
> arch/arm/configs/lpc32xx_defconfig | 29 +++++++++++------------------
> 1 file changed, 11 insertions(+), 18 deletions(-)
>
This is an outdated cover letter, please discard it.
Sorry for noise.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-04-25 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 0:57 [PATCH 0/2] ARM: lpc32xx: updates to lpc32xx_defconfig Vladimir Zapolskiy
2016-04-25 1:04 ` Vladimir Zapolskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-18 3:31 Vladimir Zapolskiy
2016-04-18 15:05 ` Arnd Bergmann
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=571D6D14.10108@mleia.com \
--to=vz@mleia.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).