public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/341] 6.6.48-rc1 review
Date: Sun, 1 Sep 2024 11:43:24 +0200	[thread overview]
Message-ID: <2024090118-wisdom-footman-ace8@gregkh> (raw)
In-Reply-To: <4b332d8c-4ed0-4ecf-a4db-75c1aa932b48@roeck-us.net>

On Sat, Aug 31, 2024 at 02:26:28PM -0700, Guenter Roeck wrote:
> On 8/27/24 07:33, Greg Kroah-Hartman wrote:
> > 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.
> > 
> [ ... ]
> 
> > Suren Baghdasaryan <surenb@google.com>
> >      change alloc_pages name in dma_map_ops to avoid name conflicts
> > 
> 
> This patch triggers:
> 
> Building s390:defconfig ... failed
> --------------
> Error log:
> arch/s390/pci/pci_dma.c:724:10: error: 'const struct dma_map_ops' has no member named 'alloc_pages'; did you mean 'alloc_pages_op'?
>   724 |         .alloc_pages    = dma_common_alloc_pages,
> 
> for pretty much all s390 builds.
> 
> Source code analysis suggests that the problem also affects
> arch/ia64/hp/common/sba_iommu.c.a

Thanks, already handled.

greg k-h

      reply	other threads:[~2024-09-01  9:43 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
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 [this message]

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=2024090118-wisdom-footman-ace8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox