linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: diana.craciun@nxp.com, malat@debian.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	chunkeey@gmail.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.21-2 tag
Date: Sat, 05 Jan 2019 22:53:56 +1100	[thread overview]
Message-ID: <877efjxquj.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <87ftu8y3vw.fsf@concordia.ellerman.id.au>

Hi Linus,

Michael Ellerman <mpe@ellerman.id.au> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Linus,
>
> Please pull some powerpc fixes for 4.21:
...
>
> for you to fetch changes up to 074400a7be61250d9f0ccec07d5c35ffec4d8d22:
>
>   powerpc: Drop use of 'type' from access_ok() (2019-01-04 23:07:59 +1100)

I see you've fixed this in your tree already.

If you want to skip this pull and avoid having two fixes for the
access_ok() stuff in the history that would be fine by me.

The rest of this pull request is all very minor and could wait until
next week, I could pull out the redundant access_ok() fix and generate a
new tag later in the week.

cheers


> - ------------------------------------------------------------------
> powerpc fixes for 4.21 #2
>
> A fix for the recent access_ok() change, which broke the build. We recently
> added a use of type in order to squash a warning elsewhere about type being
> unused.
>
> A handful of other minor build fixes, and one defconfig update.
>
> Thanks to:
>   Christian Lamparter, Christophe Leroy, Diana Craciun, Mathieu Malaterre.
>
> - ------------------------------------------------------------------
> Christian Lamparter (1):
>       powerpc/4xx/ocm: Fix compilation error due to PAGE_KERNEL usage
>
> Diana Craciun (1):
>       powerpc/fsl: Fixed warning: orphan section `__btb_flush_fixup'
>
> Mathieu Malaterre (1):
>       powerpc: Drop use of 'type' from access_ok()
>
> Michael Ellerman (4):
>       powerpc/4xx/ocm: Fix phys_addr_t printf warnings
>       powerpc/configs: Add PPC4xx_OCM to ppc40x_defconfig
>       KVM: PPC: Book3S HV: radix: Fix uninitialized var build error
>       Merge branch 'master' into fixes
>
>
>  arch/powerpc/configs/ppc40x_defconfig  |  1 +
>  arch/powerpc/include/asm/uaccess.h     |  2 +-
>  arch/powerpc/kernel/head_booke.h       | 18 ++++++++++++------
>  arch/powerpc/kvm/book3s_64_mmu_radix.c |  2 +-
>  arch/powerpc/platforms/4xx/ocm.c       | 10 +++++-----
>  5 files changed, 20 insertions(+), 13 deletions(-)
> -----BEGIN PGP SIGNATURE-----
>
> iQIcBAEBAgAGBQJcL1eOAAoJEFHr6jzI4aWA86wP/3V5zlUNtsyXpcCx60PNIMya
> 6z6oWVKoM92nMIyfWuoxKBEbylSyixFSxOsKoiVJDyigW5WWNjsPQ1KOUD2OVn0V
> OQhj2aDXwUtxdlQ5dK0H9lodsUKUEw1/saqcgi2OS8iDDa8kJIEemDe29Omf5DyE
> U2RKl++nhAfK8BLfMRCAIqL+TVZq9Zy+zNwbVtsmj7lAlw+Csb4KV3YvlJ7b6pjD
> Ntm6O3X8sy7GtJdMpeBDOMTbWuvIQpefVH135jS1IjJZbrafZK6a4gQ9cs5mx68d
> +/nyzkcjy83eRGkv3QY5Y+vEa0wkFdBb6Nf0MH63xCPVYVjom6pRUGL+RPldi2GO
> bmieDXavlicX9y+BCQSKASTzNo2uR2heF31aCnr6bsOSeT8ZNGbIwgHuGGqrzN+8
> qLQb00hA0uKlbNgPpNoyYO5K3khntR348HfH0Uwlm3Nttvn1TEh87c9L19FcdlMw
> SlA6kpJ6328FkEv5FUPu7v7764dPgOQNImPKnsYdhbUxhHnDMx33LzsUEQQcYWpM
> 3nsKQMW1yqMH2BG8u9LQtZErFanX+RNm81OsP38F8nvGe1RJkoq7R7MSooZ9tzs2
> Ymf8W+KNofKmXVAPh7AyKQzpy0a/sEqAXmtTPBf7bsdwU5PQB0+LMf0yzyZpEp2U
> 3eFcseqDoO32ScDZQUYt
> =Y+yv
> -----END PGP SIGNATURE-----

  reply	other threads:[~2019-01-05 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 13:00 [GIT PULL] Please pull powerpc/linux.git powerpc-4.21-2 tag Michael Ellerman
2019-01-05 11:53 ` Michael Ellerman [this message]
2019-01-05 19:50   ` Linus Torvalds
2019-01-05 20:20 ` 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=877efjxquj.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=chunkeey@gmail.com \
    --cc=diana.craciun@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=malat@debian.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;
as well as URLs for NNTP newsgroup(s).