qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 02/13] elfload: fix coding style nit
Date: Wed, 30 Sep 2009 19:43:38 +0200	[thread overview]
Message-ID: <20090930174338.GC1399@redhat.com> (raw)
In-Reply-To: <cover.1254332572.git.mst@redhat.com>

Put space between = and * when dereferencing a pointer,
to avoid confusion with old-style "*="

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 bsd-user/elfload.c   |    2 +-
 linux-user/elfload.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/bsd-user/elfload.c b/bsd-user/elfload.c
index 19981f0..33ddcc4 100644
--- a/bsd-user/elfload.c
+++ b/bsd-user/elfload.c
@@ -1268,7 +1268,7 @@ int load_elf_binary(struct linux_binprm * bprm, struct target_pt_regs * regs,
             }
             if (retval >= 0) {
                 interp_ex = *((struct exec *) bprm->buf); /* aout exec-header */
-                interp_elf_ex=*((struct elfhdr *) bprm->buf); /* elf exec-header */
+                interp_elf_ex = *((struct elfhdr *) bprm->buf); /* elf exec-header */
             }
             if (retval < 0) {
                 perror("load_elf_binary3");
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
index 7c8e771..07277a6 100644
--- a/linux-user/elfload.c
+++ b/linux-user/elfload.c
@@ -1476,7 +1476,7 @@ int load_elf_binary(struct linux_binprm * bprm, struct target_pt_regs * regs,
 	    }
 	    if (retval >= 0) {
 		interp_ex = *((struct exec *) bprm->buf); /* aout exec-header */
-		interp_elf_ex=*((struct elfhdr *) bprm->buf); /* elf exec-header */
+		interp_elf_ex = *((struct elfhdr *) bprm->buf); /* elf exec-header */
 	    }
 	    if (retval < 0) {
 		perror("load_elf_binary3");
-- 
1.6.5.rc2

  parent reply	other threads:[~2009-09-30 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1254332572.git.mst@redhat.com>
2009-09-30 17:43 ` [Qemu-devel] [PATCH 01/13] vvfat: fix coding style nit Michael S. Tsirkin
2009-09-30 17:43 ` Michael S. Tsirkin [this message]
2009-09-30 17:43 ` [Qemu-devel] [PATCH 03/13] gdbstub: " Michael S. Tsirkin
2009-09-30 17:43 ` [Qemu-devel] [PATCH 04/13] escc: " Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 05/13] omap_dma: fix unbalanced { in commented out code Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 06/13] twl92230: fix old style increment/decrement usage Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 07/13] linux-user: fix old style decrement usage Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 08/13] target-mips: unmatched brackets in if 0 Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 09/13] tests: " Michael S. Tsirkin
2009-09-30 18:59   ` [Qemu-devel] " Blue Swirl
2009-09-30 20:14   ` [Qemu-devel] " Markus Armbruster
2009-09-30 17:44 ` [Qemu-devel] [PATCH 10/13] linux-user: fix coding style nit Michael S. Tsirkin
2009-09-30 17:44 ` [Qemu-devel] [PATCH 11/13] net: " Michael S. Tsirkin
2009-09-30 17:45 ` [Qemu-devel] [PATCH 12/13] slirp: fix unmatched bracket in if 0 Michael S. Tsirkin
2009-09-30 17:45 ` [Qemu-devel] [PATCH 13/13] escc: fix another coding style nit Michael S. Tsirkin

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=20090930174338.GC1399@redhat.com \
    --to=mst@redhat.com \
    --cc=blauwirbel@gmail.com \
    --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).