linux-kernel - Re: [PATCH 31/39] USB: remove DEFINE_PCI_DEVICE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131209083317.GA27716@kroah.com>
Date:	Mon, 9 Dec 2013 00:33:17 -0800
From:	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>
To:	Felipe Balbi <balbi@...com>
Cc:	Jingoo Han <jg1.han@...sung.com>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: [PATCH 31/39] USB: remove DEFINE_PCI_DEVICE_TABLE macro

On Sun, Dec 08, 2013 at 10:03:42PM -0600, Felipe Balbi wrote:
> On Tue, Dec 03, 2013 at 08:27:58AM +0900, Jingoo Han wrote:
> > Don't use DEFINE_PCI_DEVICE_TABLE macro, because this macro
> > is not preferred.
> > 
> > Signed-off-by: Jingoo Han <jg1.han@...sung.com>
> 
> I wonder why I wasn't Cc:ed to this email considering it touches three
> drivers I care about.
> 
> Greg, I have the original ones in my tree and I would really like to
> avoid rebasing my 'next' branch. Do we keep it there or do you want to
> avoid merging those commits ?

Just keep it there and we can handle the merge, it shouldn't be a big
deal, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/