mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	steiner@sgi.com
Subject: Re: [PATCH] uv/x2apic: update for change in pci bridge handling.
Date: Thu, 9 Jun 2011 08:13:30 -0700	[thread overview]
Message-ID: <20110609081330.21a49d9d@jbarnes-desktop> (raw)
In-Reply-To: <BANLkTi=8JQWojj4UrH1iBYN=tWdx5AuOCA@mail.gmail.com>

On Thu, 9 Jun 2011 13:43:52 +1000
Dave Airlie <airlied@gmail.com> wrote:

> On Wed, May 25, 2011 at 2:00 PM, Dave Airlie <airlied@gmail.com> wrote:
> > From: Dave Airlie <airlied@redhat.com>
> >
> > I forgot about the special uv handling code for this, so this
> > patch fixes it up.
> 
> ping?
> 
> This fixes a warning and bug in Linus tree,
> 
>   CC      arch/x86/kernel/apic/x2apic_uv_x.o
> /home/airlied/git/linux-2.6/arch/x86/kernel/apic/x2apic_uv_x.c: In
> function ‘uv_system_init’:
> /home/airlied/git/linux-2.6/arch/x86/kernel/apic/x2apic_uv_x.c:882:2:
> warning: passing argument 1 of ‘pci_register_set_vga_state’ from
> incompatible pointer type [enabled by default]
> /home/airlied/git/linux-2.6/include/linux/pci.h:1094:13: note:
> expected ‘arch_set_vga_state_t’ but argument is of type ‘int
> (*)(struct pci_dev *, bool,  unsigned int,  bool)’
> 
> 
> Dave.
> 
> >
> > Signed-off-by: Dave Airlie <airlied@redhat.com>
> > ---
> >  arch/x86/kernel/apic/x2apic_uv_x.c |    8 ++++----
> >  drivers/pci/pci.c                  |    4 ++--
> >  2 files changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/arch/x86/kernel/apic/x2apic_uv_x.c b/arch/x86/kernel/apic/x2apic_uv_x.c
> > index 33b10a0..185cd1e 100644
> > --- a/arch/x86/kernel/apic/x2apic_uv_x.c
> > +++ b/arch/x86/kernel/apic/x2apic_uv_x.c
> > @@ -599,14 +599,14 @@ late_initcall(uv_init_heartbeat);
> >
> >  /* Direct Legacy VGA I/O traffic to designated IOH */
> >  int uv_set_vga_state(struct pci_dev *pdev, bool decode,
> > -                     unsigned int command_bits, bool change_bridge)
> > +                     unsigned int command_bits, u32 flags)
> >  {
> >        int domain, bus, rc;
> >
> > -       PR_DEVEL("devfn %x decode %d cmd %x chg_brdg %d\n",
> > -                       pdev->devfn, decode, command_bits, change_bridge);
> > +       PR_DEVEL("devfn %x decode %d cmd %x flags %d\n",
> > +                       pdev->devfn, decode, command_bits, flags);
> >
> > -       if (!change_bridge)
> > +       if (!(flags & PCI_VGA_STATE_CHANGE_BRIDGE))
> >                return 0;
> >
> >        if ((command_bits & PCI_COMMAND_IO) == 0)
> > diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> > index a339237..4528ee7 100644
> > --- a/drivers/pci/pci.c
> > +++ b/drivers/pci/pci.c
> > @@ -2862,11 +2862,11 @@ void __init pci_register_set_vga_state(arch_set_vga_state_t func)
> >  }
> >
> >  static int pci_set_vga_state_arch(struct pci_dev *dev, bool decode,
> > -                     unsigned int command_bits, bool change_bridge)
> > +                     unsigned int command_bits, u32 flags)
> >  {
> >        if (arch_set_vga_state)
> >                return arch_set_vga_state(dev, decode, command_bits,
> > -                                               change_bridge);
> > +                                               flags);
> >        return 0;
> >  }

Yeah, this is fine with me, you can push it through your tree.

Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>

-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2011-06-09 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  4:00 Dave Airlie
2011-06-09  3:43 ` Dave Airlie
2011-06-09  7:09   ` Ingo Molnar
2011-06-09 10:32     ` Dave Airlie
2011-06-09 11:16       ` Ingo Molnar
2011-06-09 15:13   ` Jesse Barnes [this message]

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=20110609081330.21a49d9d@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.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

all inboxes | Powered by JetHome®