public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wolfram Sang <w.sang@pengutronix.de>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: manual merge of the watchdog tree with Linus' tree
Date: Wed, 26 May 2010 08:35:34 +0200	[thread overview]
Message-ID: <20100526063534.GI3972@infomag.iguana.be> (raw)
In-Reply-To: <20100526133815.e62bacb8.sfr@canb.auug.org.au>

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.

  reply	other threads:[~2010-05-26  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  3:38 linux-next: manual merge of the watchdog tree with Linus' tree Stephen Rothwell
2010-05-26  6:35 ` Wim Van Sebroeck [this message]
2010-05-26  7:33   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2013-02-25  1:17 Stephen Rothwell
2017-11-27  0:06 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100526063534.GI3972@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=w.sang@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox