LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.4-3 tag
Date: Sun, 28 May 2023 10:14:01 +1000	[thread overview]
Message-ID: <87a5xptira.fsf@mail.lhotse> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Linus,

Please pull another powerpc fix for 6.4:

The following changes since commit 1f7aacc5eb9ed2cc17be7a90da5cd559effb9d59:

  powerpc/iommu: Incorrect DDW Table is referenced for SR-IOV device (2023-05-17 00:54:55 +1000)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.4-3

for you to fetch changes up to 358e526a1648cdd773ba169da5867874ae2408e3:

  powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges (2023-05-21 11:40:34 +1000)

- ------------------------------------------------------------------
powerpc fixes for 6.4 #3

 - Reinstate ARCH_FORCE_MAX_ORDER ranges to fix various breakage.

- ------------------------------------------------------------------
Michael Ellerman (1):
      powerpc/mm: Reinstate ARCH_FORCE_MAX_ORDER ranges


 arch/powerpc/Kconfig | 6 ++++++
 1 file changed, 6 insertions(+)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmRynH4ACgkQUevqPMjh
pYBJiQ/+JDl1NKXbyU5d7uJZbI2k5u3Pq14o6+E9IyOzN1Ez5IEsUcruKmYpPBV4
Pn5iG/wBlcYKxK5zq0SF0zs7Q+ouXGZUR0ykY0vabcD/0s+AKIPlZAzKfaHwAB6j
phpLCldv4luZxXK5ukf1jLddwl4Dj5cKKZAuL9KQf3qQLfhmZJLh/HCnf22ydDW+
qAoj1pVFWEjQN+DkCR0dvryD2DsXXixCFNCTKy1OcQbLJCiDnmbzzxhTGDl7O5UE
VjqCJQE8lomc0EStD+9w6O/FXpeIlVsIM72IPxRWMsoR4vSyQ/TRPqVA7OxybLy3
CJcBWkk+nhNze/5+8uNQcvy/q2FJDE7DvibZc5WtH+rXid8+qq1EaVhfaeQ/z2Va
WjzbXT8OVJVi8H2o2bY0Yb2Mx+jZIIkpSaLdRez3Q0w5dK/AryzYT3c/vx7LHKkI
PK74+R/2wZiKZCipY4J3XBLRFV5tR5VA0qW2ls5yvu+D6kiSfHTKj6S0KJ9jZTIc
ieqbEhzdvnD+GAN8QZDmtl6b7SUyC/QXFgBVvj87kl++zAyRxFE1Oe6LpbelXWdg
eRGGyhdnWt0TUC8jLmlhaGvDpXwaViqIVG0abhH/Ma6EUAmxs2z8mCE+3CIAGWoR
WwGQV63NXw2zMHac5VkBGVCGatCYRIsC7ivYa60Pe6LcidbT+hs=
=LSac
-----END PGP SIGNATURE-----

             reply	other threads:[~2023-05-28  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28  0:14 Michael Ellerman [this message]
2023-05-28  1:12 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.4-3 tag pr-tracker-bot

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=87a5xptira.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox