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] [day] [month] [year] [list]

Date:	Mon, 23 Jun 2008 10:22:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ben Dooks <ben-linux@...ff.org>
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.

O> > 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?

Yes - and posted patch series to the lists. The entire watchdog tree went
systematically through the cleanup process. Then I've queued a small
series of patches which are a proposed rework of Wim's idea about
changing the API for watchdogs entirely.

It has slipped back out of sight of most people for ages because Wim has
been attending to other things so it has been queued for about 3 weeks.

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