From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jones <drjones@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>"Richard W.M. Jones"
<rjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 5/7] hw/loader: split out load_image_gzipped_buffer()
Date: Fri, 12 Dec 2014 14:43:38 +0100 [thread overview]
Message-ID: <548AF10A.3030407@redhat.com> (raw)
In-Reply-To: <CAFEAcA9CtgY6ARu5X0QqrnJmPg98ohs=JsPHM_rEHfai0t-v6Q@mail.gmail.com>
On 12/12/14 14:11, Peter Maydell wrote:
> On 9 December 2014 at 01:13, Laszlo Ersek <lersek@redhat.com> wrote:
>> In the next patch we'd like to reuse the image decompression facility
>> without installing the output as a ROM at a specific guest-phys address.
>>
>> In addition, expose LOAD_IMAGE_MAX_GUNZIP_BYTES, because that's a
>> straightforward "max_sz" argument for the new load_image_gzipped_buffer().
>>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>
>> +int load_image_gzipped(const char *filename, hwaddr addr, uint64_t max_sz)
>> +{
>> + int bytes;
>> + uint8_t *data;
>> +
>> + bytes = load_image_gzipped_buffer (filename, max_sz, &data);
>
> Doesn't checkpatch complain about the space before the "(" here?
(Checkpatch? What's that? :))
It sure does.
WARNING: space prohibited between function name and open parenthesis '('
Obviously, the edk2 coding style *requires* that damn space. I got so
used to it that it slipped in here.
Thanks!
Laszlo
>
> Otherwise:
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> -- PMM
>
next prev parent reply other threads:[~2014-12-12 13:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 1:12 [Qemu-devel] [PATCH v3 0/7] fw_cfg, bootorder, and UEFI+'-kernel' on arm/virt Laszlo Ersek
2014-12-09 1:12 ` [Qemu-devel] [PATCH v3 1/7] fw_cfg: max access size and region size are the same for MMIO data reg Laszlo Ersek
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 2/7] fw_cfg: introduce the "data_memwidth" property Laszlo Ersek
2014-12-12 12:49 ` Peter Maydell
2014-12-12 13:39 ` Laszlo Ersek
2014-12-12 13:41 ` Peter Maydell
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 3/7] fw_cfg: expose the "data_memwidth" prop with fw_cfg_init_data_memwidth() Laszlo Ersek
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 4/7] arm: add fw_cfg to "virt" board Laszlo Ersek
2014-12-12 12:55 ` Peter Maydell
2014-12-12 13:41 ` Laszlo Ersek
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 5/7] hw/loader: split out load_image_gzipped_buffer() Laszlo Ersek
2014-12-12 13:11 ` Peter Maydell
2014-12-12 13:43 ` Laszlo Ersek [this message]
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 6/7] hw/arm: pass pristine kernel image to guest firmware over fw_cfg Laszlo Ersek
2014-12-12 13:20 ` Peter Maydell
2014-12-12 13:52 ` Laszlo Ersek
2014-12-12 13:57 ` Peter Maydell
2014-12-12 14:10 ` Laszlo Ersek
2014-12-12 14:14 ` Richard W.M. Jones
2014-12-12 14:24 ` Laszlo Ersek
2014-12-09 1:13 ` [Qemu-devel] [PATCH v3 7/7] hw/arm/virt: enable passing of EFI-stubbed kernel to guest UEFI firmware Laszlo Ersek
2014-12-12 13:20 ` Peter Maydell
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=548AF10A.3030407@redhat.com \
--to=lersek@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).