linux-kernel - Re: linux-next: manual merge of the watchdog tree with Linus' tree

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]

Date:	Wed, 26 May 2010 08:35:34 +0200
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Wolfram Sang <w.sang@...gutronix.de>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: manual merge of the watchdog tree with Linus' tree

Hi Stephen,

> These are two versions of the same patch.  I used the version from Linus'
> tree - but I do need to ask what is the point of having a patch in
> linux-next for two days and then submitting a different version of the
> patch to Linus?  The changes are not insignificant. Both patches have the
> same Author date and SOB etc lines.

The one that went to Linus is the correct one.
I must apologise, I indeed fucked things up. I wasn't completely happy
with Wolfram's patch, changed it, Wolfram pointed out some things that
still could be improved and then we tested the final version, saw that
everything was OK and much beter then what we had.
And then I made the error to want to rush it in during this merge window
still (due to the fact that we are allready reviewing this driver for a
long time). So yes sorry, this was the wrong thing to do (well, not having
a better driver in, but the way the testing should have been done and the
correct process that should have been followed).

I will clean up the watchdog-next tree.

Sorry again,
Wim.

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