[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1255125329.18167.412.camel@desktop>
Date: Fri, 09 Oct 2009 14:55:29 -0700
From: Daniel Walker <dwalker@...o99.com>
To: Bruce B <bbeare1@...il.com>
Cc: Greg KH <gregkh@...e.de>, Bill Pemberton <wfp5p@...ginia.edu>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Cleanups for: line length, printk KERN_ argument,
stack frame size > 2048 (added a kmalloc/kfree), style/formatting errors,
incorrect include files
On Fri, 2009-10-09 at 14:31 -0700, Bruce B wrote:
>
>
> On Oct 9, 2009, at 2:16 PM, Greg KH wrote:
>
> >
> > Try changing one thing at a time per patch please.
> >
> > There's some bugs in here:
> >
> >> - struct config_t dig_in_config[32];
> >> - struct config_t dig_out_config[32];
> >> - struct config_t chan_in_config[32];
> >> - struct config_t chan_out_config[32];
> >> int i;
> >> + config_data = kmalloc(sizeof(struct config_data_t), GFP_KERNEL);
> >
> > Shouldn't that be:
> > config_data = kmalloc(sizeof(struct config_data_t)*32, GFP_KERNEL);
>
>
> The structure already has the [32]'s copied from the original defn's.
> If you like... I can still break up the commit into two patches. Also,
> moving the *32 out isn't a bad idea; were I
> to break it up, I would likely do so.
I would break it up .. Especially pulling out run time changes from
cleanups .. Also neither patch has a sign off line, and this patch
actually adds one line over 80 so that at least doesn't go along with
your subject..
If your going to respin this patches your first patch "[PATCH] Cleanup:
indent/format errors, printk calls." added some trailing whitespace too.
So you could do both..
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists