From: Helge Deller <deller@gmx.de>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
intel-gfx@lists.freedesktop.org, kunit-dev@googlegroups.com,
linux-bluetooth@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-serial@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [linux-next:master] BUILD REGRESSION e1f6a8eaf1c271a0158114a03e3605f4fba059ad
Date: Wed, 5 Jul 2023 18:22:42 +0200 [thread overview]
Message-ID: <17b4e65f-a140-8e4d-505b-f2f6f7d1a8c5@gmx.de> (raw)
In-Reply-To: <202307060015.uSSLonkv-lkp@intel.com>
On 7/5/23 18:07, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: e1f6a8eaf1c271a0158114a03e3605f4fba059ad Add linux-next specific files for 20230705
>
> Error/Warning reports:
>
> https://lore.kernel.org/oe-kbuild-all/202306122223.HHER4zOo-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202306260401.qZlYQpV2-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202306291857.nyJjYwqk-lkp@intel.com
> https://lore.kernel.org/oe-kbuild-all/202306301756.x8dgyYnL-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> arch/parisc/kernel/pdt.c:67:6: warning: no previous prototype for 'arch_report_meminfo' [-Wmissing-prototypes]
The arch/parisc/* warnings have been fixed a few days ago in for-next, and
the patches will most likely be merged upstream today...
Helge
prev parent reply other threads:[~2023-07-05 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 16:07 kernel test robot
2023-07-05 16:22 ` Helge Deller [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=17b4e65f-a140-8e4d-505b-f2f6f7d1a8c5@gmx.de \
--to=deller@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.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