public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Joerg Roedel <joro@8bytes.org>
Cc: Vaughan Cao <vaughan.cao@oracle.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove duplicate checking code
Date: Thu, 29 May 2014 15:45:47 +0200	[thread overview]
Message-ID: <1401371147.22923.4.camel@x220> (raw)
In-Reply-To: <20140526093959.GH17056@8bytes.org>

On Mon, 2014-05-26 at 11:39 +0200, Joerg Roedel wrote:
> On Fri, May 16, 2014 at 03:39:40PM +0800, Vaughan Cao wrote:
> > amd_iommu_rlookup_table[devid] != NULL is already guaranteed by check_device
> > called before, it's fine to attach device at this point.
> > 
> > Signed-off-by: Vaughan Cao <vaughan.cao@oracle.com>
> > ---
> >  drivers/iommu/amd_iommu.c | 6 ------
> >  1 file changed, 6 deletions(-)
> 
> Applied, thanks.

This one entered linux-next, as of next-20142527, in commit ecef115d4540
("iommu/amd: Remove duplicate checking code"). It triggers an obviously
correct warning:
    drivers/iommu/amd_iommu.c: In function ‘amd_iommu_init_passthrough’:
    drivers/iommu/amd_iommu.c:3503:6: warning: unused variable ‘devid’ [-Wunused-variable]
      u16 devid;
          ^
    drivers/iommu/amd_iommu.c:3502:20: warning: unused variable ‘iommu’ [-Wunused-variable]
      struct amd_iommu *iommu;
                        ^

Is the trivial fix for this queued somewhere?


Paul Bolle


  reply	other threads:[~2014-05-29 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  7:39 [PATCH] remove duplicate checking code Vaughan Cao
2014-05-26  9:39 ` Joerg Roedel
2014-05-29 13:45   ` Paul Bolle [this message]
2014-05-30 18:21     ` Joerg Roedel

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=1401371147.22923.4.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vaughan.cao@oracle.com \
    /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