From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 30CFCC432C3 for ; Fri, 22 Nov 2019 12:10:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EBF1B20679 for ; Fri, 22 Nov 2019 12:10:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=mork.no header.i=@mork.no header.b="gqK/ajgL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727573AbfKVMKN (ORCPT ); Fri, 22 Nov 2019 07:10:13 -0500 Received: from canardo.mork.no ([148.122.252.1]:40595 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726686AbfKVMKM (ORCPT ); Fri, 22 Nov 2019 07:10:12 -0500 Received: from miraculix.mork.no ([IPv6:2a02:2121:282:b3eb:68e2:39ff:fe1c:1a78]) (authenticated bits=0) by canardo.mork.no (8.15.2/8.15.2) with ESMTPSA id xAMCA2ZK024257 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 22 Nov 2019 13:10:02 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mork.no; s=b; t=1574424603; bh=Zn0KvcZXnPXpBNWH0DiuFbkAHELGuxXUH0gZ2EV4wlM=; h=From:To:Cc:Subject:References:Date:Message-ID:From; b=gqK/ajgLoia9egUwprnScsd5Klkvud9SAB+eXZlaxsx++nPBixAPhBQQIT1Rt83Jg 12BtRA8K/9bxJILLYRUjpDerUTrPizjTRk6yDb88bl5QFGxkfpPvcVf00ImZSbDLkv /a6YsoHa+mR60aGEu/lOkMvhHkVl/nGiwD13J60o= Received: from bjorn by miraculix.mork.no with local (Exim 4.92) (envelope-from ) id 1iY7l6-00073r-PT; Fri, 22 Nov 2019 13:09:56 +0100 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: Yongxin Liu Cc: , , , , Subject: Re: [PATCH] Revert "platform/x86: wmi: Destroy on cleanup rather than unregister" Organization: m References: <20191115052710.46880-1-yongxin.liu@windriver.com> <87blt45eew.fsf@miraculix.mork.no> Date: Fri, 22 Nov 2019 13:09:56 +0100 In-Reply-To: <87blt45eew.fsf@miraculix.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork"'s message of "Fri, 22 Nov 2019 12:38:47 +0100") Message-ID: <8736eg5cyz.fsf@miraculix.mork.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: clamav-milter 0.101.4 at canardo X-Virus-Status: Clean Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bj=C3=B8rn Mork writes: > Maybe we should add a WARN_ON(!MAJOR(devt)) or similar to > device_destroy() to prevent similar future problems? No, that's definitely not a good idea. We have examples like drivers/tty/vt/vt.c which (ab)use the devt with zero major and a unique minor to keep track of devices. So forget about any warning. But the device_destroy's with a static MKDEV(0,0) should be removed. Bj=C3=B8rn