public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: treding@nvidia.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] drm/tegra: fix another missing include
Date: Wed, 5 Apr 2023 14:05:40 +0200	[thread overview]
Message-ID: <ZC1kFMgpXlqVErTi@orome> (raw)
In-Reply-To: <20230405114443.113834-1-christian.koenig@amd.com>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

On Wed, Apr 05, 2023 at 01:44:43PM +0200, Christian König wrote:
> Since tegra now compile tests on other platforms the kernel test robot
> started to complain that this here is not pulled in under all
> conditions.
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202304050946.yGGTKkcr-lkp@intel.com/
> ---
>  drivers/gpu/drm/tegra/fb.c | 1 +
>  1 file changed, 1 insertion(+)

I had meant to bring this up in response to the other patch that you had
sent but then forgot. One of the sanity scripts I run complains that you
have different email addresses in the author and Signed-off-by: fields.
I already fixed that up for the original patch (I used the Signed-off-by
email for the author as well). Let me know if that's not how you want to
handle this.

May also be worth fixing up your setup so it doesn't generate these
conflicting entries.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-04-05 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 11:44 [PATCH] drm/tegra: fix another missing include Christian König
2023-04-05 12:05 ` Thierry Reding [this message]
2023-04-05 12:14   ` Christian König
2023-04-05 13:48     ` Thierry Reding

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=ZC1kFMgpXlqVErTi@orome \
    --to=thierry.reding@gmail.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=treding@nvidia.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