linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, <x86@kernel.org>,
	Wuyun <wuyun.wu@huawei.com>
Subject: Re: [PATCH] x86/MSI: Clean up unnecessary override function
Date: Wed, 25 Jun 2014 09:12:26 +0800	[thread overview]
Message-ID: <53AA21FA.7050801@huawei.com> (raw)
In-Reply-To: <20140624132136.GA28885@laptop.dumpdata.com>

> They do. Please in the future use 'git annotate' to
> figure out which commits added them in and see if
> those are still in use.

Hi Konrad,
   Thanks for your detailed explanation, I see what your mean,
you are right, x86_msi will be replaced in x86/xen running.
This is the point I missing.

Bjorn, please drop this patch.

Thanks!
Yijing.

> 
> P.S.
> Look in arch/x86/pci/xen.c
>>
>> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
>> ---
>>  arch/x86/kernel/x86_init.c |   22 ----------------------
>>  1 files changed, 0 insertions(+), 22 deletions(-)
>>
>> diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c
>> index e48b674..00529fa 100644
>> --- a/arch/x86/kernel/x86_init.c
>> +++ b/arch/x86/kernel/x86_init.c
>> @@ -113,11 +113,7 @@ struct x86_msi_ops x86_msi = {
>>  	.setup_msi_irqs		= native_setup_msi_irqs,
>>  	.compose_msi_msg	= native_compose_msi_msg,
>>  	.teardown_msi_irq	= native_teardown_msi_irq,
>> -	.teardown_msi_irqs	= default_teardown_msi_irqs,
>> -	.restore_msi_irqs	= default_restore_msi_irqs,
>>  	.setup_hpet_msi		= default_setup_hpet_msi,
>> -	.msi_mask_irq		= default_msi_mask_irq,
>> -	.msix_mask_irq		= default_msix_mask_irq,
>>  };
>>  
>>  /* MSI arch specific hooks */
>> @@ -126,28 +122,10 @@ int arch_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
>>  	return x86_msi.setup_msi_irqs(dev, nvec, type);
>>  }
>>  
>> -void arch_teardown_msi_irqs(struct pci_dev *dev)
>> -{
>> -	x86_msi.teardown_msi_irqs(dev);
>> -}
>> -
>>  void arch_teardown_msi_irq(unsigned int irq)
>>  {
>>  	x86_msi.teardown_msi_irq(irq);
>>  }
>> -
>> -void arch_restore_msi_irqs(struct pci_dev *dev)
>> -{
>> -	x86_msi.restore_msi_irqs(dev);
>> -}
>> -u32 arch_msi_mask_irq(struct msi_desc *desc, u32 mask, u32 flag)
>> -{
>> -	return x86_msi.msi_mask_irq(desc, mask, flag);
>> -}
>> -u32 arch_msix_mask_irq(struct msi_desc *desc, u32 flag)
>> -{
>> -	return x86_msi.msix_mask_irq(desc, flag);
>> -}
>>  #endif
>>  
>>  struct x86_io_apic_ops x86_io_apic_ops = {
>> -- 
>> 1.7.1
>>
>>
> 
> .
> 


-- 
Thanks!
Yijing


      reply	other threads:[~2014-06-25  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  8:30 [PATCH] x86/MSI: Clean up unnecessary override function Yijing Wang
2014-06-24 13:21 ` Konrad Rzeszutek Wilk
2014-06-25  1:12   ` Yijing Wang [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=53AA21FA.7050801@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wuyun.wu@huawei.com \
    --cc=x86@kernel.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).