linux-kernel - Re: [PATCH 1/3] MFD: renamed ab3100.h to abx500.h

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: <v2l63386a3d1004130814i6c834d6boa105d4f7491cb01b@mail.gmail.com>
Date:	Tue, 13 Apr 2010 17:14:20 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	srinidhi.kasagar@...ricsson.com
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	STEricsson_nomadik_linux <STEricsson_nomadik_linux@...t.st.com>,
	Mattias WALLIN <mattias.wallin@...ricsson.com>
Subject: Re: [PATCH 1/3] MFD: renamed ab3100.h to abx500.h

2010/4/13 srinidhi <srinidhi.kasagar@...ricsson.com>:

> So do you expect the existing ab4500 also to be merged into abx500?

Don't think so, the 4500 is not related to the 3100, 3550 and 5500:s,
so they don't have much in common, whereas the latter share a lot of
characteristics. It's better if it stays where it is I think.

abx500 was the best name we could come up with that wasn't too
short, we contemplated abx.h but it was too short, abxxx0 looks
silly and so on. So abx500 denotes our largest family of mixsig ASICs
which has a lot in common, i.e. everything except the
AB8500/AB4500/STw4500, hope it's not too confusing...

But the ab4500 files should be renamed ab8500.[c|h] after current
product naming decisions though.

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/