From: Dan Carpenter <dan.carpenter@oracle.com>
To: DaeSeok Youn <daeseok.youn@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
bergwolf@gmail.com, andreas.dilger@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: make functions as static
Date: Wed, 26 Feb 2014 14:31:38 +0300 [thread overview]
Message-ID: <20140226113138.GP26722@mwanda> (raw)
In-Reply-To: <CAHb8M2DiKuiD4A4-HuNRvkAgZ24uon1ekzAq9OiEE+36qHXcDg@mail.gmail.com>
On Wed, Feb 26, 2014 at 08:11:40PM +0900, DaeSeok Youn wrote:
> Actually , I saw some code like this file which is seperate line
> between return value and function name.
> So I didn't make one line of them.
>
> Ok, I will make another patch after merge this one.
No, you are misunderstanding what I am saying. Those type of function
declarations are allowed in the kernel so the original code is fine.
What I am saying is this patch is doing two thing but it should be doing
only one thing.
> @@ -53,8 +53,8 @@ lnd_t the_o2iblnd = {
>
> kib_data_t kiblnd_data;
>
> -__u32
> -kiblnd_cksum (void *ptr, int nob)
> +static __u32
> +kiblnd_cksum(void *ptr, int nob)
> {
> char *c = ptr;
> __u32 sum = 0;
Changing the white space here is OK because it is a minor related
white space change.
> @@ -368,7 +368,7 @@ kiblnd_create_peer(lnet_ni_t *ni, kib_peer_t **peerp, lnet_nid_t nid)
> }
>
> void
> -kiblnd_destroy_peer (kib_peer_t *peer)
> +kiblnd_destroy_peer(kib_peer_t *peer)
> {
This is a random unrelated white space change, so do it in a separate
patch.
regards,
dan carpenter
next prev parent reply other threads:[~2014-02-26 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 9:17 [PATCH] staging: lustre: make functions as static Daeseok Youn
2014-02-26 9:20 ` Dan Carpenter
2014-02-26 11:11 ` DaeSeok Youn
2014-02-26 11:31 ` Dan Carpenter [this message]
2014-02-26 11:41 ` DaeSeok Youn
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=20140226113138.GP26722@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox