From: Johan Hovold <johan@kernel.org>
To: Konstantin Shkolnyy <Konstantin.Shkolnyy@silabs.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
"'Konstantin Shkolnyy'" <konstantin.shkolnyy@gmail.com>,
"johan@kernel.org" <johan@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] RE: [PATCH v2 2/3] USB: serial: cp210x: Added comments to CRTSCTS flag code.
Date: Tue, 3 May 2016 14:21:07 +0200 [thread overview]
Message-ID: <20160503122107.GN25025@localhost> (raw)
In-Reply-To: <BLUPR0701MB157275E6D876467DFAE93029917A0@BLUPR0701MB1572.namprd07.prod.outlook.com>
On Tue, May 03, 2016 at 12:11:53PM +0000, Konstantin Shkolnyy wrote:
> > -----Original Message-----
> > From: linux-usb-owner@vger.kernel.org [mailto:linux-usb-
> > owner@vger.kernel.org] On Behalf Of David Laight
> > Sent: Tuesday, May 03, 2016 04:44
> > To: 'Konstantin Shkolnyy'; johan@kernel.org
> > Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: [EXT] RE: [PATCH v2 2/3] USB: serial: cp210x: Added comments to
> > CRTSCTS flag code.
> >
> > From: Konstantin Shkolnyy
> > > Sent: 30 April 2016 03:22
> > > Replaced magic numbers used in the CRTSCTS flag code with symbolic
> > names
> > > from the chip specification.
> > >
> > > Signed-off-by: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
> > > ---
> > > Changes in v2:
> > > Improved CRTSCTS fix based on feedback. Dropped get_termios error
> > handling.
> > >
> > > drivers/usb/serial/cp210x.c | 93
> > +++++++++++++++++++++++++++++++++------------
> > > 1 file changed, 69 insertions(+), 24 deletions(-)
> > >
> > > diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
> > ...
> > > +/* cp210x_flow_ctl::ulControlHandshake */
> > > +#define SERIAL_DTR_MASK 0x00000003
> > > +#define SERIAL_CTS_HANDSHAKE 0x00000008
> > > +#define SERIAL_DSR_HANDSHAKE 0x00000010
> > > +#define SERIAL_DCD_HANDSHAKE 0x00000020
> > > +#define SERIAL_DSR_SENSITIVITY 0x00000040
> > ...
> >
> > I'd have thought the names ought to start CP210X_
>
> These names are inherited from the Labs chip spec.
Yes, but it's still a good idea to add a CP210X_ prefix to avoid any
confusion with the serial-core defines.
Thanks,
Johan
prev parent reply other threads:[~2016-05-03 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 2:22 [PATCH v2 2/3] USB: serial: cp210x: Added comments to CRTSCTS flag code Konstantin Shkolnyy
2016-05-03 9:44 ` David Laight
2016-05-03 12:11 ` [EXT] " Konstantin Shkolnyy
2016-05-03 12:21 ` Johan Hovold [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=20160503122107.GN25025@localhost \
--to=johan@kernel.org \
--cc=David.Laight@ACULAB.COM \
--cc=Konstantin.Shkolnyy@silabs.com \
--cc=konstantin.shkolnyy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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