From: claudio@evidence.eu.com (Claudio Scordino)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] atmel_serial: Atmel RS485 support
Date: Mon, 22 Mar 2010 12:15:25 +0100 [thread overview]
Message-ID: <4BA7514D.3020901@evidence.eu.com> (raw)
In-Reply-To: <4BA695E4.70105@bluewatersys.com>
Hi Ryan,
first of all, thank you for your feedback.
To me, all comments seem to be reasonable, except maybe the following one:
>>
>> +static void atmel_start_rx(struct uart_port *port);
>> +static void atmel_stop_rx(struct uart_port *port);
>
> Can you move these functions, so that these declarations are not needed?
Actually, atmel_stop_rx is already defined, and I prefer to not move it
(since I change it, people may get confused by the diff...).
I also think that atmel_start_rx (which is added by the patch) should be
near to atmel_stop_rx...
>> + UART_PUT_IDR(port, ATMEL_US_ENDRX | ATMEL_US_TIMEOUT |
>> port->read_status_mask);
>
> This line, and a couple of others, extend over 80 characters. Could you
> please split them up.
Of course. I'm going to split them up and use a backslash at the end of
the original lines.
I will create a new patch according to your comments, test it and submit
again to the mailing list.
Many thanks again,
Claudio
WARNING: multiple messages have this Message-ID (diff)
From: Claudio Scordino <claudio@evidence.eu.com>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Rick Bronson <rick@efn.org>, John Nicholls <john@thinlinx.com>,
Sebastian Heutling <Sebastian.Heutling@who-ing.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
michael trimarchi <michael@evidence.eu.com>,
alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] atmel_serial: Atmel RS485 support
Date: Mon, 22 Mar 2010 12:15:25 +0100 [thread overview]
Message-ID: <4BA7514D.3020901@evidence.eu.com> (raw)
In-Reply-To: <4BA695E4.70105@bluewatersys.com>
Hi Ryan,
first of all, thank you for your feedback.
To me, all comments seem to be reasonable, except maybe the following one:
>>
>> +static void atmel_start_rx(struct uart_port *port);
>> +static void atmel_stop_rx(struct uart_port *port);
>
> Can you move these functions, so that these declarations are not needed?
Actually, atmel_stop_rx is already defined, and I prefer to not move it
(since I change it, people may get confused by the diff...).
I also think that atmel_start_rx (which is added by the patch) should be
near to atmel_stop_rx...
>> + UART_PUT_IDR(port, ATMEL_US_ENDRX | ATMEL_US_TIMEOUT |
>> port->read_status_mask);
>
> This line, and a couple of others, extend over 80 characters. Could you
> please split them up.
Of course. I'm going to split them up and use a backslash at the end of
the original lines.
I will create a new patch according to your comments, test it and submit
again to the mailing list.
Many thanks again,
Claudio
next prev parent reply other threads:[~2010-03-22 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 8:28 [PATCH] atmel_serial: Atmel RS485 support Claudio Scordino
2010-03-19 8:28 ` Claudio Scordino
2010-03-21 20:15 ` Ryan Mallon
2010-03-21 20:15 ` Ryan Mallon
2010-03-21 21:55 ` Ryan Mallon
2010-03-21 21:55 ` Ryan Mallon
2010-03-22 11:15 ` Claudio Scordino [this message]
2010-03-22 11:15 ` Claudio Scordino
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=4BA7514D.3020901@evidence.eu.com \
--to=claudio@evidence.eu.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.