All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: netdev@vger.kernel.org
Subject: Re: [PATCH 1/8] Phonet: fix NULL-deref in a8059512b120362b15424f152b2548fe8b11bd0c
Date: Tue, 8 Mar 2011 22:59:41 +0200	[thread overview]
Message-ID: <201103082259.41844.remi@remlab.net> (raw)
In-Reply-To: <20110308.112923.39177383.davem@davemloft.net>

	Hello,

On March 8th 2011 21:29:23 David Miller, you wrote :
> You don't even read what I tell you, which makes reviewing your work
> insanely frustrating.

Fair enough.

You were the one complaining about the Nokia mail server being insanely 
broken (in private email by the way). So I have to read stuff at home, and 
implement it the next day at work. Informations do get lost at night. I don't 
need to mention I don't like this is frustrating for us Nokians as well.

(...)
> It also irks me that you persisted to provide the most terse possible
> one-line commit message.  Have a conversation in your commit message,
> this isn't for you it's for other people trying to understand your
> work.

I'm trying to fix the terrible mess that ST-Ericsson left of the Phonet stack 
here. This wouldn't be an issue if the crap hadn't been merged, or if I had 
been given enough time to voice my concerns.

Just one WTF? out of many:

        static u8 data[4] = {
                0x03, 0x04,
        };
        data[2] = pn->tx_fc;
        data[3] = pn->rx_fc;

(Those coffee-deprivated, note the 'static' keyword.) I wonder if the guy ever 
wrote C (not C++) before he came to kernel.org and left as quickly.

I am totally fine with strictness on your part. I do genuinely believe it 
improves code quality and such, and do try to apply similar patterns when I am 
the reviewer. So I present my apologizes for my series  of unintended 
violations of The Process.

I just wish you'd been as strict back then. Nobody would be having this 
pointless non-technical discussion... Well... I'll fix it tomorrow because I 
don't want that kind of crap in the Linux kernel anyway.

Thanks every one you for your cooperation.

-- 
Rémi

  reply	other threads:[~2011-03-08 20:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 13:56 [RFCv3] [PATCH 0/8] net-next: Phonet fixes and cleanup Rémi Denis-Courmont
2011-03-08 13:56 ` [PATCH 1/8] Phonet: fix NULL-deref in a8059512b120362b15424f152b2548fe8b11bd0c Rémi Denis-Courmont
2011-03-08 19:29   ` David Miller
2011-03-08 20:59     ` Rémi Denis-Courmont [this message]
2011-03-08 21:09       ` David Miller
2011-03-08 21:30         ` Rémi Denis-Courmont
2011-03-08 21:34           ` David Miller
2011-03-08 13:57 ` [PATCH 2/8] Phonet: return an error when skb TX fails Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 3/8] Phonet: correct pipe backlog callback return values Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 4/8] Phonet: factor common code to send control messages Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 5/8] Phonet: allocate sock from accept syscall rather than soft IRQ Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 6/8] Phonet: provide pipe socket option to retrieve the pipe identifier Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 7/8] Phonet: support active connection without pipe controller on modem Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 8/8] Phonet: kill the ST-Ericsson pipe controller Kconfig Rémi Denis-Courmont

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=201103082259.41844.remi@remlab.net \
    --to=remi@remlab.net \
    --cc=netdev@vger.kernel.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.