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: <20100114082823.63379b3d@jbarnes-piketon>
Date:	Thu, 14 Jan 2010 08:28:23 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	David Miller <davem@...emloft.net>
Cc:	gregkh@...e.de, tilman@...p.cc, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	isdn@...ux-pingi.de, isdn4linux@...tserv.isdn4linux.de
Subject: Re: [PATCH] pci: push deprecated pci_find_device() function to last
 user

On Thu, 14 Jan 2010 00:12:04 -0800 (PST)
David Miller <davem@...emloft.net> wrote:

> From: Greg KH <gregkh@...e.de>
> Date: Wed, 13 Jan 2010 20:43:31 -0800
> 
> > On Wed, Jan 13, 2010 at 08:33:38PM -0800, David Miller wrote:
> >> From: Tilman Schmidt <tilman@...p.cc>
> >> Date: Wed, 13 Jan 2010 15:23:28 +0100 (CET)
> >> 
> >> > The ISDN4Linux HiSax driver family contains the last remaining
> >> > users of the deprecated pci_find_device() function. This patch
> >> > creates a private copy of that function in HiSax, and removes
> >> > the now unused global function together with its controlling
> >> > configuration option, CONFIG_PCI_LEGACY.
> >> > 
> >> > Impact: code reorganization, no functional change
> >> > Signed-off-by: Tilman Schmidt <tilman@...p.cc>
> >> > ---
> >> > Note: This patch is not, nor does it intend to be, checkpatch.pl
> >> > clean. The issues checkpatch.pl reports on it were already
> >> > present before, and are unrelated to the topic of this patch.
> >> 
> >> I'm fine with this, and Greg or whoever else can take this
> >> through a driver or PCI specific tree if they want:
> >> 
> >> Acked-by: David S. Miller <davem@...emloft.net>
> > 
> > Where do ISDN patches go through, the network tree?
> > 
> > Acked-by: Greg Kroah-Hartman <gregkh@...e.de>
> 
> Yeah usually, but I thought the PCI tree might want this one
> because it tosses things from drivers/pci

I can take it, but I lost the original patch.  Tilman, can you resend?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ