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
Subject: Re: [PATCH 4.19 0/1] 4.19.294-rc1 review
Date: Thu, 31 Aug 2023 19:22:25 +0200 [thread overview]
Message-ID: <2023083112-hazelnut-subject-0736@gregkh> (raw)
In-Reply-To: <fbefb0cd-e056-4504-b0b2-ebd778d4996f@roeck-us.net>
On Thu, Aug 31, 2023 at 09:10:02AM -0700, Guenter Roeck wrote:
> On Thu, Aug 31, 2023 at 01:09:48PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.294 release.
> > There are 1 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, 02 Sep 2023 11:08:22 +0000.
> > Anything received after that time might be too late.
> >
>
> arch/arm/mach-ep93xx/timer-ep93xx.c:12:10: fatal error: platform.h: No such file or directory
> 12 | #include "platform.h"
>
> "ARM: ep93xx: fix missing-prototype warnings" needs to be reverted in
> v4.19.y as well.
Oops, missed that, let me go add it and push out a -rc2.
thanks for the quick test.
greg k-h
next prev parent reply other threads:[~2023-08-31 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 11:09 [PATCH 4.19 0/1] 4.19.294-rc1 review Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 4.19 1/1] Revert "MIPS: Alchemy: fix dbdma2" Greg Kroah-Hartman
2023-08-31 16:10 ` [PATCH 4.19 0/1] 4.19.294-rc1 review Guenter Roeck
2023-08-31 17:22 ` Greg Kroah-Hartman [this message]
2023-09-01 16:01 ` Shuah Khan
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=2023083112-hazelnut-subject-0736@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.