qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 14/14] lsi53c895a: current_dev is not used
Date: Thu,  2 Jun 2011 13:53:49 +0200	[thread overview]
Message-ID: <3d53f33baed3fc2252a9a6acd1e5cafb1ac79d2d.1307014903.git.quintela@redhat.com> (raw)
In-Reply-To: <cover.1307014902.git.quintela@redhat.com>
In-Reply-To: <cover.1307014902.git.quintela@redhat.com>


Signed-off-by: Juan Quintela <quintela@redhat.com>
---
 hw/lsi53c895a.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/hw/lsi53c895a.c b/hw/lsi53c895a.c
index 83084b6..90c6cbc 100644
--- a/hw/lsi53c895a.c
+++ b/hw/lsi53c895a.c
@@ -889,7 +889,6 @@ static void lsi_do_msgout(LSIState *s)
     uint8_t msg;
     int len;
     uint32_t current_tag;
-    SCSIDevice *current_dev;
     lsi_request *current_req, *p, *p_next;
     int id;

@@ -901,7 +900,6 @@ static void lsi_do_msgout(LSIState *s)
         current_req = lsi_find_by_tag(s, current_tag);
     }
     id = (current_tag >> 8) & 0xf;
-    current_dev = s->bus.devs[id];

     DPRINTF("MSG out len=%d\n", s->dbc);
     while (s->dbc) {
-- 
1.7.5.2

  parent reply	other threads:[~2011-06-02 11:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 11:53 [Qemu-devel] [PATCH 00/14] More gcc 4.6 warnings fixes Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 01/14] kvm: remove fop write only variable Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 02/14] tcg: define and set call_type only when it is used Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 03/14] flatload: memp was a write-only variable Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 04/14] xen: pentry is not used in this function Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 05/14] linuxload: id_change was a write only variable Juan Quintela
2011-06-10 17:04   ` Peter Maydell
2011-06-02 11:53 ` [Qemu-devel] [PATCH 06/14] flatload: end_code was only used in a debug message Juan Quintela
2011-06-10 15:31   ` Peter Maydell
2011-06-02 11:53 ` [Qemu-devel] [PATCH 07/14] alpha: fn2 was a write only variable Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 08/14] syscall: really return ret code Juan Quintela
2011-06-10 17:00   ` Peter Maydell
2011-06-02 11:53 ` [Qemu-devel] [PATCH 09/14] exec: last_first_tb was only used in !ONLY_USER case Juan Quintela
2011-06-17 11:38   ` Peter Maydell
2011-06-24 14:42   ` Stefan Hajnoczi
2011-06-02 11:53 ` [Qemu-devel] [PATCH 10/14] mips: we really need the extra arguments Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 11/14] linux-user: fpu_save_addr is not used Juan Quintela
2011-06-02 13:51   ` Peter Maydell
2011-06-02 14:59     ` Juan Quintela
2011-06-02 11:53 ` [Qemu-devel] [PATCH 12/14] linux-user: syscall should use sanitized arg1 Juan Quintela
2011-06-10 17:13   ` Peter Maydell
2011-06-02 11:53 ` [Qemu-devel] [PATCH 13/14] alpha: disp12 is not used for USER emulation Juan Quintela
2011-06-02 11:53 ` Juan Quintela [this message]
2011-06-02 12:24   ` [Qemu-devel] [PATCH 14/14] lsi53c895a: current_dev is not used Andreas Färber
2011-06-02 12:39     ` Juan Quintela
2011-06-02 13:05 ` [Qemu-devel] [PATCH 00/14] More gcc 4.6 warnings fixes Christophe Fergeau

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=3d53f33baed3fc2252a9a6acd1e5cafb1ac79d2d.1307014903.git.quintela@redhat.com \
    --to=quintela@redhat.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).