From: "Malladi, Meghana" <m-malladi@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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: Thu, 27 Feb 2025 11:13:22 +0530 [thread overview]
Message-ID: <f1d61696-a5c0-4727-ab52-526294a2a5f9@ti.com> (raw)
In-Reply-To: <a3fc706c-3825-49fc-beea-3fea7d9c0038@linaro.org>
On 2/26/2025 5:36 PM, Krzysztof Kozlowski wrote:
> On 26/02/2025 12: 54, Malladi, Meghana wrote: > Hi Krzysztof, > > On
> 2/26/2025 4: 18 PM, Krzysztof Kozlowski wrote: >> On 26/02/2025 11: 44,
> Malladi, Meghana wrote: > > > On 2/26/2025 1: 35 >> PM, Krzysztof Kozlowski
> 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!
> updgPX1FFo0b4GXEXdPDfwTBSgIATJM2ZirviWBzo9UAByA7dipk7rbevgVn7EQb6-
> DBhdHMpW7WhdxsrgH8RrHp6HnyASM$>
> ZjQcmQRYFpfptBannerEnd
>
> On 26/02/2025 12:54, Malladi, Meghana wrote:
>> Hi Krzysztof,
>>
>> On 2/26/2025 4:18 PM, Krzysztof Kozlowski wrote:
>>> 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
>>> 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!
>>> updq3RaPV007wGXFFrPD30z5a3GGYjpJweyhUcIfUTTaUs-8q0QpC4Yk9azBiFp7cBAf2Knk6fnVs4Fs-zRjTMEn8kmpiGo$>
>>> ZjQcmQRYFpfptBannerEnd
>>>
>>> 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.
>>>
>>
>> Yes, I wanted to re-confirm before posting it again (just in case).
>>
>>>>>> 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?
>>>
>>
>> This change enables generic HSR protocol support in the kernel which is
>> required for HSR driver support in TI boards. When I said "not TI
>> specific" - I meant this change is not internal to TI driver. Hope this
>> clarifies the miscommunication from my earlier mail.
>
> Yes, sure, but this defconfig change benefits and is sent for certain TI
> upstream boards, so it is TI upstream maintainers field. It still fits
> the "Submitting Patches for Given SoC" in SoC maintainer profile.
>
Okay, I got your point now. So as long as this defconfig benefits TI
SoCs, it should be sent with maintainer profile. I will keep that in
mind for future patches as well. Thanks for clarifying this.
Best Regards,
Meghana
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-02-27 5:46 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
2025-02-26 11:54 ` Malladi, Meghana
2025-02-26 12:06 ` Krzysztof Kozlowski
2025-02-27 5:43 ` Malladi, Meghana [this message]
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=f1d61696-a5c0-4727-ab52-526294a2a5f9@ti.com \
--to=m-malladi@ti.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=danishanwar@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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