From: Pavel Machek <pavel@ucw.cz>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Luis Correia <luis.f.correia@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jarek Poplawski <jarkao2@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
David Miller <davem@davemloft.net>
Subject: Re: [announce] new rt2800 drivers for Ralink wireless & project tree
Date: Fri, 6 Nov 2009 08:46:44 +0100 [thread overview]
Message-ID: <20091106074643.GA5562@ucw.cz> (raw)
In-Reply-To: <200911042251.23506.IvDoorn@gmail.com>
> > Look at the diffstat of Bart's driver:
> >
> > 15 files changed, 4036 insertions(+), 7158 deletions(-)
> >
> > He reduced your 5.2 KLOC non-working driver into a 1.8 KLOC _working_
> > driver.
>
> Bullshit, read the mails again.
This was uncalled for, right?
...
> Some people actually require sleep during the night, perhaps that you don't need
> that and can hence review 41 patches which changes thousands of lines on the
> same day the patches were submitted.
If you lack time, "Really start reading my mails" sentence you used at
the start of email is *not* user-friendly way to say that.
> > And _still_ your complaint about Bart's series is that he updated the
> > MAINTAINERS entry and added an entry for rt2800? Heck _sure_ he should
> > update it, he is the one doing the hard work of trying to bring it to
> > users, trying to clean up a messy driver space, trying to turn crap into
> > gold.
>
> So if I want to focus on something different in the kernel, I just send 1 patch,
> and a second to claim the maintainership of it even though there is an active
> maintainer available?
What about listing yourself as a maintainer for a start?
> > The thing is, if you dont have the time or interest to listen to and act
> > upon review feedback, be constructive about it and fix (obvious)
> > structural problems in your rt2800 code, you should just step aside and
> > let Bart maintain what he is apparently more capable of maintaining than
> > you are.
> >
> > What you are doing here is a thinly veiled land-grab: you did a minimal
> > token driver for rt2800 that doesnt work, kept it in your private tree
> > for _1.5 years_, and the moment someone _else_ came along and did
> > something better and more functional in drivers/staging/, you discovered
> > your sudden interest for it and moved the crappy driver upstream at
> > lightning's speed (it is already in net-next AFAICS, despite negative
> > test and review feedback) - ignoring and throwing away all the work that
> > Bart has done.
>
> Get your facts straight, the bullshit level in your mail is staggering.
>
> You have no fucking clue who wrote the rt2800 driver which is in
> drivers/staging/,
Perhaps you should not be a maintainer if you can't behave yourself?
> Because a lot of people prefer looking from the sideline,
> contributing _nothing_
Given your behaviour, I'm not suprised people are not too eager to
work with you.
> As for "throwing away that work" I ACKED 10 of his patches, and said I would review
> the rest later! But like I said, apparently it is a bad habit for people to sleep during
> the night.
Read your email again. It was quite far from 'acked 10, asked for
time'. You flamed him first.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
Bartlomiej Zolnierkiewicz
<bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>,
Luis Correia
<luis.f.correia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
Jarek Poplawski <jarkao2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Subject: Re: [announce] new rt2800 drivers for Ralink wireless & project tree
Date: Fri, 6 Nov 2009 08:46:44 +0100 [thread overview]
Message-ID: <20091106074643.GA5562@ucw.cz> (raw)
In-Reply-To: <200911042251.23506.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Look at the diffstat of Bart's driver:
> >
> > 15 files changed, 4036 insertions(+), 7158 deletions(-)
> >
> > He reduced your 5.2 KLOC non-working driver into a 1.8 KLOC _working_
> > driver.
>
> Bullshit, read the mails again.
This was uncalled for, right?
...
> Some people actually require sleep during the night, perhaps that you don't need
> that and can hence review 41 patches which changes thousands of lines on the
> same day the patches were submitted.
If you lack time, "Really start reading my mails" sentence you used at
the start of email is *not* user-friendly way to say that.
> > And _still_ your complaint about Bart's series is that he updated the
> > MAINTAINERS entry and added an entry for rt2800? Heck _sure_ he should
> > update it, he is the one doing the hard work of trying to bring it to
> > users, trying to clean up a messy driver space, trying to turn crap into
> > gold.
>
> So if I want to focus on something different in the kernel, I just send 1 patch,
> and a second to claim the maintainership of it even though there is an active
> maintainer available?
What about listing yourself as a maintainer for a start?
> > The thing is, if you dont have the time or interest to listen to and act
> > upon review feedback, be constructive about it and fix (obvious)
> > structural problems in your rt2800 code, you should just step aside and
> > let Bart maintain what he is apparently more capable of maintaining than
> > you are.
> >
> > What you are doing here is a thinly veiled land-grab: you did a minimal
> > token driver for rt2800 that doesnt work, kept it in your private tree
> > for _1.5 years_, and the moment someone _else_ came along and did
> > something better and more functional in drivers/staging/, you discovered
> > your sudden interest for it and moved the crappy driver upstream at
> > lightning's speed (it is already in net-next AFAICS, despite negative
> > test and review feedback) - ignoring and throwing away all the work that
> > Bart has done.
>
> Get your facts straight, the bullshit level in your mail is staggering.
>
> You have no fucking clue who wrote the rt2800 driver which is in
> drivers/staging/,
Perhaps you should not be a maintainer if you can't behave yourself?
> Because a lot of people prefer looking from the sideline,
> contributing _nothing_
Given your behaviour, I'm not suprised people are not too eager to
work with you.
> As for "throwing away that work" I ACKED 10 of his patches, and said I would review
> the rest later! But like I said, apparently it is a bad habit for people to sleep during
> the night.
Read your email again. It was quite far from 'acked 10, asked for
time'. You flamed him first.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-06 7:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:51 [announce] new rt2800 drivers for Ralink wireless & project tree Bartlomiej Zolnierkiewicz
2009-11-03 21:00 ` Ivo van Doorn
2009-11-03 21:44 ` Bartlomiej Zolnierkiewicz
2009-11-03 22:01 ` Ivo van Doorn
2009-11-03 22:34 ` Bartlomiej Zolnierkiewicz
2009-11-03 23:09 ` Gertjan van Wingerde
2009-11-03 23:46 ` Bartlomiej Zolnierkiewicz
2009-11-04 1:33 ` Julian Calaby
2009-11-04 1:33 ` Julian Calaby
2009-11-04 2:28 ` Bartlomiej Zolnierkiewicz
2009-11-03 23:48 ` Alan Cox
2009-11-03 23:48 ` Alan Cox
2009-11-03 23:52 ` Bartlomiej Zolnierkiewicz
2009-11-04 0:40 ` Alan Cox
2009-11-04 0:48 ` Bartlomiej Zolnierkiewicz
2009-11-04 8:37 ` Ingo Molnar
2009-11-04 14:38 ` John W. Linville
2009-11-04 14:38 ` John W. Linville
2009-11-04 21:51 ` Ivo van Doorn
2009-11-04 22:12 ` John W. Linville
2009-11-04 22:12 ` John W. Linville
2009-11-06 7:46 ` Pavel Machek [this message]
2009-11-06 7:46 ` Pavel Machek
2009-11-06 17:58 ` Ivo van Doorn
2009-11-06 18:30 ` Bartlomiej Zolnierkiewicz
2009-11-06 18:30 ` Bartlomiej Zolnierkiewicz
2009-11-06 18:59 ` John W. Linville
2009-11-07 17:30 ` Pavel Machek
2009-11-07 17:30 ` Pavel Machek
2009-11-07 18:12 ` Luis Correia
2009-11-07 18:31 ` Ivo van Doorn
2009-11-07 18:31 ` Ivo van Doorn
2009-11-07 19:43 ` Luis R. Rodriguez
2009-11-03 21:01 ` Gertjan van Wingerde
2009-11-03 21:01 ` Gertjan van Wingerde
2009-11-04 15:15 ` John W. Linville
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=20091106074643.GA5562@ucw.cz \
--to=pavel@ucw.cz \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=ivdoorn@gmail.com \
--cc=jarkao2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luis.f.correia@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
/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.