public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, 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, hargar@microsoft.com, broonie@kernel.org,
	Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 6.1 000/772] 6.1.120-rc1 review
Date: Fri, 13 Dec 2024 13:24:38 +0100	[thread overview]
Message-ID: <2024121311-stays-moonlit-ee5e@gregkh> (raw)
In-Reply-To: <CA+G9fYu+u4a+63vCCeLo1LdWhvK75B9j-znx7kp2ZVtzK_H4AQ@mail.gmail.com>

On Fri, Dec 13, 2024 at 02:29:56AM +0530, Naresh Kamboju wrote:
> On Thu, 12 Dec 2024 at 21:23, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.1.120 release.
> > There are 772 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 Sat, 14 Dec 2024 14:41:35 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.120-rc1.gz
> > or in the git tree and branch at:
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> The powerpc builds failed on Linux stable-rc linux-6.1.y due to following build
> warnings / errors.
> 
> powerpc:
>   * build/gcc-13-tqm8xx_defconfig
> 
> First seen on Linux stable-rc v6.1.119-773-g9f320894b9c2.
>   Good: v6.1.119
>   Bad: v6.1.119-773-g9f320894b9c2
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Build log:
> -----
> /builds/linux/arch/powerpc/include/asm/page_32.h:16: error:
> "ARCH_DMA_MINALIGN" redefined [-Werror]
>    16 | #define ARCH_DMA_MINALIGN       L1_CACHE_BYTES
>       |
> In file included from /builds/linux/include/linux/slab.h:15:
> /builds/linux/include/linux/cache.h:104: note: this is the location of
> the previous definition
>   104 | #define ARCH_DMA_MINALIGN __alignof__(unsigned long long)
>       |
> cc1: all warnings being treated as errors
> 
> The bisection pointed to,
>    mm/slab: decouple ARCH_KMALLOC_MINALIGN from ARCH_DMA_MINALIGN
>    commit 4ab5f8ec7d71aea5fe13a48248242130f84ac6bb upstream.

Ick, this was to fix a different build error.  Looks like I need to
queue up 78615c4ddb73 ("powerpc: move the ARCH_DMA_MINALIGN definition
to asm/cache.h") as well, I'll go do that now...

thanks,

greg k-h

  reply	other threads:[~2024-12-13 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 14:49 [PATCH 6.1 000/772] 6.1.120-rc1 review Greg Kroah-Hartman
2024-12-12 14:53 ` [PATCH 6.1 281/772] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-12 15:01 ` [PATCH 6.1 761/772] drm/ttm: Make sure the mapped tt pages are decrypted when needed Greg Kroah-Hartman
2024-12-12 15:01 ` [PATCH 6.1 762/772] drm/ttm: Print the memory decryption status just once Greg Kroah-Hartman
2024-12-12 16:25 ` [PATCH 6.1 000/772] 6.1.120-rc1 review Pavel Machek
2024-12-12 20:59 ` Naresh Kamboju
2024-12-13 12:24   ` Greg Kroah-Hartman [this message]
2024-12-12 21:38 ` Florian Fainelli
2024-12-13 12:33   ` Greg Kroah-Hartman
2024-12-13  2:30 ` Peter Schneider
2024-12-13  2:44 ` Ron Economos
2024-12-13 14:17   ` Greg Kroah-Hartman
2024-12-13 10:03 ` Jon Hunter
2024-12-13 13:13 ` Mark Brown
2024-12-13 17:06 ` Shuah Khan
2024-12-13 18:35 ` SeongJae Park

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=2024121311-stays-moonlit-ee5e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@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