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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 00/73] 6.1.119-rc1 review
Date: Mon, 2 Dec 2024 14:02:17 +0100 [thread overview]
Message-ID: <2024120206-dreamy-wilder-ec77@gregkh> (raw)
In-Reply-To: <eda70745-0ea2-43bd-bee3-8905e3a1d3cc@roeck-us.net>
On Sat, Nov 23, 2024 at 07:47:09AM -0800, Guenter Roeck wrote:
> On 11/20/24 04:57, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.119 release.
> > There are 73 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 Fri, 22 Nov 2024 12:57:58 +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.119-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
> >
> > -------------
> > Pseudo-Shortlog of commits:
> >
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Linux 6.1.119-rc1
> >
> > Michal Luczaj <mhal@rbox.co>
> > net: Make copy_safe_from_sockptr() match documentation
> >
> > Eli Billauer <eli.billauer@gmail.com>
> > char: xillybus: Fix trivial bug with mutex
> >
> > Mikulas Patocka <mpatocka@redhat.com>
> > parisc: fix a possible DMA corruption
> >
>
> This results in:
>
> include/linux/slab.h:229: warning: "ARCH_KMALLOC_MINALIGN" redefined
> 229 | #define ARCH_KMALLOC_MINALIGN ARCH_DMA_MINALIGN
> |
> In file included from include/linux/cache.h:6,
> from include/linux/mmzone.h:12,
> from include/linux/gfp.h:7,
> from include/linux/mm.h:7:
> 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 */
>
> because commit 4ab5f8ec7d71a ("mm/slab: decouple ARCH_KMALLOC_MINALIGN
> from ARCH_DMA_MINALIGN") was not applied as well.
>
> Then there is
>
> include/linux/dma-mapping.h:546:47: error: macro "cache_line_size" passed 1 arguments, but takes just 0
> 546 | static inline int dma_get_cache_alignment(void)
> | ^
> arch/parisc/include/asm/cache.h:31: note: macro "cache_line_size" defined here
> 31 | #define cache_line_size() dcache_stride
> |
> include/linux/dma-mapping.h:547:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
>
> because commit 8c57da28dc3df ("dma: allow dma_get_cache_alignment()
> to be overridden by the arch code") is missing as well.
>
> Those two patches fix the compile errors. I have not tested if the resulting
> images boot.
Thanks, I'll go queue them up now.
greg k-h
next prev parent reply other threads:[~2024-12-02 13:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 12:57 Greg Kroah-Hartman
2024-11-20 16:45 ` Mark Brown
2024-11-20 17:01 ` SeongJae Park
2024-11-20 18:31 ` Florian Fainelli
2024-11-20 23:22 ` Shuah Khan
2024-11-21 4:26 ` Ron Economos
2024-11-21 8:32 ` Naresh Kamboju
2024-11-21 9:02 ` Pavel Machek
2024-11-21 16:50 ` Hardik Garg
2024-11-21 19:39 ` Jon Hunter
2024-11-22 6:59 ` Muhammad Usama Anjum
2024-11-22 13:55 ` Yann Sionneau
2024-11-23 7:25 ` Pavel Machek
2024-11-23 16:11 ` Chuck Lever III
2024-11-23 17:47 ` Pavel Machek
2024-11-23 15:47 ` Guenter Roeck
2024-12-02 13:02 ` Greg Kroah-Hartman [this message]
2024-11-28 17:54 ` Pavel Machek
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=2024120206-dreamy-wilder-ec77@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.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=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
all inboxes | Powered by JetHome®