[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190427061856.GA675@ubu>
Date: Sat, 27 Apr 2019 02:18:56 -0400
From: Kimberly Brown <kimbrownkd@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/8] kobject: Add default group support to kobj_type
and replace subsystem uses
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
Powered by blists - more mailing lists