From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Leif Lindholm
<leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Roy Franz <roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mark Salter <msalter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] efi: fix pointer type errors in fdt_uefi_find_params()
Date: Wed, 18 Jun 2014 10:28:45 +0100 [thread overview]
Message-ID: <20140618092845.GE24049@console-pimps.org> (raw)
In-Reply-To: <CAKv+Gu-PKHx8Z64W0v2jA8p2w6whewhgVdYaQyBfJRZrPSFLyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 18 Jun, at 11:06:09AM, Ard Biesheuvel wrote:
>
> You say potato, I say po-tah-to?
> But seriously, whichever you prefer ...
$ git grep "const void" | wc -l
4441
$ git grep "void const" | wc -l
50
I say potato, you say "tasty carbohydrate ball"
But yeah, it's not a big deal and I can fix this up when applying.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-06-18 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 14:54 [PATCH] efi: fix pointer type errors in fdt_uefi_find_params() Ard Biesheuvel
[not found] ` <1402671299-22493-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-06-18 9:02 ` Matt Fleming
[not found] ` <20140618090245.GC24049-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-06-18 9:06 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-PKHx8Z64W0v2jA8p2w6whewhgVdYaQyBfJRZrPSFLyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-18 9:28 ` Matt Fleming [this message]
[not found] ` <20140618092845.GE24049-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-06-18 10:53 ` Ard Biesheuvel
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=20140618092845.GE24049@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=msalter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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