linux-kernel - Re: [patch 2/3] WATCHDOG: Clean out header of s3c2410

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: <20080622230601.GD21835@fluff.org.uk>
Date:	Mon, 23 Jun 2008 00:06:01 +0100
From:	Ben Dooks <ben-linux@...ff.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Ben Dooks <ben-linux@...ff.org>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, wim@...ana.be
Subject: Re: [patch 2/3] WATCHDOG: Clean out header of s3c2410_wdt driver.

On Sun, Jun 22, 2008 at 11:35:16PM +0100, Alan Cox wrote:
> On Sun, 22 Jun 2008 22:36:50 +0100
> Ben Dooks <ben-linux@...ff.org> wrote:
> 
> > Remove the changelog from the top of the driver, which
> > is redundant as this information is more accurately
> > represented from the revision control holding the
> > file.
> > 
> > Signed-off-by: Ben Dooks <ben-linux@...ff.org>
> 
> NAK. This is going to clash with the big pile of changes stuck in the
> maintainers in queue.

Then why, as the original driver authour and current maintainer
do I not get told about this? This isn't the first time I've come
to apply this sort of thing and find that someone else has slipped
in an 'trivial' change such as whitespace that breaks an entire
patch series.

Do people not bother to check who wrote the driver or who is the
current maintainer before doing these things?

-- 
Ben (ben@...ff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'
--
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/