Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1460728yba; Fri, 26 Apr 2019 23:21:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqyCDvneLVbBK5CWXITmTRdOyAwEAvAQu99o6hDN+iMxDsFIiGIh9+Ddo7b2cZPboW6tB18I X-Received: by 2002:a17:902:86:: with SMTP id a6mr49754467pla.277.1556346061569; Fri, 26 Apr 2019 23:21:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556346061; cv=none; d=google.com; s=arc-20160816; b=Oy892Ni/ic9JR5PgJ0WQZz/G63dhOuDNUCB9SWSUTrP2mAVKmfb3KqxV1Vdqo1j+4J 6GkrklPP8Da6dF5MRG3oPectk5XHflteLoL0kFeTRKcR4I8+moKllemE/pvzPkZ0EArY 8oYiPIn5xEb2d0TpM6kubXM7nnR2KURgyhFMbk405wCxhax1R0emYfrrDyAJLAYMhiUQ 38I1vpJzWQaRIYnAsKXup0H3vqkW9EZOWzRsvuQqX5+oCMXnpn85GiVKZVKZ65HoU28W 1JiDHyvP0oKcIMGQ4zdRyyDa4//A7JoZUxPa21a0rOmuo2Thcjpa+1KhRZAIaN9qg1hx nZWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=AA/ZawmM0902rvXQ1ebDm2YuQrKe3V70foLmoIoE4Qo=; b=FRaxqQ2rOuX9U0YjR7bLpQdlRXroqTBcm1yovleV3zd3Vw9+y+9Ir9qAkn5yxyadVF XJAxY4fuZFd+mP2NxhTX6/g5dlHICvv4yrbLUNh/ivpb8+jYpJyfAwRZWyunxpvFPx53 n7veeyfizEn1PcKzKc3y481sQBy6hHzHOmtMBgW0MBrR+21ql1XAL/k9POcN7CYl5iN7 vqYxPDh6jUfNy8GFgUFz+tXqupdjQjHjTNFurSQQTXwETZgMBSv5GilaOvysVYt+gKN1 2jQ7XviuSsUBx9ufoUZEb1SURHFPM4NKxYTQruJxTm11/BnnHkPwJTKJqYrPD2Cyewie 98gA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PPO+ptpK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f16si26562567pgj.149.2019.04.26.23.20.46; Fri, 26 Apr 2019 23:21:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PPO+ptpK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726243AbfD0GTB (ORCPT + 99 others); Sat, 27 Apr 2019 02:19:01 -0400 Received: from mail-it1-f196.google.com ([209.85.166.196]:40884 "EHLO mail-it1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725966AbfD0GTA (ORCPT ); Sat, 27 Apr 2019 02:19:00 -0400 Received: by mail-it1-f196.google.com with SMTP id k64so1632740itb.5 for ; Fri, 26 Apr 2019 23:19:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=AA/ZawmM0902rvXQ1ebDm2YuQrKe3V70foLmoIoE4Qo=; b=PPO+ptpKPEIc/QKQQ8wbAvzTOsgYAKoKk8j57oAGbJSe5X0aDdzRMOk1342AY74flX ehkF7FkYN79mu1QAuCXXtk3QoylgzyxLlsp3wX/IJBEcRKxr2wJS2qpzXK4dfG/rEUxt st+O9EBVBRVCdZPXE2HklEvTAdOdW8GjZRUiUFy4WfkFnWlzVlWf8lWN453t7hrT9H5m 6FjiGqJ+0aI7gHI7n7bzKlvh63g87Njy0MnSdOgjykLCllHa1jiUuxpJb74qsnyM7Fc2 hGfZ2KyZ5uGgTXpDav5L6iLiKzPVNgXl0OjyTD2B/msRn7sw+wt0XicwvZyxmcmO7EaI vWCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=AA/ZawmM0902rvXQ1ebDm2YuQrKe3V70foLmoIoE4Qo=; b=GrelO+kdVpbc4CevRlH643K7j6pSkm5QOqw3UZdpHMsN7PbpyjAKbvTNiiqtZWK9ep Bl+9ayZw5J9M56YENt87VmKP3GCL6DpJwPFncReP7l/8iwmKj13YngPAlW3EMk/EdSIs zIeziwCICvD2F0UKNh5Y27bSBH6v77hBB7POQ3hej6FT/92JxVpGyWQVWt1dBYdvPj0X xhfVBT3JXbOX8fHGnD84nO3JxZ9AFVxVgXx397rtRN3p0AOKDzfen0MJU1FensFv5UR6 /d7bygu8qTeh4n1U3LmL871kiRrxTn4FPAvLRVbynR3F/ktksvqy78C1dCjHYvXpNlUf mhsg== X-Gm-Message-State: APjAAAXJZvioJZ70Pqwgqx3Va1mMYUTmchVpZP1MfXsKiDeXiTsyz8Zz viQXsz4sEMghzOQ/bE0UqaA= X-Received: by 2002:a24:b214:: with SMTP id u20mr3465165ite.134.1556345939834; Fri, 26 Apr 2019 23:18:59 -0700 (PDT) Received: from ubu (2600-6c48-437f-c81d-b1d9-7ff0-b1de-5362.dhcp6.chtrptr.net. [2600:6c48:437f:c81d:b1d9:7ff0:b1de:5362]) by smtp.gmail.com with ESMTPSA id o2sm1042061ioh.59.2019.04.26.23.18.58 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 26 Apr 2019 23:18:59 -0700 (PDT) Date: Sat, 27 Apr 2019 02:18:56 -0400 From: Kimberly Brown To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/8] kobject: Add default group support to kobj_type and replace subsystem uses Message-ID: <20190427061856.GA675@ubu> References: <20190322201440.GA30814@ubu-Virtual-Machine> <20190425201253.GA12131@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190425201253.GA12131@kroah.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 25, 2019 at 10:12:53PM +0200, Greg Kroah-Hartman wrote: > On Mon, Apr 01, 2019 at 10:51:10PM -0400, Kimberly Brown wrote: > > This patchset adds support for default attribute groups to kobj_type. > > Also, the uses of kobj_type's default_attrs field are replaced with > > default_groups in the following subsystems: > > - samples > > - block > > - net > > - irq > > - padata > > - cpufreq > > - livepatch > > > > The subsystem maintainers and lists will be copied on the subsystem > > patches. > > > > The uses of kobj_type's default_attrs field in the other subsystems will > > be replaced in future patchsets. > > Thanks for all of these, now queued up. Patches to fix up the other > subsystems are always welcome :) > > greg k-h Thanks, Greg! I'll start preparing more patches. I know that patches should be in linux-next for some time before the merge window opens. How long do they typically need to be in linux-next? I'm trying to figure out if the next patches I work on could be included in the next merge window, in which case I'll let the maintainers know that the patch will either need to go through the driver-core tree or wait for the next release cycle. Thanks, Kim