From: Ashish Mhetre <amhetre@nvidia•com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro•org>,
Randy Dunlap <rdunlap@infradead•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Nov 27 (drivers/memory/tegra/tegra186.c)
Date: Tue, 5 Dec 2023 09:41:28 +0530 [thread overview]
Message-ID: <c361dbe4-1ef3-4f92-8fb5-9de184b0bf38@nvidia.com> (raw)
In-Reply-To: <cdb7c02f-a314-4e64-b95c-66c91e83d4d5@linaro.org>
On 12/2/2023 5:40 PM, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
>
>
> On 28/11/2023 01:31, Randy Dunlap wrote:
>>
>> On 11/26/23 20:05, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20231124:
>>>
>> on ARCH=arm64:
>> when CONFIG_IOMMU_API is not set:
>>
>> ../drivers/memory/tegra/tegra186.c: In function 'tegra186_mc_resume':
>> ../drivers/memory/tegra/tegra186.c:149:17: error: implicit declaration of function 'tegra186_mc_client_sid_override' [-Werror=implicit-function-declaration]
>> 149 | tegra186_mc_client_sid_override(mc, client, client->sid);
> Ashish,
>
> This was reported few days ago and still no fix or comment. So we are
> repeating the same case happened weeks ago with other LKP reported issue
> - I need to ping you, otherwise you will not address reports in your
> code. We all expect that contributor addresses the reports related to
> their code.
Hi Krzysztof,
Sorry, I am not sure why but I have not received the original mail.
I searched my entire inbox but couldn't find it. I'll check my mail
settings. Same thing happened for that LKP report mail as well.
I came to know about it only when you added me in 'To' and added
'linux-tegra' mailing list.
For the LKP report, I had replied to you and was waiting for your
response.
>
> Knowing this I will double think before I take any code from you.
>
> I am planning to drop this code next week, unless some fix comes.
I'll send a fix for it today.
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2023-12-05 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 4:05 linux-next: Tree for Nov 27 Stephen Rothwell
2023-11-28 0:31 ` linux-next: Tree for Nov 27 (drivers/memory/tegra/tegra186.c) Randy Dunlap
2023-12-02 12:10 ` Krzysztof Kozlowski
2023-12-05 4:11 ` Ashish Mhetre [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=c361dbe4-1ef3-4f92-8fb5-9de184b0bf38@nvidia.com \
--to=amhetre@nvidia$(echo .)com \
--cc=krzysztof.kozlowski@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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