public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zoltan Kelemen" <zoltan.kelemen@digisec.se>
To: "Dan Carpenter" <dan.carpenter@oracle.com>
Cc: willy@meta-x.org, gregkh@linuxfoundation.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging:panel: Rewrite for fixing synchronization issues
Date: Fri, 29 Jun 2012 11:05:16 +0200	[thread overview]
Message-ID: <20120629090516.8845AD52AA77@bmail04.one.com> (raw)
In-Reply-To: <20120629072441.GN5333@mwanda>

On 29 jun 2012 09:24 "Dan Carpenter" <dan.carpenter@oracle.com> wrote:

> Gar...  Don't do this.  :/  Each bullet point here should be a
> separate patch.  Please break it apart and resend.

I understand a large patch is harder to audit than small incremental changes, but the patch was the result of a code rewrite, where I attempted to summarize the changes in large in the bulleted list. There isn't a one-to-one correspondence between a bullet and a change in the code. Breaking the rewrite into small pieces would not only be quite hard but to some extent even more confusing to audit since you risk to see the leaves instead of the tree.

> Do not create lock_pprt() and unlock_pprt() functions.  It doesn't
> save any lines of code.  It means that Sparse is unable check for

Good point. (The functions were a remnant from previous work-in-progress where they were used in common from process/softirq code, and used different lock calls depending on the context of the call).

Regards,
Zoltan

  reply	other threads:[~2012-06-29  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 20:57 [PATCH 1/3] staging:panel: Rewrite for fixing synchronization issues Zoltan Kelemen
2012-06-29  7:24 ` Dan Carpenter
2012-06-29  9:05   ` Zoltan Kelemen [this message]
2012-06-29  9:32     ` Dan Carpenter

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=20120629090516.8845AD52AA77@bmail04.one.com \
    --to=zoltan.kelemen@digisec.se \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@meta-x.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