From: Stephan Gerhold <stephan@gerhold.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: defconfig: u8500: Enable CONFIG_GP2AP002
Date: Tue, 14 Apr 2020 11:43:17 +0200 [thread overview]
Message-ID: <20200414094317.GA5896@gerhold.net> (raw)
In-Reply-To: <CACRpkdYW930B-riUi5OnmsDCJD_piJ+321rgB40bq93ndzSp5A@mail.gmail.com>
On Tue, Apr 14, 2020 at 11:08:38AM +0200, Linus Walleij wrote:
> On Sun, Apr 5, 2020 at 7:34 PM Stephan Gerhold <stephan@gerhold.net> wrote:
>
> > sharp,gp2ap002s00f is used as a proximity sensor in
> > samsung-golden and samsung-skomer.
> >
> > Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
>
> Ooops I saw now that I already had this in my "Skomer and misc"
> enablement patch. (rebasing my trees today).
>
> I can put this in front of that patch and take it out of mine if you
> prefer stepwise enablement.
>
Do you mean the "ARM: defconfig: u8500: Enable new drivers for ux500"
patch? It doesn't matter which commit/patch adds it, as long as it ends
up in the u8500_defconfig :)
Thanks,
Stephan
_______________________________________________
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:[~2020-04-14 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 17:32 [PATCH 1/2] ARM: dts: ux500: samsung-golden: Add proximity sensor Stephan Gerhold
2020-04-05 17:32 ` [PATCH 2/2] ARM: defconfig: u8500: Enable CONFIG_GP2AP002 Stephan Gerhold
2020-04-14 9:08 ` Linus Walleij
2020-04-14 9:43 ` Stephan Gerhold [this message]
2020-04-14 9:10 ` [PATCH 1/2] ARM: dts: ux500: samsung-golden: Add proximity sensor Linus Walleij
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=20200414094317.GA5896@gerhold.net \
--to=stephan@gerhold.net \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).