linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Borislav Petkov <bp@alien8.de>,
	Sergey Temerkhanov <s.temerkhanov@gmail.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: please use pci_alloc_irq_vectors in thunderx_edac.
Date: Thu, 13 Apr 2017 10:53:26 +0200	[thread overview]
Message-ID: <20170413085326.GD6734@linux-x5ow.site> (raw)
In-Reply-To: <20170412173021.GA8910@lst.de>

On Wed, Apr 12, 2017 at 07:30:22PM +0200, Christoph Hellwig wrote:
> > shows some have been done. I wonder whether marking
> > pci_enable_msix_exact() would cause a lot of warnings though. An
> > allyesconfig build would tell...
> 
> It would cause lots of warnings.  The problem with __deprecated is that
> it causes warnings for existing users, not just new ones.

So a checkpatch rule is the way to go, I guess.

-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

      reply	other threads:[~2017-04-13  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  6:06 please use pci_alloc_irq_vectors in thunderx_edac Christoph Hellwig
2017-04-12  9:21 ` Borislav Petkov
2017-04-12 17:16   ` Christoph Hellwig
2017-04-12 17:28     ` Borislav Petkov
2017-04-12 17:30       ` Christoph Hellwig
2017-04-13  8:53         ` Johannes Thumshirn [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=20170413085326.GD6734@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=bp@alien8.de \
    --cc=hch@lst.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.temerkhanov@gmail.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;
as well as URLs for NNTP newsgroup(s).