From: Linus Walleij <linus.walleij@linaro.org>
To: Brian Masney <masneyb@onstation.org>
Cc: Andy Gross <andy.gross@linaro.org>,
linux-arm-msm@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: qcom_defconfig: add options for LG Nexus 5 phone
Date: Tue, 5 Mar 2019 08:50:45 +0100 [thread overview]
Message-ID: <CACRpkdYGnAxCteTuCbwJY_StrGm0BJ9ThQAdEEKCUYpF8AL_hw@mail.gmail.com> (raw)
In-Reply-To: <20190210121657.4200-1-masneyb@onstation.org>
On Sun, Feb 10, 2019 at 1:17 PM Brian Masney <masneyb@onstation.org> wrote:
> Add wcn36xx wireless, msm vibrator, pm8941 power key, bq24190 charger,
> spmi-iadc, spmi-vadc, mpu6515 gyroscope / accelerometer, and tsl2772
> proximity / light drivers as modules to support the LG Nexus 5
> (hammerhead) phone.
>
> CFG80211 is changed to be a module to match MAC80211 since this isn't
> required for initial bootup.
>
> Device manager support is also added as a module since this is needed by
> postmarketOS.
>
> Signed-off-by: Brian Masney <masneyb@onstation.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Brian if this doesn't get applied because of the occasional maintainer overload
just send it directly to the ARM SoC maintainers arm@kernel.org that's
what I do.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-05 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 12:16 [PATCH] ARM: qcom_defconfig: add options for LG Nexus 5 phone Brian Masney
2019-03-05 7:50 ` Linus Walleij [this message]
2019-03-06 8:21 ` Andy Gross
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=CACRpkdYGnAxCteTuCbwJY_StrGm0BJ9ThQAdEEKCUYpF8AL_hw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.gross@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masneyb@onstation.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).