linux-kernel - Re: [PATCH] usb: xhci: fix section mismatch in linux-next

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] [day] [month] [year] [list]

Date:	Fri, 16 Mar 2012 20:25:04 -0700
From:	Gerard Snitselaar <dev@...tselaar.org>
To:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
Cc:	gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: xhci: fix section mismatch in linux-next

On Fri, Mar 16, 2012 at 02:05:42PM -0700, Sarah Sharp wrote:
> This looks fine.  Does it need to be applied to stable as well, or is this
> just a "nice to have" that should be queued for 3.4?
> 
> Sarah Sharp
> 

Hi Sarah, it is only a problem in linux-next because that code path
was added to xhci_hcd_init() by 3429e91a which isn't in stable.

> On Fri, Mar 16, 2012 at 11:34:11AM -0700, Gerard Snitselaar wrote:
> > xhci_unregister_pci() is called in xhci_hcd_init().
> > 
> > Signed-off-by: Gerard Snitselaar <dev@...tselaar.org>
> > ---
> >  drivers/usb/host/xhci-pci.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
> > index ef98b38..0d7b851 100644
> > --- a/drivers/usb/host/xhci-pci.c
> > +++ b/drivers/usb/host/xhci-pci.c
> > @@ -326,7 +326,7 @@ int __init xhci_register_pci(void)
> >  	return pci_register_driver(&xhci_pci_driver);
> >  }
> >  
> > -void __exit xhci_unregister_pci(void)
> > +void xhci_unregister_pci(void)
> >  {
> >  	pci_unregister_driver(&xhci_pci_driver);
> >  }
> > -- 
> > 1.7.7.6
> > 

-- 
--
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/