linux-kernel - Re: [PATCH 3/8] USB: gadget: __init and _

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: <n2v8bd0f97a1004161640q640bade7xd4887dde5921b79e@mail.gmail.com>
Date:	Fri, 16 Apr 2010 19:40:50 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Michal Nazarewicz <m.nazarewicz@...sung.com>
Cc:	linux-usb@...r.kernel.org, Greg KH <greg@...ah.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Mike Frysinger <vapier@...too.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/8] USB: gadget: __init and __exit tags removed

On Fri, Apr 16, 2010 at 05:49, Michal Nazarewicz wrote:
> __init, __initdata and __exit tags have have been removed from
> various files to make it possible for gadgets that do not use
> the __init/__exit tags to use those.
>
> Files in question are related to:
> * the core composite framework,
> * the mass storage function (fixing a section mismatch) and
> * ethernet driver (ACM, ECM, RNDIS).

it would be nice if the expected behavior were documented somewhere so
we dont have to keep thrashing the section markings on the gadget
drivers.  first they get marked to save space for setups where it
makes no sense to keep the functions.  then they get tweaked to
support a semi-dynamic state.  now they're all removed to support yet
a different setup.

sounds like the system is insufficiently flexible to meet the
realistic needs of different groups.
-mike
--
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/