devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: liviu.dudau@arm.com, devicetree@vger.kernel.org,
	Sudeep Holla <sudeep.holla@arm.com>,
	linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
	linux-kernel@vger.kernel.org, lorenzo.pieralisi@arm.com,
	mathieu.poirier@linaro.org, suzuki.poulose@arm.com,
	robh+dt@kernel.org
Subject: Re: [PATCH RESEND 0/1] arm64: dts: Juno CTI device tree additions
Date: Wed, 9 Mar 2022 11:50:16 +0000	[thread overview]
Message-ID: <YiiUePW2DESezPLo@bogus> (raw)
In-Reply-To: <20220309113117.1126-1-mike.leach@linaro.org>

On Wed, Mar 09, 2022 at 11:31:16AM +0000, Mike Leach wrote:
> This is a resend of a patch from some time ago (04/2020)[1] which seems to
> have fallen through the cracks - most likely as last time I mistakenly
> tagged it as dt-bindings: rather than dts:
>

Quite likely, but I vaguely remember this and I assume the bindings had
on-going discussions at that time.

> I am planning a release of additional CTI configuration examples, which
> include some for Juno - so this is now needed upstream to support that work.
>
> Patch unchanged, other than a correction to the subject.
>

That may not work. I haven't tried applying but it would be good to
post it rebasing on -next at this moment or after v5.18-rc1 is released.
I have already sent v5.18 material, so I need to queue this for v5.19.
So preferable post the rebase version at v5.18-rc1 in 2+ weeks time.
We have had some restructuring including the new scmi version of DTB
in the mainline or queued in -next at the moment.

Sorry for missing this last time.

> [1] https://lore.kernel.org/linux-arm-kernel/20200415201330.15894-1-mike.leach@linaro.org/
> 
> 
> Mike Leach (1):
>   arm64: dts: arm:  Juno - add CTI entries to device tree
>

No need of the cover letter for one patch, just post the patch next time.

-- 
Regards,
Sudeep

  parent reply	other threads:[~2022-03-09 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 11:31 [PATCH RESEND 0/1] arm64: dts: Juno CTI device tree additions Mike Leach
2022-03-09 11:31 ` [PATCH RESEND 1/1] arm64: dts: arm: Juno - add CTI entries to device tree Mike Leach
2022-03-09 11:50 ` Sudeep Holla [this message]
2022-03-09 13:49   ` [PATCH RESEND 0/1] arm64: dts: Juno CTI device tree additions Mike Leach

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=YiiUePW2DESezPLo@bogus \
    --to=sudeep.holla@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).