Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762182Ab2FHXi0 (ORCPT ); Fri, 8 Jun 2012 19:38:26 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:48954 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761856Ab2FHXiL (ORCPT ); Fri, 8 Jun 2012 19:38:11 -0400 MIME-Version: 1.0 In-Reply-To: <1339196027_596874@CP5-2952> References: <1339193608_596134@CP5-2952> <1339196027_596874@CP5-2952> From: Linus Torvalds Date: Fri, 8 Jun 2012 16:37:49 -0700 X-Google-Sender-Auth: _QzpA6EWLpMXYspNzpt2so1uvJ8 Message-ID: Subject: Re: [git pull] drm intel + exynos fixes To: Chris Wilson Cc: Dave Airlie , Daniel Vetter , DRI mailing list , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 22 On Fri, Jun 8, 2012 at 3:52 PM, Chris Wilson wrote: > > And that was my point. You were blaming the patch for making you aware > of existing behaviour that results in utter confusion, for as Alex > points out there is no sane way for userspace to handle the unknown > connection status from the detection routine. Ahh. Yes, then I agree with you. The current behavior is clearly insane in the presense of an unknown connector status. So if the higher levels are eventually fixed to say "if one input is 'unknown' and another is 'connected', we'll assume 'unknown' means 'not connected'", then we can re-apply that patch. As it is, it's apparently a disaster to reply 'unknown' in this situation. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/