All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mychaela Falconia <mychaela.falconia@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/6] serial ports: add ability to suppress raising DTR & RTS on open
Date: Mon, 30 May 2022 18:23:25 +0200	[thread overview]
Message-ID: <YpTvffJRWK19ZtW+@kroah.com> (raw)
In-Reply-To: <CA+uuBqbAz0SL88HTsg1m-80i9eHS7EjnRyrKE=GWrXA7u1GB_A@mail.gmail.com>

On Mon, May 30, 2022 at 08:05:00AM -0800, Mychaela Falconia wrote:
> Greg K-H wrote:
> 
> > To ignore the public, accepted, standard is to become an operating
> > system that does not follow the standard, which would not be a good
> > thing at all.
> 
> So is FreeBSD 13.x a bad OS then, because it offers an *option* of
> suppressing this particular standard-mandated behaviour?

I never said that, please do not be disengenous, that will only get you
added to people's email filters to be ignored.

> > Again, that is the standard, why wouldn't you want to do that?  To not
> > do that would be to break interoperability with millions of devices out
> > there (remember modems?)
> 
> I don't need to "remember" modems, I use them almost every day in my
> test lab - but none of my proposed patch versions (nor FreeBSD's recent
> CNO_RTSDTR feature addition) break interoperability with anything,
> instead both FreeBSD's solution (for their OS) and my proposed Linux
> patches merely provide an *option* for more specialized hw devices
> that require different handling.

That's fine, but again, you were ranting against the existing standard
as if that was the thing that is wrong and broken here.  Not your
one-off hardware implementation that does not follow the existing
standard.  Please read the context you cut out.

> > > The solution implemented in FreeBSD relies on a feature of that OS
> > > which does not exist in Linux: initial-state devices.
> >
> > Linux dropped those a long time ago for good reasons, let's not revisit
> > that design decision again please.
> 
> Dropped?  Are you saying that Linux once had them at some point in the
> past?

Yes we had much the same thing, but they might have worked a bit
differently.  Check the 2.2 kernel days or earlier.

> > From what I recall with the original patch series, Johan is the author
> > of these, not you.  Rebasing and forwarding on is great, but please
> > never drop original authorship of patches, that's just rude, and in
> > some cases, ripe for legal worries.
> 
> In the case of the 3 patches which originate from Johan (1/6, 2/6 and
> 4/6), I submitted them with the following attribution:
> 
> From: me
> [...]
> Co-developed-by: Johan
> Signed-off-by: Johan
> Signed-off-by: me
> 
> My reading of Documentation/process/submitting-patches.rst told me
> this was the correct protocol - but if I got it wrong, what is the
> correct way then?  Specifically, what is the correct protocol when
> (in this chronological order):

"From:" would be from Johan as he wrote the commit.

thanks,

greg k-h

      reply	other threads:[~2022-05-30 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 22:27 [PATCH 0/6] serial ports: add ability to suppress raising DTR & RTS on open Mychaela N. Falconia
2022-05-30 13:26 ` Greg Kroah-Hartman
2022-05-30 16:05   ` Mychaela Falconia
2022-05-30 16:23     ` Greg Kroah-Hartman [this message]

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=YpTvffJRWK19ZtW+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mychaela.falconia@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 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.