linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: javier@osg.samsung.com (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ARM: multi_v7_defconfig: Build Atmel maXTouch driver as a module
Date: Mon, 5 Sep 2016 01:31:22 +0200	[thread overview]
Message-ID: <d1992291-d314-0a08-bbb2-a1682bd126f8@osg.samsung.com> (raw)
In-Reply-To: <7304023.0tarkq2cRD@wuerfel>

Hello Arnd,

On 09/02/2016 05:38 PM, Arnd Bergmann wrote:
> On Tuesday, August 16, 2016 11:08:14 AM CEST Javier Martinez Canillas wrote:
>> The driver is for a trackpad device so is not needed for booting and
>> makes more sense to have it as module to reduce the kernel image size.
>>
>> It was probably enabled as built-in because module autoload was not
>> working when the I2C device was registered by OF but this got fixed
>> in commit b7d21058b40b ("Input: atmel_mxt_ts - add maxtouch to I2C
>> table for module autoload") so it's safe to enable as a module now.
>>
>> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>>
>> ---
> 
> Applied to next/defconfig.
> 

Thanks.

> My preferred way is to get defconfig updates forwarded by the platform
> maintainers that are interested, but this seems to apply to multiple
> platforms, so I'm not asking you to pick one to resend it to.
> 

Yes. I usually route defconfig patches through a platform maintainer, but as
you said, this driver is used by different platforms so I decided to send it
to you directly since I didn't know which platform to choose.

Sorry if that caused inconveniences.

> 	Arnd
> 

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

      reply	other threads:[~2016-09-04 23:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 15:08 [RESEND PATCH] ARM: multi_v7_defconfig: Build Atmel maXTouch driver as a module Javier Martinez Canillas
2016-09-02 15:38 ` Arnd Bergmann
2016-09-04 23:31   ` Javier Martinez Canillas [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=d1992291-d314-0a08-bbb2-a1682bd126f8@osg.samsung.com \
    --to=javier@osg.samsung.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).