From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Robert Foss <robert.foss@linaro.org>
Cc: jonathan@marek.ca, andrey.konovalov@linaro.org,
todor.too@gmail.com, agross@kernel.org,
bjorn.andersson@linaro.org, jgrahsl@snap.com, hfink@snap.com,
dmitry.baryshkov@linaro.org, devicetree@vger.kernel.org,
Rob Herring <robh@kernel.org>,
hverkuil@xs4all.nl, mchehab@kernel.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v3 01/19] media: dt-bindings: media: camss: Add qcom,sm8250-camss binding
Date: Wed, 5 Jan 2022 01:15:13 +0000 [thread overview]
Message-ID: <8d66b058-690c-281d-2f4f-774681cf4dda@linaro.org> (raw)
In-Reply-To: <6baa737b-441a-3dfe-f363-aaf4d4fd62c8@linaro.org>
On 04/01/2022 20:44, Bryan O'Donoghue wrote:
> Please don't apply V3 for now
I see the pull-request is already active
That's no problem I'll make a new patchset to
- Add regulator-bulk support to camss
- Fixing RB3/SDM845
- Fixing RB5/SM8250
- Fixing SDM660
These three platforms work fine as is we just
need to fixup the description of the regulators
- And add in the sensors for the RB5 which
is where most of the changes to my branch are
and have no been submitted to this list yet
Seems less confusing that way. I'll see if I can get that patchset out
tomorrow
---
bod
prev parent reply other threads:[~2022-01-05 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211222003751.2461466-1-bryan.odonoghue@linaro.org>
2021-12-22 0:37 ` [PATCH v3 01/19] media: dt-bindings: media: camss: Add qcom,sm8250-camss binding Bryan O'Donoghue
2022-01-04 13:42 ` Vladimir Zapolskiy
2022-01-04 15:28 ` Bryan O'Donoghue
2022-01-04 20:44 ` Bryan O'Donoghue
2022-01-05 1:15 ` Bryan O'Donoghue [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=8d66b058-690c-281d-2f4f-774681cf4dda@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hfink@snap.com \
--cc=hverkuil@xs4all.nl \
--cc=jgrahsl@snap.com \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robert.foss@linaro.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@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).