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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikZD5qie4y=tRpZXuea9D+_vDSGLMr+20p_PVkC@mail.gmail.com>
Date:	Wed, 23 Mar 2011 18:55:28 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Greg KH <gregkh@...e.de>,
	Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@...ricsson.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	linux-bluetooth@...r.kernel.org,
	Pavan Savoy <pavan_savoy@...y.com>,
	Vitaly Wool <vitalywool@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Arnd Bergmann <arnd@...db.de>,
	Marcel Holtmann <marcel@...tmann.org>,
	Lukasz Rymanowski <Lukasz.Rymanowski@...to.com>,
	Par-Gunnar Hjalmdahl <pghatwork@...il.com>,
	Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH 2/2] mach-ux500: Add CG2900 devices

2011/3/23 Greg KH <gregkh@...e.de>:

>>  arch/arm/mach-ux500/Makefile         |    4 +
>>  arch/arm/mach-ux500/board-mop500.c   |  160 ++++++++++++++++
>>  arch/arm/mach-ux500/devices-cg2900.c |  349 ++++++++++++++++++++++++++++++++++
>>  arch/arm/mach-ux500/devices-cg2900.h |   19 ++
>>  4 files changed, 532 insertions(+), 0 deletions(-)
>>  create mode 100644 arch/arm/mach-ux500/devices-cg2900.c
>>  create mode 100644 arch/arm/mach-ux500/devices-cg2900.h
>
> As this touches ARM specific code, I need an ack from the ARM maintainer
> before I can take this through the staging tree.  Is there any way to
> make it part of your drivers/staging/ submission?  There are other
> examples in the staging tree already that do this, why not do that here
> as well?

Hm yeah maybe it's possible if you move devices-cg2900.*
to staging/cg2900, then split off the stuff in board-mop500.c into
some drivers/staging/cg2900/board-mop500-cg2900.c which
adds the device in some proper initcall.

Do you think it can be done P-G? I might have overestimated
the work involved in moving that stuff to /staging.

Yours,
Linus Walleij
--
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