From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linuxppc-dev@ozlabs.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/prom: Avoid reference to potentially freed memory
Date: Mon, 19 Oct 2015 20:32:34 +1100 [thread overview]
Message-ID: <1445247154.30407.3.camel@ellerman.id.au> (raw)
In-Reply-To: <mvrlh7$mjr$1@ger.gmane.org>
On Fri, 2015-10-16 at 22:09 +0200, Christophe JAILLET wrote:
> Le 16/10/2015 12:02, Michael Ellerman a écrit :
> > As the kbuild robot detected you have left an extra "}" here.
> >
> > I don't mind too much if you send patches that aren't compile tested, but you
> > might save yourself some time by compiling them.
>
> Sorry about it, and thanks for your patience.
> IMHO, this should never happen and patches should be at least
> compile-tested.
Preferably yes. But for these sort of cleanup patches, where you're touching
lots of different arches, I realise it can be tedious to find all the various
cross compilers. So I'm willing to cut you a bit of slack :)
> I will be more careful and compile-test any new patch I submit.
Thanks.
cheers
next prev parent reply other threads:[~2015-10-19 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 6:14 [PATCH] powerpc/prom: Avoid reference to potentially freed memory Christophe JAILLET
2015-10-16 7:50 ` kbuild test robot
2015-10-16 10:02 ` Michael Ellerman
2015-10-16 20:09 ` Christophe JAILLET
2015-10-19 9:32 ` Michael Ellerman [this message]
2015-10-16 21:38 ` [PATCH v2] " Christophe JAILLET
2015-10-19 9:27 ` Michael Ellerman
2015-10-21 4:36 ` [PATCH v3] " Christophe JAILLET
2015-10-21 11:41 ` [v2] " Michael Ellerman
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=1445247154.30407.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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