All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Richard Narron <richard@aaazen.com>
Cc: Linux stable <stable@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 5.15 000/214] 5.15.167-rc1 review
Date: Fri, 13 Sep 2024 14:22:42 +0200	[thread overview]
Message-ID: <2024091328-excusable-lubricant-c607@gregkh> (raw)
In-Reply-To: <a6392c39-e12f-e913-8f4f-c135b283ce@aaazen.com>

On Thu, Sep 12, 2024 at 02:54:18PM -0700, Richard Narron wrote:
> On Wed, 11 Sep 2024, Greg Kroah-Hartman wrote:
> 
> > On Tue, Sep 10, 2024 at 03:54:18PM -0700, Richard Narron wrote:
> > > Slackware 15.0 64-bit compiles and runs fine.
> > > Slackware 15.0 32-bit fails to build and gives the "out of memory" error:
> > >
> > > cc1: out of memory allocating 180705472 bytes after a total of 284454912
> > > bytes
> > > ...
> > > make[4]: *** [scripts/Makefile.build:289:
> > > drivers/staging/media/atomisp/pci/isp/kernels/ynr/ynr_1.0/ia_css_ynr.ho
> > > st.o] Error 1
> > >
> > > Patching it with help from Lorenzo Stoakes allows the build to
> > > run:
> > > https://lore.kernel.org/lkml/5882b96e-1287-4390-8174-3316d39038ef@lucifer.local/
> > >
> > > And then 32-bit runs fine too.
> >
> > Great, please help to get that commit merged into Linus's tree and then
> > I can backport it here.
> 
> Thanks to Linus and Lorenzo and Hans there is new smaller fix patch in
> Linus's tree:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging/media/atomisp/pci/sh_css_frac.h?id=7c6a3a65ace70f12b27b1a27c9a69cb791dc6e91
> 
> This works with the new 5.15.167 kernel with both 32-bit (x86) and 64-bit
> (x86_64) CPUs
> 
> Can this be backported?

Yes it will, give us a chance to catch up :)

thanks,

greg k-h

  reply	other threads:[~2024-09-13 12:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 22:54 [PATCH 5.15 000/214] 5.15.167-rc1 review Richard Narron
2024-09-11 13:00 ` Greg Kroah-Hartman
2024-09-11 13:17   ` Lorenzo Stoakes
2024-09-12 21:54   ` Richard Narron
2024-09-13 12:22     ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10  9:30 Greg Kroah-Hartman
2024-09-10 13:08 ` Jon Hunter
2024-09-11 12:56   ` Greg Kroah-Hartman
2024-09-10 16:20 ` Mark Brown
2024-09-10 18:37 ` Florian Fainelli
2024-09-10 18:43 ` Harshit Mogalapalli
2024-09-10 21:12 ` Shuah Khan
2024-09-11 12:48   ` Greg Kroah-Hartman
2024-09-11 11:14 ` Naresh Kamboju

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=2024091328-excusable-lubricant-c607@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=richard@aaazen.com \
    --cc=stable@vger.kernel.org \
    --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.