linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-serial@vger.kernel.org
Subject: Re: RFC: out-of-tree tty driver breakage (changing ASYNC_ bits)
Date: Mon, 11 Jan 2016 15:53:20 +0000 (UTC)	[thread overview]
Message-ID: <n70j5g$sem$1@ger.gmane.org> (raw)
In-Reply-To: 20160111044204.GB12741@kroah.com

On 2016-01-11, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Jan 10, 2016 at 01:42:44PM -0800, Peter Hurley wrote:
>
>> This will break out-of-tree drivers but I don't really see a
>> realistic alternative. Also, I think the new symbol prefix ASY_ isn't
>> great and I'd like to get some suggestions.
>
> Don't worry about breaking out-of-tree drivers, that's fine.

One request from this maintainer of several out-of-tree drivers: if
you break something, break it such that it won't compile.  It would be
nice to avoid changes that break functionality but still compile
without warning.

-- 
Grant Edwards               grant.b.edwards        Yow! Where do your SOCKS
                                  at               go when you lose them in
                              gmail.com            th' WASHER?

  parent reply	other threads:[~2016-01-11 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 21:42 RFC: out-of-tree tty driver breakage (changing ASYNC_ bits) Peter Hurley
2016-01-10 23:44 ` One Thousand Gnomes
2016-01-11  0:36   ` Peter Hurley
2016-01-11  4:42 ` Greg KH
2016-01-11  5:16   ` Peter Hurley
2016-01-11 15:53   ` Grant Edwards [this message]
2016-01-11 16:24     ` Peter Hurley
2016-06-28 15:39       ` Grant Edwards
2016-06-28 15:54         ` Grant Edwards
2016-06-28 16:05           ` Grant Edwards

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='n70j5g$sem$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.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 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).