linux-kernel - Re: [RFC] Driver for Real Time Clock chip ST M41T65

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: <Pine.LNX.4.55.0808261524590.28361@cliff.in.clinika.pl>
Date:	Tue, 26 Aug 2008 15:42:46 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	"Steven A. Falco" <sfalco@...ris.com>
cc:	Will Newton <will.newton@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] Driver for Real Time Clock chip ST M41T65

On Tue, 26 Aug 2008, Steven A. Falco wrote:

> I'd also like to know if I should submit a new driver or mod the existing
> one.  If I mod the existing one, should it be renamed, should I update the
> Kconfig, existing defconfigs, etc?

 Keeping the code base common is good for maintenance.  Therefore for a 
minor differences like yours there is no doubt you better just add them to 
the existing driver.

 For larger variations -- it depends, i.e. it's better to keep the common
bits shared, unless the maintenance cost of such an approach exceeds that
of the other one.  Frequently it just boils down to doing it right which
may not necessarily be easy. ;)

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