All of lore.kernel.org
 help / color / mirror / Atom feed
From: saiprakash.ranjan@codeaurora.org
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add DT nodes for watchdog and llcc for SC7180 and SM8150 SoCs
Date: Wed, 11 Dec 2019 07:10:00 +0000	[thread overview]
Message-ID: <0101016ef3cb0b8c-e0a0c552-b148-473a-b247-e633912fcf09-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <20191211070216.GF3143381@builder>

On 2019-12-11 12:32, Bjorn Andersson wrote:
> On Tue 10 Dec 20:30 PST 2019, Sai Prakash Ranjan wrote:
> 
>> This series adds device tree node for watchdog on SC7180 and SM8150.
>> It also adds a node for LLCC (Last level cache controller) on SC7180.
>> 
>> Patch 3 depends on the dt binding change to LLCC node name:
>>  - https://patchwork.kernel.org/patch/11246055/
>> 
> 
> Series applied
> 

Thanks Bjorn !!

--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-12-11  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0101016ef3391259-59ec5f0a-2ae7-45a8-881e-edc2d0bf7b26-000000@us-west-2.amazonses.com>
2019-12-11  7:02 ` [PATCH 0/3] Add DT nodes for watchdog and llcc for SC7180 and SM8150 SoCs Bjorn Andersson
2019-12-11  7:02   ` Bjorn Andersson
2019-12-11  7:10   ` saiprakash.ranjan [this message]
2019-12-11  7:10   ` saiprakash.ranjan
2019-12-11  4:30 Sai Prakash Ranjan
  -- strict thread matches above, loose matches on Subject: below --
2019-12-11  4:30 Sai Prakash Ranjan

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=0101016ef3cb0b8c-e0a0c552-b148-473a-b247-e633912fcf09-000000@us-west-2.amazonses.com \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.