From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Goncharov <dgoncharov@users.sf.net>
Cc: Eric Biggers <ebiggers@kernel.org>,
bug-make@gnu.org, stable@vger.kernel.org
Subject: Re: No progress output when make 4.4.1 builds Linux 4.19 and earlier
Date: Wed, 8 Mar 2023 14:27:19 +0100 [thread overview]
Message-ID: <ZAiNN0wkLpdjY1Y2@kroah.com> (raw)
In-Reply-To: <CAG+Z0CuAQsq-1DNaX0_qHnqSBt1YrUBbBaypxgwT0USFyOkk4g@mail.gmail.com>
On Wed, Mar 08, 2023 at 08:12:57AM -0500, Dmitry Goncharov wrote:
> On Wed, Mar 8, 2023 at 1:37 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Mar 07, 2023 at 10:13:45PM -0800, Eric Biggers wrote:
> ...
> > > Is this an intentional breakage from the 'make' side?
> No it is not an intentional breakage.
> This is a fix for https://savannah.gnu.org/bugs/?63347.
>
> > The fact that kernels 5.4 and newer imply to me that there is
> > a kernel build fix that should resolve this if someone can take the time
> > to bisect it...
>
> Kernel makefile was updated to work with old and new make in
> 4bf73588165ba7d32131a043775557a54b6e1db5.
> If you wanted to backport, try this commit.
Nice, that worked for me! I'll go queue that up for the stable kernels
now, thank you for the quick response.
greg k-h
next prev parent reply other threads:[~2023-03-08 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 6:13 No progress output when make 4.4.1 builds Linux 4.19 and earlier Eric Biggers
2023-03-08 6:17 ` Greg KH
2023-03-08 6:34 ` Eric Biggers
2023-03-08 13:12 ` Dmitry Goncharov
2023-03-08 13:27 ` Greg KH [this message]
2023-03-08 13:57 ` Paul Smith
2023-03-08 14:31 ` Greg KH
2023-03-08 14:39 ` Dmitry Goncharov
2023-03-08 15:53 ` David Laight
2023-03-08 17:50 ` Paul Smith
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=ZAiNN0wkLpdjY1Y2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bug-make@gnu.org \
--cc=dgoncharov@users.sf.net \
--cc=ebiggers@kernel.org \
--cc=stable@vger.kernel.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