From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>
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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/341] 6.6.48-rc1 review
Date: Wed, 28 Aug 2024 22:35:27 +0800 [thread overview]
Message-ID: <20240828223526.7E07.409509F4@e16-tech.com> (raw)
In-Reply-To: <20240827143843.399359062@linuxfoundation.org>
Hi,
> This is the start of the stable review cycle for the 6.6.48 release.
> There are 341 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 Thu, 29 Aug 2024 14:37:36 +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.6.48-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.6.y
> and the diffstat can be found below.
We need a patch
upsteam: 0a04ff09bcc39e0044190ffe9f00f998f13647c
From: Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: tools: move alignment-related macros to new <linux/align.h>
to fix the new build error.
tools/include/linux/bitmap.h: In function 'bitmap_zero':
tools/include/linux/bitmap.h:28:29: warning: implicit declaration of
function 'ALIGN' [-Wimplicit-function-declaration]
#define bitmap_size(nbits) (ALIGN(nbits, BITS_PER_LONG) / BITS_PER_BYTE)
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/08/28
next prev parent reply other threads:[~2024-08-28 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 14:33 [PATCH 6.6 000/341] 6.6.48-rc1 review Greg Kroah-Hartman
2024-08-27 15:39 ` Naresh Kamboju
2024-08-27 17:47 ` Florian Fainelli
2024-08-29 14:23 ` Greg Kroah-Hartman
2024-08-28 1:00 ` SeongJae Park
2024-08-28 3:57 ` Peter Schneider
2024-08-28 11:41 ` Mark Brown
2024-08-28 11:53 ` Takeshi Ogasawara
2024-08-28 14:30 ` Naresh Kamboju
2024-08-28 17:29 ` Naresh Kamboju
2024-08-29 14:16 ` Greg Kroah-Hartman
2024-08-28 14:35 ` Wang Yugui [this message]
2024-08-28 14:45 ` Alexander Lobakin
2024-08-29 14:20 ` Greg Kroah-Hartman
2024-08-28 16:02 ` Miguel Ojeda
2024-08-28 18:16 ` Ron Economos
2024-08-29 10:24 ` Jon Hunter
2024-08-29 11:14 ` Shreeya Patel
2024-08-31 21:26 ` Guenter Roeck
2024-09-01 9:43 ` Greg Kroah-Hartman
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=20240828223526.7E07.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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