From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <p.zabel@pengutronix.de>,
<linus.walleij@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3 v7] Misc SCM changes
Date: Wed, 25 Oct 2023 18:16:34 +0530 [thread overview]
Message-ID: <be86eca9-1bdb-eae9-6d00-8349de2c6166@quicinc.com> (raw)
In-Reply-To: <CAA8EJprTCWevfRNdVDV5xpgNu-Fh21HGM_eS2pOUuZJesgCD6Q@mail.gmail.com>
On 10/25/2023 1:37 AM, Dmitry Baryshkov wrote:
> On Wed, 4 Oct 2023 at 20:26, Mukesh Ojha <quic_mojha@quicinc.com> wrote:
>>
>> I have given version to this series as v7 as it has already
>> gone through v6 and later got added to minidump patch series
>> However, these 3 patches can go independently and has no
>> relation with minidump hence, separated it from minidump series.
>
> Please describe the merge strategy, since these patches cross the
> subsystem boundary. Linusw has acked patch2, which might mean that he
> is fine for it to be merged via the arm-soc? tree. However as nothing
> was mentioned in the cover letter, Bjorn has marked patch2 as not
> applicable (as it is outside of the usual subsystem area).
Thanks for your time in reviewing this series.
Sent another version here after addressing the comments.
https://lore.kernel.org/lkml/1698235506-16993-1-git-send-email-quic_mojha@quicinc.com/
-Mukesh
>
prev parent reply other threads:[~2023-10-25 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:25 Mukesh Ojha
2023-10-04 17:25 ` [PATCH v7 1/3] firmware: qcom_scm: provide a read-modify-write function Mukesh Ojha
2023-10-24 19:59 ` Dmitry Baryshkov
2023-10-04 17:25 ` [PATCH v7 2/3] pinctrl: qcom: Use qcom_scm_io_update_field() Mukesh Ojha
2023-10-04 17:25 ` [PATCH v7 3/3] firmware: scm: Modify only the download bits in TCSR register Mukesh Ojha
2023-10-24 19:53 ` Dmitry Baryshkov
2023-10-24 13:29 ` [PATCH 0/3 v7] Misc SCM changes Kathiravan Thirumoorthy
2023-10-24 15:08 ` Dmitry Baryshkov
[not found] ` <d6f48748-22c4-4e4c-a1e9-7a6940b9b432@quicinc.com>
2023-10-24 20:04 ` Dmitry Baryshkov
2023-10-25 3:49 ` Kathiravan Thirumoorthy
2023-10-24 20:07 ` Dmitry Baryshkov
2023-10-25 12:46 ` Mukesh Ojha [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=be86eca9-1bdb-eae9-6d00-8349de2c6166@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®