From: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Joe Perches' <joe@perches.com>,
linux-kernel@vger.kernel.org,
'Bjorn Helgaas' <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 38/39] PCI: remove DEFINE_PCI_DEVICE_TABLE macro
Date: Mon, 2 Dec 2013 17:27:11 -0800 [thread overview]
Message-ID: <20131203012711.GA32730@kroah.com> (raw)
In-Reply-To: <003e01ceefc5$1a6f9880$4f4ec980$%han@samsung.com>
On Tue, Dec 03, 2013 at 10:15:06AM +0900, Jingoo Han wrote:
> On Tuesday, December 03, 2013 8:52 AM, Joe Perches wrote:
> > On Tue, 2013-12-03 at 08:32 +0900, Jingoo Han wrote:
> > > Don't use DEFINE_PCI_DEVICE_TABLE macro, because this macro
> > > is not preferred. Also, the definition of DEFINE_PCI_DEVICE_TABLE
> > > macro is removed.
> >
> > These sorts of treewide conversions are almost never
> > applied wholesale.
> >
> > This patch is not appropriate until there are no more
> > uses of DEFINE_PCI_DEVICE_TABLE in Linus' tree.
> >
> > Just marking the function as deprecated in the
> > documentation and the pci.h file is probably good
> > enough for now.
> >
> > see: http://lkml.org/lkml/2013/12/2/400
>
> Actually, I want to remove all DEFINE_PCI_DEVICE_TABLEs from the
> next 3.14-rc1 kernel, by merging all patches through Greg's tree.
>
> Greg,
> How about you?
No, take them through their individual driver trees please.
thanks,
greg k-h
prev parent reply other threads:[~2013-12-03 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001501ceefb1$69c96820$3d5c3860$%han@samsung.com>
2013-12-02 23:32 ` [PATCH 38/39] PCI: remove DEFINE_PCI_DEVICE_TABLE macro Jingoo Han
2013-12-02 23:52 ` Joe Perches
2013-12-03 1:15 ` Jingoo Han
2013-12-03 1:27 ` 'Greg Kroah-Hartman' [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=20131203012711.GA32730@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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