From: Timur Tabi <timur@codeaurora.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Wei Yongjun <weiyongjun1@huawei.com>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/4] arm64: defconfig: enable new trigger modes for leds
Date: Mon, 23 Oct 2017 21:30:33 -0500 [thread overview]
Message-ID: <5b1f0f4e-edaf-225a-2287-722b16dd88e0@codeaurora.org> (raw)
In-Reply-To: <CAP245DVqNQ2uUZTQmCF0sm_Mya9pWBaeheO4S=BSF7t8juN0YA@mail.gmail.com>
On 10/23/17 6:11 PM, Amit Kucheria wrote:
>> This is great, thanks.
> Can I take this as an ACK?
Sure, but I'm not a maintainer for the defconfig, so it's just my
personal opinion.
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-10-24 2:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:57 [PATCH 0/4] arm64 defconfig: enable additional led triggers Amit Kucheria
2017-10-18 20:57 ` [PATCH 1/4] arm64: defconfig: enable new trigger modes for leds Amit Kucheria
2017-10-19 15:24 ` Timur Tabi
2017-10-23 4:56 ` Amit Kucheria
2017-10-23 15:24 ` Timur Tabi
2017-10-23 23:11 ` Amit Kucheria
2017-10-24 2:30 ` Timur Tabi [this message]
2017-10-24 11:48 ` Manivannan Sadhasivam
2017-10-18 20:57 ` [PATCH 2/4] arm64: dts: qcom: apq8016-sbc: Allow USR4 LED to notify kernel panic Amit Kucheria
2017-10-18 20:57 ` [PATCH 3/4] arm64: dts: hisilicon: hi6220-hikey: Allow USR1 " Amit Kucheria
2017-10-18 20:57 ` [PATCH 4/4] arm64: dts: hisilicon: hi3660-hikey960: Allow USR4 " Amit Kucheria
[not found] ` <CAFGCpxy3v6Z5kTqDEF=mqEpSm2+7pn6jSrotx=sHVBmC=VH3Bw@mail.gmail.com>
2017-10-23 4:43 ` Amit Kucheria
2017-10-24 11:32 ` Guodong Xu
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=5b1f0f4e-edaf-225a-2287-722b16dd88e0@codeaurora.org \
--to=timur@codeaurora.org \
--cc=amit.kucheria@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=weiyongjun1@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome