From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Trilok Soni <quic_tsoni@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Alex Elder <elder@linaro.org>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Abel Vesa <abel.vesa@linaro.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Johan Hovold <johan+linaro@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
Vinod Koul <vinod.koul@linaro.org>,
Stephan Gerhold <stephan@gerhold.net>,
Caleb Connolly <kc@postmarketos.org>
Subject: Re: Qualcomm DT bindings and DTS cleanups - tracking community wide
Date: Thu, 6 Oct 2022 09:57:31 +0200 [thread overview]
Message-ID: <0e5438a6-80ba-ace6-b10a-df292c3e82b7@linaro.org> (raw)
In-Reply-To: <943ec4f3-e6a4-7614-fb6f-1adce1487857@quicinc.com>
On 04/10/2022 18:37, Trilok Soni wrote:
>>> If so, where?
>>> A. elinux.org (needs some formatting when pasting the output from tools)
>>> B. gitlab pages/wiki (maybe scripts could parse tools and create the page?)
>>> C. gitlab dedicated repo - some text file
>>> D. Linux kernel TODO file (might be difficult to keep updated)
>>> E. kernel.org wiki (requires LF accounts, AFAIK, a bit pain to edit; I
>>> have it for Exynos but I don't find it usable -
>>> https://exynos.wiki.kernel.org/todo_tasks)
>>
>>
>> Hi All,
>>
>> Any thoughts on this? So far I did not receive any responses, so
>> probably this could mean that there is little interest in this?
>
> My preference for tracking is gitlab. B or C. Everyone will have login
> and understands the workflow.
Thanks Trilok for the input.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-06 7:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:32 Qualcomm DT bindings and DTS cleanups - tracking community wide Krzysztof Kozlowski
2022-10-04 14:50 ` Krzysztof Kozlowski
2022-10-04 16:37 ` Trilok Soni
2022-10-06 7:57 ` Krzysztof Kozlowski [this message]
2022-10-10 10:32 ` Luca Weiss
2022-10-10 15:10 ` Krzysztof Kozlowski
2022-10-10 16:52 ` Neil Armstrong
2022-10-10 11:34 ` Caleb Connolly
2022-10-10 15:10 ` Krzysztof Kozlowski
2022-10-06 8:21 ` Johan Hovold
2022-10-06 8:39 ` Krzysztof Kozlowski
2022-10-06 15:07 ` Johan Hovold
2022-10-06 9:44 ` Dmitry Baryshkov
2022-10-06 15:20 ` Johan Hovold
2022-10-11 13:57 ` Krzysztof Kozlowski
2022-10-13 12:46 ` Krzysztof Kozlowski
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=0e5438a6-80ba-ace6-b10a-df292c3e82b7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=elder@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=kc@postmarketos.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nicolas.dechesne@linaro.org \
--cc=quic_tsoni@quicinc.com \
--cc=robert.foss@linaro.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephan@gerhold.net \
--cc=vinod.koul@linaro.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).