linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH] slcan2d: add new slcan daemon
Date: Wed, 21 Aug 2013 19:46:36 +0200	[thread overview]
Message-ID: <5214FCFC.3070404@hartkopp.net> (raw)
In-Reply-To: <CAGm1_ksLBm-uS9SiOx+cPHim0CLM6Zg65t4am-=kL_7qgH5-6Q@mail.gmail.com>

On 17.08.2013 21:01, Yegor Yefremov wrote:
> On Wed, Jul 24, 2013 at 2:01 PM, Yegor Yefremov
> <yegorslists@googlemail.com> wrote:
>> Hi Marc, Oliver,
>>
>> On Thu, Jul 11, 2013 at 11:54 AM,  <yegorslists@googlemail.com> wrote:
>>> From: Yegor Yefremov <yegorslists@googlemail.com>
>>>
>>> Cleaned up version of Oliver Hartkopp's effort with addition of
>>> UART speed configuration.
>>>
>>> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
>>
>> any comments/suggestions?
> 
> ping
> 

Hi Yegor,

sorry for my delayed response.

I just got through your slcan2d by diffing it with the existing slcand.

It's a cool cleanup and it adds all relevant command line options we know from
slcan_attach.c & UART settings - i think that was the idea, right?

As i can see there's no change of the functionality when the 'optional
options' are not given on the command line.

So why don't you just post a patch which makes the slcand your 'slcan2d' code?

IMHO having both the slcand and the slcan2d in the same repository does not
make sense if they behave identical when having the same (empty) options.

Or did I miss anything that slcand <tty> behaves different to slcan2d <tty> ??

Thanks & BR,
Oliver


  reply	other threads:[~2013-08-21 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  9:54 [PATCH] slcan2d: add new slcan daemon yegorslists
2013-07-24 12:01 ` Yegor Yefremov
2013-08-17 19:01   ` Yegor Yefremov
2013-08-21 17:46     ` Oliver Hartkopp [this message]
2013-08-22  7:12       ` Yegor Yefremov

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=5214FCFC.3070404@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=yegorslists@googlemail.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).