public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Kartik Rajput <kkartik@nvidia•com>
To: "sfr@canb•auug.org.au" <sfr@canb•auug.org.au>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
	"rdunlap@infradead•org" <rdunlap@infradead•org>
Cc: "linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	Thierry Reding <treding@nvidia•com>
Subject: Re: linux-next: Tree for Dec 19 (drivers/soc/tegra/fuse/fuse-tegra30.c)
Date: Wed, 20 Dec 2023 06:13:24 +0000	[thread overview]
Message-ID: <ad24207b11d27466aa84328d1f91a34fff8540ab.camel@nvidia.com> (raw)
In-Reply-To: <e7529a79-73d1-48be-9f98-aed9793b2bc6@infradead.org>

On Tue, 2023-12-19 at 15:04 -0800, Randy Dunlap wrote:
> 
> 
> On 12/18/23 20:41, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20231218:
> > 
> 
> on arm64:
> 
> ../drivers/soc/tegra/fuse/fuse-tegra30.c:698:28: error:
> 'tegra194_soc_attr_group' undeclared here (not in a function); did
> you mean 'tegra_soc_attr_group'?
>   698 |         .soc_attr_group = &tegra194_soc_attr_group,
>       |                            ^~~~~~~~~~~~~~~~~~~~~~~
>       |                            tegra_soc_attr_group
> 
> 
> Full randconfig file is attached.
> 
> -- 
> #Randy
> https://people.kernel.org/tglx/notes-about-netiquette
> https://subspace.kernel.org/etiquette.html

Thanks Randy, Stephen, for reporting this.

I've posted
fix https://lore.kernel.org/linux-tegra/20231220061013.120173-1-kkartik@nvidia.com/T/#u
for this.

Regards,
Kartik

next prev parent reply	other threads:[~2023-12-20  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  4:41 linux-next: Tree for Dec 19 Stephen Rothwell
2023-12-19 23:04 ` linux-next: Tree for Dec 19 (drivers/soc/tegra/fuse/fuse-tegra30.c) Randy Dunlap
2023-12-20  6:13   ` Kartik Rajput [this message]
2023-12-19 23:43 ` linux-next: Tree for Dec 19 [sound/pci/hda/snd-hda-scodec-cs35l41.ko] Randy Dunlap

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=ad24207b11d27466aa84328d1f91a34fff8540ab.camel@nvidia.com \
    --to=kkartik@nvidia$(echo .)com \
    --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 \
    --cc=treding@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox