All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sesterhenn <snakebyte@gmx.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] kzalloc() conversion in drivers/isdn
Date: Wed, 01 Mar 2006 07:40:20 +0000	[thread overview]
Message-ID: <1141198821.6512.3.camel@alice> (raw)
In-Reply-To: <1141024983.6530.1.camel@alice>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Tue, 2006-02-28 at 22:32 +0300, Alexey Dobriyan wrote:
> >      /* Allocate space for private device-specific data */
> > -    local = kmalloc(sizeof(local_info_t), GFP_KERNEL);
> > -    if (!local) return -ENOMEM;
> > -    memset(local, 0, sizeof(local_info_t));
> > +    local = kzalloc(sizeof(local_info_t), GFP_KERNEL);
> > +    if (!local)
> > +	return -ENOMEM;
> 
> Don't even try to sneak in unrelated changes. I mean, really. Why bother
> if I'll carefully drop them anyway?

I thought one should clean up the code while doing this
stuff? Or should coding style cleanups just be done in the exact
line one is changing? What would be the way to fix such thing?
Send a patch which indents and cleans the entire file, which would
possible break other patches in queue for that file. or send a patch
to clean up all if() foo; constructs in a subsystem?
Sorry to have caused you work overhead, i'll try not to do those
cleanups anymore.

Thanks Eric


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-03-01  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27  7:23 [KJ] kzalloc() conversion in drivers/isdn Eric Sesterhenn
2006-02-28 19:32 ` Alexey Dobriyan
2006-03-01  7:40 ` Eric Sesterhenn [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=1141198821.6512.3.camel@alice \
    --to=snakebyte@gmx.de \
    --cc=kernel-janitors@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.