From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Andreas Oberritter <obi@linuxtv.org>,
Antti Palosaari <crope@iki.fi>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] DVB: dvb_frontend: fix delayed thread exit
Date: Sat, 10 Dec 2011 08:28:46 -0200 [thread overview]
Message-ID: <4EE3345E.5050304@redhat.com> (raw)
In-Reply-To: <CAGoCfiyx6JR_MiVdC=ZGw_G-hzrE7O8mZp1a8of8=PcxW_P82g@mail.gmail.com>
On 10-12-2011 00:25, Devin Heitmueller wrote:
> Hello Andreas,
>
> On Fri, Dec 9, 2011 at 9:06 PM, Andreas Oberritter<obi@linuxtv.org> wrote:
>> WTF, Devin, you again? I haven't asked anyone to upstream it. Feel free
>> to analyze the code and resubmit it.
>
> 1. It's marked with a subject line that starts with "[PATCH]"
> 2. It has your SIgned-Off-By line.
> 3. it was sent to the mailing list.
> 4. It doesn't have any keywords like "RFC" or "proposed".
Devin,
You're over-reacting. This patch were a reply from Andreas to a thread,
and not a separate patch submission.
Patches like are generally handled as RFC, especially since it doesn't
contain a description.
> If you don't intend for it to go upstream then don't do all of the above.
>
> I'm not sure if your "WTF, Devin, you again?" is some indication that
> I'm annoying you. The last patch you submitted that touches the
> threading in dvb_frontend.c had a host of problems and was clearly not
> well researched (i.e. "DVB: dvb_frontend: convert semaphore to
> mutex"). As in this case, there is no background indicating that this
> patch has been fully thought out and due diligence has been done.
>
> Maybe you have thoroughly researched the change, taken the time to
> fully understand its effects, and tested it with a variety of boards
> and scenarios. Without a good patch description, there is no way to
> know.
>
> I apologize if you're inconvenienced if I'm making an active effort to
> prevent poorly documented changes from getting merged (which often
> result in regressions). Oh wait, I'm not sorry at all. Nevermind.
>
> Devin
>
Regards,
Mauro
next prev parent reply other threads:[~2011-12-10 10:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 18:20 [PATCH] [media] drxk: Switch the delivery system on FE_SET_PROPERTY Mauro Carvalho Chehab
2011-12-09 18:26 ` Antti Palosaari
2011-12-09 18:58 ` Mauro Carvalho Chehab
2011-12-09 19:08 ` Antti Palosaari
2011-12-09 22:11 ` Mauro Carvalho Chehab
2011-12-09 22:33 ` Devin Heitmueller
2011-12-09 23:37 ` Mauro Carvalho Chehab
2011-12-09 23:43 ` Mauro Carvalho Chehab
2011-12-10 1:37 ` [PATCH] DVB: dvb_frontend: fix delayed thread exit Andreas Oberritter
2011-12-10 1:59 ` Devin Heitmueller
2011-12-10 2:06 ` Andreas Oberritter
2011-12-10 2:25 ` Devin Heitmueller
2011-12-10 10:28 ` Mauro Carvalho Chehab [this message]
2011-12-10 13:43 ` Devin Heitmueller
2011-12-10 16:16 ` Mauro Carvalho Chehab
2011-12-10 11:12 ` Mauro Carvalho Chehab
2011-12-09 19:00 ` [PATCHv2] [media] drxk: Switch the delivery system on FE_SET_PROPERTY Mauro Carvalho Chehab
2011-12-09 20:04 ` Eddi De Pieri
2011-12-09 22:04 ` Mauro Carvalho Chehab
2011-12-10 4:00 ` Oliver Endriss
2011-12-10 11:18 ` Mauro Carvalho Chehab
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=4EE3345E.5050304@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=obi@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox