From: Joe Perches <joe@perches.com>
To: Ivaylo DImitrov <ivo.g.dimitrov.75@gmail.com>
Cc: gregkh@linuxfoundation.org, omar.ramirez@copitl.com,
pali.rohar@gmail.com, pavel@ucw.cz, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org,
Ivaylo Dimitrov <freemangordon@abv.bg>
Subject: Re: [PATCH v2] Staging: TIDSPBRIDGE: Remove UUID helper
Date: Mon, 09 Dec 2013 10:34:48 -0800 [thread overview]
Message-ID: <1386614088.8168.12.camel@joe-AO722> (raw)
In-Reply-To: <1386583996-5648-1-git-send-email-ivo.g.dimitrov.75@gmail.com>
On Mon, 2013-12-09 at 12:13 +0200, Ivaylo DImitrov wrote:
> From: Ivaylo Dimitrov <freemangordon@abv.bg>
>
> Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't
> need to be exported. It can also be made way simpler by using sscanf.
Hi Ivaylo.
Trivial notes:
The function name change in dbcdc.c from
uuid_uuid_from_string to dcd_uuid_from_string
seems unnecessary.
If you are going to change the name, please
also reindent the multi-line statements to the
open parenthesis as the rest of the file has
that style.
> diff --git a/drivers/staging/tidspbridge/rmgr/dbdcd.c b/drivers/staging/tidspbridge/rmgr/dbdcd.c
[]
> @@ -1001,7 +1042,7 @@ static int get_attrs_from_buf(char *psz_buf, u32 ul_buf_size,
> token = strsep(&psz_cur, seps);
>
> /* dsp_uuid ui_node_id */
> - uuid_uuid_from_string(token,
> + dcd_uuid_from_string(token,
> &gen_obj->obj_data.node_obj.ndb_props.
> ui_node_id);
> token = strsep(&psz_cur, seps);
The 2nd and 3rd lines of dcd_uuid_from_string
should be moved 1 left.
> @@ -1400,7 +1441,7 @@ static int get_dep_lib_info(struct dcd_manager *hdcd_mgr,
> break;
> } else {
> /* Retrieve UUID string. */
> - uuid_uuid_from_string(token,
> + dcd_uuid_from_string(token,
> &(dep_lib_uuids
> [dep_libs]));
> /* Is this library persistent? */
here too.
It also appears as if these could set status
to the from_string return value and error-out
when non-zero.
next prev parent reply other threads:[~2013-12-09 18:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 17:07 [PATCH] " Ivaylo DImitrov
2013-12-01 19:06 ` Joe Perches
2013-12-01 23:26 ` Ivajlo Dimitrov
2013-12-06 6:05 ` Ivajlo Dimitrov
2013-12-06 7:32 ` Dan Carpenter
2013-12-06 7:41 ` Ivajlo Dimitrov
2013-12-06 15:10 ` gregkh
2013-12-07 8:41 ` Ivajlo Dimitrov
2013-12-08 7:18 ` gregkh
2013-12-08 12:32 ` Pavel Machek
2013-12-09 10:13 ` [PATCH v2] " Ivaylo DImitrov
2013-12-09 14:40 ` Pavel Machek
2013-12-09 18:34 ` Joe Perches [this message]
2013-12-10 22:03 ` [PATCH v3] " Ivaylo DImitrov
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=1386614088.8168.12.camel@joe-AO722 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=freemangordon@abv.bg \
--cc=gregkh@linuxfoundation.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.ramirez@copitl.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®