From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Magnus <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 0/2] arm64: defconfig: ak4613/renesas sound will be kernle module
Date: Wed, 21 Jun 2017 14:21:11 +0200 [thread overview]
Message-ID: <CAMuHMdUjMb85X17H9xYDQgTrRSCRFzTPDyEg4WCfmC8gHrk=XA@mail.gmail.com> (raw)
In-Reply-To: <20170621120309.GD17965@verge.net.au>
Hi Simon,
On Wed, Jun 21, 2017 at 2:03 PM, Simon Horman <horms@verge.net.au> wrote:
> Compile the renesas sound and ak4613 drivers to reduce the ARM64 kernel
... as modules ...
Else you increase size ;-)
> size. These modules are currently only used by Renesas platforms so
> there should little risk of negative impact of this change on other users.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-06-21 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 0:23 [PATCH 0/2] arm64: defconfig: ak4613/renesas sound will be kernle module Kuninori Morimoto
2017-06-19 0:23 ` [PATCH 1/2] arm64: defconfig: compile ak4613 as kernel module Kuninori Morimoto
2017-06-19 0:24 ` [PATCH 2/2] arm64: defconfig: compile renesas sound " Kuninori Morimoto
2017-06-20 13:20 ` [PATCH 0/2] arm64: defconfig: ak4613/renesas sound will be kernle module Simon Horman
2017-06-21 0:10 ` Kuninori Morimoto
2017-06-21 12:03 ` Simon Horman
2017-06-21 12:21 ` Geert Uytterhoeven [this message]
2017-06-22 9:02 ` 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='CAMuHMdUjMb85X17H9xYDQgTrRSCRFzTPDyEg4WCfmC8gHrk=XA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.