All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ashish Mhetre <amhetre@nvidia.com>,
	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: Sat, 2 Dec 2023 13:10:35 +0100	[thread overview]
Message-ID: <cdb7c02f-a314-4e64-b95c-66c91e83d4d5@linaro.org> (raw)
In-Reply-To: <8b44e417-e9dc-4d6f-b0ae-f9834d0624ac@infradead.org>

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.

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.

Best regards,
Krzysztof


  reply	other threads:[~2023-12-02 12:10 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 [this message]
2023-12-05  4:11     ` Ashish Mhetre

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=cdb7c02f-a314-4e64-b95c-66c91e83d4d5@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=amhetre@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.