From: Russell Currey <ruscur@russell.cc>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Snowpatch
Date: Wed, 12 Dec 2018 10:18:19 +1100 [thread overview]
Message-ID: <1544570299.3422798.1606440520.1D651F72@webmail.messagingengine.com> (raw)
In-Reply-To: <d76e02ff-97dd-fe59-eec9-2756f77bd2a4@c-s.fr>
On Wed, Dec 12, 2018, at 8:41 AM, Christophe Leroy wrote:
> snowpatch is pretty surprising on
> https://patchwork.ozlabs.org/patch/1003954/
>
> How can such a trivial patch for 8xx alter compilation of all other
> targets that much (ie add or remove sparse warnings) ?
It was a bug I fixed as soon as I noticed and shouldn't happen any more.
>
> Christophe
prev parent reply other threads:[~2018-12-11 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 21:41 Snowpatch Christophe Leroy
2018-12-11 23:18 ` Russell Currey [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=1544570299.3422798.1606440520.1D651F72@webmail.messagingengine.com \
--to=ruscur@russell.cc \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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