public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Malladi, Meghana" <m-malladi@ti.com>, Arnd Bergmann <arnd@arndb.de>
Cc: quic_bjorande@quicinc.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, srk@ti.com, "Anwar,
	Md Danish" <danishanwar@ti.com>,
	catalin.marinas@arm.com, will@kernel.org
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR driver
Date: Wed, 26 Feb 2025 11:48:48 +0100	[thread overview]
Message-ID: <6081917c-9c20-48fc-baaf-7ac9a9679a72@linaro.org> (raw)
In-Reply-To: <0d33dea6-c021-4f2a-bb3f-92efd6eebd18@ti.com>

On 26/02/2025 11:44, Malladi, Meghana wrote:
> 
> 
> On 2/26/2025 1:35 PM, Krzysztof Kozlowski wrote:
>> On 26/02/2025 07: 18, Malladi, Meghana wrote: > Hi all, > > Apologies in 
>> case you are receiving this email for the second time. > Any reason why 
>> this patch hasn't been merged yet. Other than re-basing > this to the 
>> tip, anything
>> ZjQcmQRYFpfptBannerStart
>> This message was sent from outside of Texas Instruments.
>> Do not click links or open attachments unless you recognize the source 
>> of this email and know the content is safe.
>> Report Suspicious
>> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK! 
>> updgnZav1ue7gKXOnHOpH5hg8gLmw9Osqsqh- 
>> KTLRTnBEurV_VetrG7mzU898vB_5xFrYgbRkkuuFMBobM-uhFAmUgccRSk$>
>> ZjQcmQRYFpfptBannerEnd
>>
>> On 26/02/2025 07:18, Malladi, Meghana wrote:
>>> Hi all,
>>>
>>> Apologies in case you are receiving this email for the second time.

BTW, Arnd when responded with Ack described the process.

>>> Any reason why this patch hasn't been merged yet. Other than re-basing 
>>> this to the tip, anything else which needs to be addressed to get this 
>>> merged?
>>
>> I don't think you sent it to your platform maintainers, so no one would
>> apply it. Usually people ignore emails they did not receive, although I
>> am here an exception tracking missing-DT-patchwork things... :)
>>
>> Best regards,
>> Krzysztof
>>
> 
> Hello Arnd/Krzysztof,
> 
> Thank you for the replies :)
> Was having ambiguity since this is not TI specific change. Wanted to 
> confirm before re-posting. Will post v2 patch including TI platform 
> maintainers.

It is not TI specific? Then which upstream boards benefit from this if
not TI?



Best regards,
Krzysztof


  reply	other threads:[~2025-02-26 11:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  6:00 [PATCH] arm64: defconfig: Enable HSR driver Ravi Gunasekaran
2024-04-19  6:02 ` Arnd Bergmann
2024-04-19  6:25   ` Ravi Gunasekaran
2024-04-19  7:02     ` Arnd Bergmann
2025-02-26  6:14 ` Malladi, Meghana
2025-02-26  6:18 ` Malladi, Meghana
2025-02-26  7:45   ` Arnd Bergmann
2025-02-26  8:05   ` Krzysztof Kozlowski
2025-02-26 10:44     ` [EXTERNAL] " Malladi, Meghana
2025-02-26 10:48       ` Krzysztof Kozlowski [this message]
2025-02-26 11:54         ` Malladi, Meghana
2025-02-26 12:06           ` Krzysztof Kozlowski
2025-02-27  5:43             ` Malladi, Meghana
2025-02-27  7:32               ` Arnd Bergmann

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=6081917c-9c20-48fc-baaf-7ac9a9679a72@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=danishanwar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-malladi@ti.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=srk@ti.com \
    --cc=will@kernel.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