linux-kernel - Re: [PATCHv3 1/2] ARM: imx: Add core definitions for MX53

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:	Wed, 10 Nov 2010 18:09:12 +0100
From:	Sascha Hauer <s.hauer@...gutronix.de>
To:	Fabio Estevam <festevam@...il.com>
Cc:	amit.kucheria@...onical.com, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org, eric@...rea.com,
	u.kleine-koenig@...gutronix.de,
	Nguyen Dinh-R00091 <R00091@...escale.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCHv3 1/2] ARM: imx: Add core definitions for MX53

On Wed, Nov 10, 2010 at 03:04:27PM -0200, Fabio Estevam wrote:
> On Wed, Nov 10, 2010 at 2:46 PM, Sascha Hauer <s.hauer@...gutronix.de> wrote:
> ...
> 
> >> Agreed, but I was unsure how to proceed with adding clock code for mx53.
> >> Should I merge mx53 clock code into clock-mx51 and rename clock-mx51?
> >
> > Yes, to something like clock-mx51-mx53.c
> >
> 
> Or maybe clock-mx5x.c would be more generic.
> 
> This way when any other MX5x processor gets added we don't need to
> change the file name again.

This can happen with mx5x also when the next MX5x is incompatible like
we had with i.MX2x when i.MX25 came out. Anyway, in this case I don't
care much.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/