From: Johan Hovold <johan@kernel.org>
To: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: cp210x: Adding tx_empty() to avoid cp2108 failure
Date: Fri, 16 Oct 2015 14:39:48 +0200 [thread overview]
Message-ID: <20151016123948.GB30216@localhost> (raw)
In-Reply-To: <CAL_jEz9K9Rn+jFTUC541xBhfQB=kggtkqhq+rcihG_z3zVC_Kg@mail.gmail.com>
On Fri, Oct 16, 2015 at 07:35:02AM -0500, Konstantin Shkolnyy wrote:
> Hello,
>
> On Fri, Oct 16, 2015 at 6:19 AM, Sergei Shtylyov
> <sergei.shtylyov@cogentembedded.com> wrote:
> [...]
> >>
> >> @@ -249,6 +251,16 @@ static struct usb_serial_driver * const
> >> serial_drivers[] = {
> >> #define CP210X_GET_CHARS 0x0E
> >> #define CP210X_GET_PROPS 0x0F
> >> #define CP210X_GET_COMM_STATUS 0x10
> >> +/* Data returned by CP210X_GET_COMM_STATUS -- h/w doc says it's 0x13
> >> bytes */
> >> +struct cp210x_comm_status {
> >> + u32 errors;
> >> + u32 hold_reasons;
> >> + u32 amount_in_in_queue;
> >> + u32 amount_in_out_queue;
> >> + u8 eof_received;
> >> + u8 wait_for_immediate;
> >> + u8 reserved;
> >> +};
> >
> >
> > Please don't declare structures amidst of the command #define's.
> >
> [...]
>
> I agree with all suggestions except this one. I find it very
> convenient, when reading code, to have the command code and its data
> declared in the same place.
No, I agree with Sergei on this. Please place the struct after the
request defines (just like the various request values after are defined
after the request list).
I'll try to provide some more feedback on your patches shortly. Sorry
for the delay.
Johan
next prev parent reply other threads:[~2015-10-16 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 22:07 [PATCH] USB: serial: cp210x: Adding tx_empty() to avoid cp2108 failure Konstantin Shkolnyy
2015-10-16 11:19 ` Sergei Shtylyov
2015-10-16 12:35 ` Konstantin Shkolnyy
2015-10-16 12:39 ` Johan Hovold [this message]
2015-10-16 12:55 ` Johan Hovold
2015-10-16 13:48 ` Konstantin Shkolnyy
2015-10-16 14:04 ` Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2015-10-07 23:38 Konstantin Shkolnyy
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=20151016123948.GB30216@localhost \
--to=johan@kernel.org \
--cc=konstantin.shkolnyy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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