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

On Fri, Jun 29, 2012 at 11:05:16AM +0200, Zoltan Kelemen wrote:
> 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.
> 

We've done this before.  We can help you break it apart.

Step 1: Change all the existing spinlocks to spin_lock_bh().
Step 2: Do all the white space changes.
Step 3: Shuffle the global variable declarations around.

That's half the patch gone already.

regards,
dan carpenter


      reply	other threads:[~2012-06-29  9:32 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
2012-06-29  9:32     ` Dan Carpenter [this message]

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