From: Greg KH <gregkh@linuxfoundation.org>
To: "J. German Rivera" <German.Rivera@freescale.com>
Cc: arnd@arndb.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, stuart.yoder@freescale.com,
bhupesh.sharma@freescale.com, agraf@suse.de,
bhamciu1@freescale.com, nir.erez@freescale.com,
itai.katz@freescale.com, scottwood@freescale.com,
leoli@freescale.com, R89243@freescale.com,
dan.carpenter@oracle.com, richard.schmitt@freescale.com
Subject: Re: [PATCH v2 3/6] staging: fsl-mc: up-rev dpbp binary interface to v2.0
Date: Tue, 22 Sep 2015 20:08:01 -0700 [thread overview]
Message-ID: <20150923030801.GA18243@kroah.com> (raw)
In-Reply-To: <1442963339-32084-4-git-send-email-German.Rivera@freescale.com>
On Tue, Sep 22, 2015 at 06:08:56PM -0500, J. German Rivera wrote:
> Add cmd_flags parameter to all dpbp APIs to comply
> with the dpbp 2.0 MC interface. Updated MC version
> major number. Pass irq args in struct instead of
> separate args.
>
> Signed-off-by: J. German Rivera <German.Rivera@freescale.com>
> ---
> drivers/staging/fsl-mc/bus/dpbp.c | 136 ++++++++++++++++++++----------
> drivers/staging/fsl-mc/include/dpbp-cmd.h | 2 +-
> drivers/staging/fsl-mc/include/dpbp.h | 91 +++++++++++++++-----
> 3 files changed, 162 insertions(+), 67 deletions(-)
>
> diff --git a/drivers/staging/fsl-mc/bus/dpbp.c b/drivers/staging/fsl-mc/bus/dpbp.c
> index d99ab6d..0004e65 100644
> --- a/drivers/staging/fsl-mc/bus/dpbp.c
> +++ b/drivers/staging/fsl-mc/bus/dpbp.c
> @@ -34,14 +34,19 @@
> #include "../include/dpbp.h"
> #include "../include/dpbp-cmd.h"
>
> -int dpbp_open(struct fsl_mc_io *mc_io, int dpbp_id, uint16_t *token)
> +int dpbp_open(struct fsl_mc_io *mc_io,
> + uint32_t cmd_flags,
> + int dpbp_id,
> + uint16_t *token)
> {
> struct mc_command cmd = { 0 };
> int err;
>
> /* prepare command */
> cmd.header = mc_encode_cmd_header(DPBP_CMDID_OPEN,
> - MC_CMD_PRI_LOW, 0);
> + cmd_flags,
> + 0);
Why are you reformatting all of these calls when you don't have to
create a new line? Seems wasteful to me, as is:
> +
That empty line, why?
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-23 3:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 23:08 [PATCH v2 0/6] staging: fsl-mc: up-rev version of MC interface code J. German Rivera
2015-09-22 23:08 ` [PATCH v2 1/6] staging: fsl-mc: Add new flags field to MC command header J. German Rivera
2015-09-22 23:08 ` [PATCH v2 2/6] staging: fsl-mc: uprev dpmng binary interface to v8.0 J. German Rivera
2015-09-22 23:08 ` [PATCH v2 3/6] staging: fsl-mc: up-rev dpbp binary interface to v2.0 J. German Rivera
2015-09-23 3:08 ` Greg KH [this message]
2015-09-22 23:08 ` [PATCH v2 4/6] staging: fsl-mc: up-rev dpmcp " J. German Rivera
2015-09-22 23:08 ` [PATCH v2 5/6] staging: fsl-mc: up-rev dpcon " J. German Rivera
2015-09-22 23:08 ` [PATCH v2 6/6] staging: fsl-mc: up-rev dprc binary interface to v4.0 J. German Rivera
2015-09-23 9:26 ` Dan Carpenter
2015-09-24 18:39 ` Jose Rivera
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=20150923030801.GA18243@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=R89243@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=itai.katz@freescale.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.com \
/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