From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/150] 6.1.105-rc1 review
Date: Tue, 13 Aug 2024 08:19:01 +0200 [thread overview]
Message-ID: <2024081352-harsh-prior-004e@gregkh> (raw)
In-Reply-To: <f514502a-0e89-4fcb-95c4-986a3cba2342@roeck-us.net>
On Mon, Aug 12, 2024 at 02:42:58PM -0700, Guenter Roeck wrote:
> On 8/12/24 09:01, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.105 release.
> > There are 150 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 14 Aug 2024 16:00:26 +0000.
> > Anything received after that time might be too late.
> >
>
> Building parisc64:C3700:smp:net=pcnet:initrd ... failed
> ------------
> Error log:
> In file included from /home/groeck/src/linux-stable/include/linux/fs.h:45,
> from /home/groeck/src/linux-stable/include/linux/huge_mm.h:8,
> from /home/groeck/src/linux-stable/include/linux/mm.h:745,
> from /home/groeck/src/linux-stable/include/linux/pid_namespace.h:7,
> from /home/groeck/src/linux-stable/include/linux/ptrace.h:10,
> from /home/groeck/src/linux-stable/arch/parisc/kernel/asm-offsets.c:20:
> /home/groeck/src/linux-stable/include/linux/slab.h:228: warning: "ARCH_KMALLOC_MINALIGN" redefined
> 228 | #define ARCH_KMALLOC_MINALIGN ARCH_DMA_MINALIGN
>
> In file included from /home/groeck/src/linux-stable/arch/parisc/include/asm/atomic.h:23,
> from /home/groeck/src/linux-stable/include/linux/atomic.h:7,
> from /home/groeck/src/linux-stable/include/linux/rcupdate.h:25,
> from /home/groeck/src/linux-stable/include/linux/rculist.h:11,
> from /home/groeck/src/linux-stable/include/linux/pid.h:5,
> from /home/groeck/src/linux-stable/include/linux/sched.h:14,
> from /home/groeck/src/linux-stable/arch/parisc/kernel/asm-offsets.c:18:
> /home/groeck/src/linux-stable/arch/parisc/include/asm/cache.h:28: note: this is the location of the previous definition
> 28 | #define ARCH_KMALLOC_MINALIGN 16 /* ldcw requires 16-byte alignment */
>
Thanks, I'll go drop the offending commit now.
greg k-h
prev parent reply other threads:[~2024-08-13 6:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 16:01 [PATCH 6.1 000/150] 6.1.105-rc1 review Greg Kroah-Hartman
2024-08-12 20:53 ` Pavel Machek
2024-08-12 21:42 ` Guenter Roeck
2024-08-13 5:45 ` Naresh Kamboju
2024-08-13 6:19 ` Greg Kroah-Hartman [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=2024081352-harsh-prior-004e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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