From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Paul Mackerras <paulus@samba.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc: Fix build warning
Date: Wed, 25 Jun 2014 09:53:43 +0200 [thread overview]
Message-ID: <CAMuHMdUW0aZ__ykR6CC793EM1RSEbYqbWaXtEqKjG4janF-rRQ@mail.gmail.com> (raw)
In-Reply-To: <53A91449.6010701@roeck-us.net>
On Tue, Jun 24, 2014 at 8:01 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> Sigh. Much easier to break something than to fix it. That would mean to get
> approval
> from at least three maintainers, and all that to get rid of a warning. I
> don't
> really have time for that. Let's just forget about it and live with the
> warning.
So you send it to akpm. Or perhaps even trivial.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2014-06-25 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 16:38 [PATCH] powerpc: Fix build warning Guenter Roeck
2014-06-17 1:25 ` David Rientjes
2014-06-17 2:02 ` Guenter Roeck
2014-06-24 4:35 ` Benjamin Herrenschmidt
2014-06-24 5:05 ` Guenter Roeck
2014-06-24 5:34 ` Benjamin Herrenschmidt
2014-06-24 6:01 ` Guenter Roeck
2014-06-24 6:38 ` Benjamin Herrenschmidt
2014-06-25 7:53 ` Geert Uytterhoeven [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=CAMuHMdUW0aZ__ykR6CC793EM1RSEbYqbWaXtEqKjG4janF-rRQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=vincent.guittot@linaro.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).