From: Christoph Hellwig <hch@lst.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Christoph Hellwig <hch@lst.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: Wed, 12 Apr 2017 19:16:22 +0200 [thread overview]
Message-ID: <20170412171622.GA8639@lst.de> (raw)
In-Reply-To: <20170412092101.cg63lwzwl44arukk@pd.tnic>
On Wed, Apr 12, 2017 at 11:21:01AM +0200, Borislav Petkov wrote:
> Do we need to mark pci_enable_msix_exact() deprecated or so, or maybe a
> checkpatch rule?
Did we ever do this for deprecated APIs before? For now I'm just watching
Linux-next and sending gentle reminders :)
next prev parent reply other threads:[~2017-04-12 17:16 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 [this message]
2017-04-12 17:28 ` Borislav Petkov
2017-04-12 17:30 ` Christoph Hellwig
2017-04-13 8:53 ` Johannes Thumshirn
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=20170412171622.GA8639@lst.de \
--to=hch@lst.de \
--cc=bp@alien8.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