From: Jiri Slaby <jirislaby@gmail.com>
To: Bruce Beare <bbeare1@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Bill Pemberton <wfp5p@virginia.edu>,
devel@driverdev.osuosl.org, linux-kernel@vger.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
Date: Sat, 10 Oct 2009 00:28:24 +0200 [thread overview]
Message-ID: <4ACFB908.6070708@gmail.com> (raw)
In-Reply-To: <1255122698-12390-1-git-send-email-bbeare1@gmail.com>
On 10/09/2009 11:11 PM, Bruce Beare wrote:
> - 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);
And possibly switch this to kzalloc and remove the for below. (As a
separate patch.)
> for (i = 0; i < 32; i++) {
> - dig_in_config[i].kind = 0;
> - dig_in_config[i].bits = 0;
> - dig_in_config[i].min = 0;
> - dig_in_config[i].max = 0;
> - dig_out_config[i].kind = 0;
> - dig_out_config[i].bits = 0;
> - dig_out_config[i].min = 0;
> - dig_out_config[i].max = 0;
> - chan_in_config[i].kind = 0;
> - chan_in_config[i].bits = 0;
> - chan_in_config[i].min = 0;
> - chan_in_config[i].max = 0;
> - chan_out_config[i].kind = 0;
> - chan_out_config[i].bits = 0;
> - chan_out_config[i].min = 0;
> - chan_out_config[i].max = 0;
> + config_data->dig_in_config[i].kind = 0;
> + config_data->dig_in_config[i].bits = 0;
> + config_data->dig_in_config[i].min = 0;
> + config_data->dig_in_config[i].max = 0;
> + config_data->dig_out_config[i].kind = 0;
> + config_data->dig_out_config[i].bits = 0;
> + config_data->dig_out_config[i].min = 0;
> + config_data->dig_out_config[i].max = 0;
> + config_data->chan_in_config[i].kind = 0;
> + config_data->chan_in_config[i].bits = 0;
> + config_data->chan_in_config[i].min = 0;
> + config_data->chan_in_config[i].max = 0;
> + config_data->chan_out_config[i].kind = 0;
> + config_data->chan_out_config[i].bits = 0;
> + config_data->chan_out_config[i].min = 0;
> + config_data->chan_out_config[i].max = 0;
prev parent reply other threads:[~2009-10-09 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:11 [PATCH] Cleanups for: line length, printk KERN_ argument, stack frame size > 2048 (added a kmalloc/kfree), style/formatting errors, incorrect include files Bruce Beare
2009-10-09 21:16 ` Greg KH
2009-10-09 21:27 ` Randy Dunlap
2009-10-09 21:29 ` Greg KH
2009-10-09 21:41 ` Bruce B
2009-10-09 21:50 ` Greg KH
2009-10-09 21:31 ` Bruce B
2009-10-09 21:55 ` Daniel Walker
2009-10-09 21:23 ` Randy Dunlap
2009-10-09 21:29 ` Bruce B
2009-10-09 21:31 ` Randy Dunlap
2009-10-09 22:28 ` Jiri Slaby [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=4ACFB908.6070708@gmail.com \
--to=jirislaby@gmail.com \
--cc=bbeare1@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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