From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: r8a66597-udc: add support for SUDMAC
Date: Fri, 30 Sep 2011 10:48:30 +0000 [thread overview]
Message-ID: <4E859E7E.1070800@renesas.com> (raw)
In-Reply-To: <4E803B16.1090905@renesas.com>
Hi,
2011/09/30 18:55, Felipe Balbi wrote:
> Hi,
>
> On Fri, Sep 30, 2011 at 06:49:15PM +0900, Yoshihiro Shimoda wrote:
>> Hi,
>> 2011/09/30 17:17, Felipe Balbi wrote:
>>> Hi,
>>>
>> < snip >
>>> On Mon, Sep 26, 2011 at 05:43:02PM +0900, Yoshihiro Shimoda wrote:
>>>> @@ -186,6 +187,51 @@ static inline void control_reg_sqclr(struct r8a66597 *r8a66597, u16 pipenum)
>>>> printk(KERN_ERR "unexpect pipe num(%d)\n", pipenum);
>>>> }
>>>>
>>>> +static void control_reg_sqset(struct r8a66597 *r8a66597, u16 pipenum)
>>>> +{
>>>> + unsigned long offset;
>>>> +
>>>> + pipe_stop(r8a66597, pipenum);
>>>> +
>>>> + if (pipenum = 0)
>>>> + r8a66597_bset(r8a66597, SQSET, DCPCTR);
>>>> + else if (pipenum < R8A66597_MAX_NUM_PIPE) {
>>>> + offset = get_pipectr_addr(pipenum);
>>>> + r8a66597_bset(r8a66597, SQSET, offset);
>>>> + } else
>>>> + printk(KERN_ERR "unexpect pipe num(%d)\n", pipenum);
>>>
>>> according to CodingStyle, if one branch as braces, all of them should
>>> have. Also, try to avoid printk(), I guess you have a *dev here to use
>>> dev_err(). Besides this, I guess it looks fine.
>>>
>>
>> I knew the rule, but I mistook the code...
>> I will fix it. And I also use dev_err() instead of printk().
>
> it might also be wise to add a patch, before this one, converting
> printk() to dev_* macros, I guess ;-)
>
I think so. :)
I wrote such patch and I will submit it soon.
Best regards,
Yoshihiro Shimoda
prev parent reply other threads:[~2011-09-30 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 8:43 [PATCH 2/2] usb: r8a66597-udc: add support for SUDMAC Yoshihiro Shimoda
2011-09-30 8:17 ` Felipe Balbi
2011-09-30 9:49 ` Yoshihiro Shimoda
2011-09-30 9:55 ` Felipe Balbi
2011-09-30 10:48 ` Yoshihiro Shimoda [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=4E859E7E.1070800@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=linux-sh@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