From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: david@fries.net, jeff@garzik.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.6.34-rc2 breaks via82cxxx Host Protected Area
Date: Sat, 27 Mar 2010 16:34:08 +0100 [thread overview]
Message-ID: <201003271634.08054.bzolnier@gmail.com> (raw)
In-Reply-To: <20100327.074434.193717071.davem@davemloft.net>
On Saturday 27 March 2010 03:44:34 pm David Miller wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Date: Sat, 27 Mar 2010 11:19:53 +0100
>
> > The commit itself may also have a problem but since it was _never_ in
> > linux-next tree it never saw a wider upstream testing.
>
> This is not true Bart.
Uh? I had verified my claims before writing previous mail..
The patch ("via82cxxx: workaround h/w bugs") appeared in Linus'
tree on 19th January and it was neither in next-20100101 nor in
next-20100119.. etc.
Why? I have no idea.. I've just noticed it today..
> My ide-2.6 and ide-next-2.6 trees are both included in
> linux-next And if they are not, that needs to be fixed
> because they very much are intended to be.
Not my area of responsibility..
> In any event, you wrote a patch which broke something and
> if you're not willing to work on a fix I have no choice
> but to simply revert.
Please..
You picked a patch out of larger patch series posted to a mailing
list (which was clearly marked as a one for my atang tree and not
for upstream), then you merged it adding your sign-off, did poor
job w.r.t. linux-next testing phase and now I'm the one to blame
for the breakage? :)
Well, your stance on kernel project management has been already
made crystal clear during rt28xx driver discussions so I'm not
really surprised here. I also don't remember ever signing support
contract with you or your employer so I will be putting your mails
into a separate folder (lets call it 'almost-spam') from now on..
--
Bartlomiej Zolnierkiewicz
next prev parent reply other threads:[~2010-03-27 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 23:21 2.6.34-rc2 breaks via82cxxx Host Protected Area David Fries
2010-03-27 0:12 ` Jeff Garzik
2010-03-27 0:36 ` David Fries
2010-03-27 0:42 ` Jeff Garzik
2010-03-27 2:09 ` David Fries
2010-03-27 10:19 ` Bartlomiej Zolnierkiewicz
2010-03-27 14:44 ` David Miller
2010-03-27 15:34 ` Bartlomiej Zolnierkiewicz [this message]
2010-03-28 3:01 ` Stephen Rothwell
2010-03-28 11:48 ` Bartlomiej Zolnierkiewicz
2010-03-27 14:57 ` David Miller
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=201003271634.08054.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=david@fries.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.