mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-m68k@lists.linux-m68k.org
Subject: Re: linux-next: Tree for Oct 7 (arch/m68k/coldfire/nettel.c)
Date: Thu, 8 Oct 2026 22:37:15 +1000	[thread overview]
Message-ID: <e3031344-a7af-4d8f-804b-6009588acd2a@linux-m68k.org> (raw)
In-Reply-To: <3a927133-3e27-4557-9887-7ed0c7315a7d@infradead.org>


On 8/10/26 08:43, Randy Dunlap wrote:
> 
> 
> On 10/7/26 6:41 AM, Mark Brown wrote:
>> Hi all,
>>
>> Note that I will be travelling to LPC from 2nd-9th October, as a
>> result -next releases will be at best spotty during that time.
>>
>> Changes since 20261006:
> 
> CONFIG_COLDFIRE=y
> CONFIG_M5206e=y
> CONFIG_NETtel=y
> 
> ../arch/m68k/coldfire/nettel.c: In function 'nettel_smc91x_init':
> ../arch/m68k/coldfire/nettel.c:126:9: error: implicit declaration of function 'mcf_setppdata' [-Wimplicit-function-declaration]
>    126 |         mcf_setppdata(0, 0x0080);
> 
> 
> Full randconfig file is attached.

Thanks for letting me know Randy.
FWIW this is not a regression in linux-next, this looks to have been 
broken for a while.

I will issue a fix in the coming days.

Regards
Greg



      reply	other threads:[~2026-10-08 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 13:41 linux-next: Tree for Oct 7 Mark Brown
2026-10-07 22:43 ` linux-next: Tree for Oct 7 (arch/m68k/coldfire/nettel.c) Randy Dunlap
2026-10-08 12:37   ` Greg Ungerer [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=e3031344-a7af-4d8f-804b-6009588acd2a@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®