From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.15 00/37] 5.15.96-rc2 review
Date: Thu, 23 Feb 2023 08:37:36 -0800 [thread overview]
Message-ID: <b53ad4fc-978a-b883-0d09-2a9306615a66@gmail.com> (raw)
In-Reply-To: <Y/eVSi4ZTcOmPBTv@kroah.com>
On 2/23/23 08:33, Greg Kroah-Hartman wrote:
> On Thu, Feb 23, 2023 at 07:36:39AM -0800, Guenter Roeck wrote:
>> On 2/23/23 06:16, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 5.15.96 release.
>>> There are 37 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, 25 Feb 2023 14:15:30 +0000.
>>> Anything received after that time might be too late.
>>>
>>
>>
>> $ git describe
>> v5.15.95-38-gd6f4f9746d40
>> groeck@server:~/src/linux-stable$ !ls
>> ls -l scripts/pahole-version.sh
>> -rw-rw-r-- 1 groeck groeck 269 Feb 23 07:33 scripts/pahole-version.sh
>>
>> This results in:
>>
>> make[1]: Entering directory '/tmp/buildbot-builddir'
>> scripts/pahole-flags.sh: 10: /opt/buildbot/slave/stable-queue-5.15/build/scripts/pahole-version.sh: Permission denied
>> scripts/pahole-flags.sh: 12: [: Illegal number:
>> scripts/pahole-flags.sh: 16: [: Illegal number:
>> scripts/pahole-flags.sh: 20: [: Illegal number:
>>
>> and all builds fail for me.
>
> This is a fun thing, the patch shows it being set to 0755, so `git am`
> should be doing the right thing here. Let me dig to see if I can change
> something in my scripts to resolve this...
We have had this happen, last time you explained that quilt did not
handle the file mode:
https://lore.kernel.org/all/d1a46ccc-cb07-fa51-f722-c48d6c84bf9d@gmail.com/
Anything we can do about this?
--
Florian
next prev parent reply other threads:[~2023-02-23 16:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 14:16 [PATCH 5.15 00/37] 5.15.96-rc2 review Greg Kroah-Hartman
2023-02-23 15:36 ` Guenter Roeck
2023-02-23 16:33 ` Greg Kroah-Hartman
2023-02-23 16:37 ` Florian Fainelli [this message]
2023-02-23 17:30 ` Guenter Roeck
2023-02-23 18:03 ` Linus Torvalds
2023-02-23 19:47 ` Nathan Chancellor
2023-02-23 21:18 ` Linus Torvalds
2023-02-23 21:23 ` Greg Kroah-Hartman
2023-02-23 21:39 ` Linus Torvalds
2023-02-24 10:25 ` Greg Kroah-Hartman
2023-02-24 16:55 ` Greg Kroah-Hartman
2023-02-23 15:40 ` Naresh Kamboju
2023-02-23 15:45 ` Shuah Khan
2023-02-23 16:18 ` Shuah Khan
2023-02-23 21:54 ` Florian Fainelli
2023-02-23 23:34 ` Shuah Khan
2023-02-24 4:03 ` Slade Watkins
2023-02-24 9:50 ` Bagas Sanjaya
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=b53ad4fc-978a-b883-0d09-2a9306615a66@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--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