linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Paul Schilling <paul.s.schilling@gmail.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	linux-serial@vger.kernel.org, Boojin Kim <boojin.kim@samsung.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>,
	linux-arm-kernel@lists.infradead.org,
	Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 02/14] ARM : SAMSUNG : Add RS485 support.
Date: Sun, 23 Oct 2011 21:20:08 +0100	[thread overview]
Message-ID: <20111023202008.GB27802@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAC=G6syuf-J4am1mHRg-5gzqy661yOT9pUK2vQyToLPtv4tvEg@mail.gmail.com>

On Sun, Oct 23, 2011 at 12:12:13PM -0500, Paul Schilling wrote:
> On Sat, Oct 22, 2011 at 8:47 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >> +             } else {
> >> +                     /* Set a short timer to toggle RTS */
> >> +                     mod_timer(
> >> +                                     &(ourport->rs485_tx_timer),
> >> +                                     jiffies + usecs_to_jiffies(
> >> +                                                     ourport->char_time_usec
> >> +                                                     / 10));
> >
> > This could do with being better formatted.  Also, & doesn't need following
> > parens.
> 
> when I ran checkpatch it complained that it exceeded 80 characters.  I
> had trouble keeping this line
> under 80 characters.

		} else {
			mod_timer(&our_port->rs485_tx_timer, jiffies +
				  usecs_to_jiffies(ourport->char_time_usec
						   / 10));

is probably a better way to format it.

> >> -             if (port->flags & UPF_CONS_FLOW)
> >> +             if (port->flags & UPF_CONS_FLOW) {
> >>                       s3c24xx_serial_rx_enable(port);
> >> +             }
> >
> > Why are you reformatting code?
> 
> I will remove the reformatting of the code.

If you wish to reformat the code to clean up checkpatch warnings, then that
needs to be a separate patch from any other changes.

  reply	other threads:[~2011-10-23 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <samsung_rs485>
2011-10-22  3:46 ` [PATCH 02/14] ARM : SAMSUNG : Add RS485 support Paul Schilling
2011-10-22 13:47   ` Russell King - ARM Linux
2011-10-23 17:12     ` Paul Schilling
2011-10-23 20:20       ` Russell King - ARM Linux [this message]
2011-11-01 12:18   ` Alan Cox
2011-11-01 14:57     ` Paul Schilling
2011-11-01 19:12       ` Paul Schilling
2011-11-01 19:22         ` Paul Schilling
2011-11-01 19:55           ` Alan Cox
2011-11-04 10:18   ` Nicolas Ferre

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=20111023202008.GB27802@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=alan@linux.intel.com \
    --cc=ben-linux@fluff.org \
    --cc=boojin.kim@samsung.com \
    --cc=gregkh@suse.de \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=paul.s.schilling@gmail.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;
as well as URLs for NNTP newsgroup(s).