From: Bjorn Andersson <bjorn.andersson@sonymobile.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Kumar Gala <galak@codeaurora.org>,
Andy Gross <agross@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-soc@vger.kernel.org" <linux-soc@vger.kernel.org>
Subject: Re: [PATCH] firmware: qcom: scm: Peripheral Authentication Service
Date: Thu, 2 Jul 2015 10:37:25 -0700 [thread overview]
Message-ID: <20150702173725.GE9633@sonymobile.com> (raw)
In-Reply-To: <559564AC.6030100@codeaurora.org>
On Thu 02 Jul 09:19 PDT 2015, Stephen Boyd wrote:
> On 06/30/2015 12:46 PM, Bjorn Andersson wrote:
> > +
> > +int __qcom_scm_pas_init_image(u32 peripheral, const void *metadata, size_t size)
> > +{
> > + dma_addr_t mdata_phys;
> > + void *mdata_buf;
> > + u32 scm_ret;
> > + int ret;
> > + struct pas_init_image_req {
> > + u32 proc;
> > + u32 image_addr;
>
> Please mark these as __le32 and do the appropriate conversions to little
> endian.
Just out of curiosity, are there any big endian systems out there that
will run this code?
Either way I will fix this, to follow the style of the other parts of
this file.
> Also consider removing the struct name and just make it
> anonymous, i.e.
>
> struct {
> __le32 proc;
> __le32 image_addr;
> } cmd;
>
Right, there's no reason to name these.
Thanks,
Bjorn
next prev parent reply other threads:[~2015-07-02 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 19:46 [PATCH] firmware: qcom: scm: Peripheral Authentication Service Bjorn Andersson
2015-06-30 23:22 ` Andy Gross
2015-07-02 16:19 ` Stephen Boyd
2015-07-02 17:37 ` Bjorn Andersson [this message]
2015-07-02 18:37 ` Stephen Boyd
2015-07-15 18:58 ` [PATCH v2] " Bjorn Andersson
2015-07-15 21:33 ` Andy Gross
2015-07-16 0:39 ` Bjorn Andersson
2015-07-15 23:43 ` Stephen Boyd
2015-07-16 0:35 ` Bjorn Andersson
2015-07-16 0:55 ` Stephen Boyd
2015-07-16 1:22 ` Bjorn Andersson
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=20150702173725.GE9633@sonymobile.com \
--to=bjorn.andersson@sonymobile.com \
--cc=agross@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=sboyd@codeaurora.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