From: Randy Dunlap <rdunlap@xenotime.net>
To: james_p_freyensee@linux.intel.com
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
suhail.ahmed@intel.com, christophe.guerard@intel.com
Subject: Re: [PATCH 4/4] n_tracerouter and n_tracesink ldisc additions.
Date: Tue, 19 Apr 2011 17:14:33 -0700 [thread overview]
Message-ID: <20110419171433.05752a99.rdunlap@xenotime.net> (raw)
In-Reply-To: <1303257955.13457.37.camel@localhost>
On Tue, 19 Apr 2011 17:05:55 -0700 J Freyensee wrote:
> On Tue, 2011-04-19 at 16:20 -0700, Randy Dunlap wrote:
> > On Tue, 19 Apr 2011 15:58:09 -0700 james_p_freyensee@linux.intel.com wrote:
> >
> > > drivers/tty/Kconfig | 31 ++++++
> > > drivers/tty/Makefile | 2 +
> > > drivers/tty/n_tracerouter.c | 241 ++++++++++++++++++++++++++++++++++++++++++
> > > drivers/tty/n_tracesink.c | 244 +++++++++++++++++++++++++++++++++++++++++++
> > > drivers/tty/n_tracesink.h | 36 +++++++
> > > include/linux/tty.h | 2 +
> > > 6 files changed, 556 insertions(+), 0 deletions(-)
> > > create mode 100644 drivers/tty/n_tracerouter.c
> > > create mode 100644 drivers/tty/n_tracesink.c
> > > create mode 100644 drivers/tty/n_tracesink.h
> > >
> > > diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig
> > > index 3fd7199..d1ab9c0 100644
> > > --- a/drivers/tty/Kconfig
> > > +++ b/drivers/tty/Kconfig
> > > @@ -319,3 +319,34 @@ config N_GSM
> > > This line discipline provides support for the GSM MUX protocol and
> > > presents the mux as a set of 61 individual tty devices.
> > >
> > > +config TRACE_ROUTER
> > > + tristate "Trace data router for MIPI P1149.7 cJTAG standard"
> > > + depends on TRACE_SINK
> > > + default Y
> >
> > Don't add default Y misc drivers.
>
> This actually isn't a misc driver. From the help, it's "Linux tty line
> discipline"
>
> But I can turn it off.
OK, random drivers. Thanks.
> > > +/* Other ldisc drivers use 65536 which basically means,
> > > + * 'I can always accept 64k' and flow control is off.
> > > + * This number is deemed appropriate for this driver.
> > > + */
> >
> > Fix multi-line comment style throughout.
>
> Could you please show me how and what you are looking for? You pointed
> out a similar issue using a different comment style, despite that at
> least I made it a point to maintain a consistent comment style
> throughout the code in the file. So I'm not quite sure what is desired.
> Thanks, I appreciate this.
See Documentation/CodingStyle, section 8:
The preferred style for long (multi-line) comments is:
/*
* This is the preferred style for multi-line
* comments in the Linux kernel source code.
* Please use it consistently.
*
* Description: A column of asterisks on the left side,
* with beginning and ending almost-blank lines.
*/
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-20 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 22:58 james_p_freyensee
2011-04-19 23:20 ` Randy Dunlap
2011-04-20 0:05 ` J Freyensee
2011-04-20 0:14 ` Randy Dunlap [this message]
2011-04-22 23:32 james_p_freyensee
2011-04-24 1:04 ` Jesper Juhl
2011-04-24 1:51 ` Greg KH
2011-04-24 23:03 ` Jesper Juhl
2011-04-29 17:02 ` J Freyensee
2011-05-05 17:08 ` J Freyensee
2011-05-06 23:56 james_p_freyensee
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=20110419171433.05752a99.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=christophe.guerard@intel.com \
--cc=gregkh@suse.de \
--cc=james_p_freyensee@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suhail.ahmed@intel.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
all inboxes | Powered by JetHome®