From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933288AbcAKPxm (ORCPT ); Mon, 11 Jan 2016 10:53:42 -0500 Received: from plane.gmane.org ([80.91.229.3]:38136 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbcAKPxl (ORCPT ); Mon, 11 Jan 2016 10:53:41 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Grant Edwards Subject: Re: RFC: out-of-tree tty driver breakage (changing ASYNC_ bits) Date: Mon, 11 Jan 2016 15:53:20 +0000 (UTC) Message-ID: References: <5692D054.7050203@hurleysoftware.com> <20160111044204.GB12741@kroah.com> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67-130-15-94.dia.static.qwest.net User-Agent: slrn/1.0.2 (Linux) Cc: linux-serial@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016-01-11, Greg KH 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?