From: Frank Rowand <frowand.list@gmail.com>
To: "Bird, Timothy" <Tim.Bird@sony.com>,
"monstr@monstr.eu" <monstr@monstr.eu>,
"fuego@lists.linuxfoundation.org"
<fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] [PATCH v2] sercp: Add support for full device paths
Date: Thu, 13 Apr 2017 16:43:57 -0700 [thread overview]
Message-ID: <58F00D3D.8040201@gmail.com> (raw)
In-Reply-To: <58F00A5B.7050700@gmail.com>
On 04/13/17 16:31, Frank Rowand wrote:
> On 04/13/17 15:47, Bird, Timothy wrote:
>> Add a new argument (-d, --device) to support a full device path.
>> Due to file argument parsing constraints, sercp cannot handle
>> certain serial paths used as the host for the source or destination.
>>
>> This feature makes it possible to use a full path, with slashes and
>> colons, to specify the serial port for the operation. Use something
>> like:
>> $ sercp -d /dev/serial/by-path/pci-0000:08:00-usb-0:3:1.4 file1 serial:/tmp
>>
>> The reason for this is that in some cases, using the full path is more
>> convenient than the single-word device. For example, the full path can
>> uniquely identify a serial port on a USB port, that might change device
>> names as USB ports are connected and disconnected.
>>
>> Signed-off-by: Tim Bird <tim.bird@sony.com>
>> ---
>> serio | 30 ++++++++++++++++++++++--------
>> 1 file changed, 22 insertions(+), 8 deletions(-)
>
> < snip >
>
> Accepted.
>
> I am assuming you have tested and will apply without further test
> given your time contraints.
>
> -Frank
>
>
And commit pushed, with an added commit to update the version.
-Frank
next prev parent reply other threads:[~2017-04-13 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 22:47 [Fuego] [PATCH v2] sercp: Add support for full device paths Bird, Timothy
2017-04-13 23:31 ` Frank Rowand
2017-04-13 23:43 ` Frank Rowand [this message]
2017-04-14 0:48 ` Bird, Timothy
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=58F00D3D.8040201@gmail.com \
--to=frowand.list@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=fuego@lists.linuxfoundation.org \
--cc=monstr@monstr.eu \
/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.