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=-7.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,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 EF6D0C433E0 for ; Wed, 29 Jul 2020 15:01:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D05D0207E8 for ; Wed, 29 Jul 2020 15:01:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596034872; bh=ESM/C4n2/9SZm7+Qrh9WZ3Nyo1d10BOHwjAtSu+wytc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=nhmqAbsOEpbHabxJ94FAuMwwWerSZ9aPSZEq0Eh7gwNXeyutoETSRmlO4ojclDWgJ RE6wak7XJlrjFxEEaHNC0tIShJSncK3bLSPoDdU0N1ttpHchfo5beGPsXAQK7/Yeml yRkYXCxPjRKSJR6SlfiO4Mzr9f++3KXRd2cUcyTc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726502AbgG2PBK (ORCPT ); Wed, 29 Jul 2020 11:01:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:37772 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726054AbgG2PBJ (ORCPT ); Wed, 29 Jul 2020 11:01:09 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BF74E207E8; Wed, 29 Jul 2020 15:01:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1596034869; bh=ESM/C4n2/9SZm7+Qrh9WZ3Nyo1d10BOHwjAtSu+wytc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ikyk9lb/olM7+v7ejcklpKjX1TxtamqCPeSAIp0xtA7IAEt7QEM0UDxkzNNNzosw5 MCyBjrZyd2YJiyUU+L9hfpqZs5ckGC9TZlWwHF+E19ZIUB6GkdXNlCNzYrpWoB2/7e dLVnnd5jKRn8M2XhUaGgKUY4DCLzQD3Mik1d2VL0= Date: Wed, 29 Jul 2020 17:01:00 +0200 From: Greg Kroah-Hartman To: "Rafael J. Wysocki" Cc: Abhishek Pandit-Subedi , Rafael Wysocki , Linux PM , "open list:BLUETOOTH DRIVERS" , ChromeOS Bluetooth Upstreaming , Stephen Boyd , "Rafael J. Wysocki" , Linux Kernel Mailing List , Len Brown , Pavel Machek Subject: Re: [PATCH v5 1/1] power: Emit changed uevent on wakeup_sysfs_add/remove Message-ID: <20200729150100.GA3508555@kroah.com> References: <20200707172845.4177903-1-abhishekpandit@chromium.org> <20200707102823.v5.1.I51f5a0be89595b73c4dc17e6cf4cc6f26dc7f2fc@changeid> <20200723183235.GA3445384@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Mon, Jul 27, 2020 at 03:38:02PM +0200, Rafael J. Wysocki wrote: > On Thu, Jul 23, 2020 at 8:32 PM Greg Kroah-Hartman > wrote: > > > > On Tue, Jul 07, 2020 at 10:28:44AM -0700, Abhishek Pandit-Subedi wrote: > > > Udev rules that depend on the power/wakeup attribute don't get triggered > > > correctly if device_set_wakeup_capable is called after the device is > > > created. This can happen for several reasons (driver sets wakeup after > > > device is created, wakeup is changed on parent device, etc) and it seems > > > reasonable to emit a changed event when adding or removing attributes on > > > the device. > > > > > > Signed-off-by: Abhishek Pandit-Subedi > > > > Rafael, any objection to this? Do you want me to take it through my > > tree, or are you going to take it through yours? Either is fine for me. > > It's already there in my tree with the R-by tag from you. {sigh} Sorry for the noise. greg k-h