From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk, wim@iguana.be
Subject: Re: [patch 2/3] WATCHDOG: Clean out header of s3c2410_wdt driver.
Date: Mon, 23 Jun 2008 10:22:55 +0100 [thread overview]
Message-ID: <20080623102255.49d602bb@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080622230601.GD21835@fluff.org.uk>
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
next prev parent reply other threads:[~2008-06-23 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 21:36 [patch 0/3] s3c2410 watchdog fixes for next kernel release Ben Dooks
2008-06-22 21:36 ` [patch 1/3] WATCHDOG: Fix NULL usage in s3c2410_wdt driver Ben Dooks
2008-06-22 22:35 ` Alan Cox
2008-06-22 21:36 ` [patch 2/3] WATCHDOG: Clean out header of " Ben Dooks
2008-06-22 22:35 ` Alan Cox
2008-06-22 23:06 ` Ben Dooks
2008-06-23 9:22 ` Alan Cox [this message]
2008-06-22 21:36 ` [patch 3/3] WATCHDOG: Fix s3c2410_wdt driver coding style issues Ben Dooks
2008-06-22 22:34 ` Alan Cox
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=20080623102255.49d602bb@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wim@iguana.be \
/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
all inboxes | Powered by JetHome®