Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 02:33:46PM -0800, Rajat Jain wrote: > On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman > wrote: > > On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: > >> If the only remaining reference to a parent, is the one taken by > >> the child (in

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

[Fixed the linux-pci mailing list address] On Mon, Dec 14, 2015 at 2:33 PM, Rajat Jain wrote: > On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman > wrote: >> On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: >>> If the only remaining reference to a parent, is the one taken by >>>

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman wrote: > On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: >> If the only remaining reference to a parent, is the one taken by >> the child (in kobject_add_internal()), then when the last >> reference to the child goes away, both child

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: > If the only remaining reference to a parent, is the one taken by > the child (in kobject_add_internal()), then when the last > reference to the child goes away, both child and its parents > shall be released. However, currently the

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: > If the only remaining reference to a parent, is the one taken by > the child (in kobject_add_internal()), then when the last > reference to the child goes away, both child and its parents > shall be released. However, currently the

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

[PATCH] kobject: Ensure child's resources get released before parent's resources

If the only remaining reference to a parent, is the one taken by the child (in kobject_add_internal()), then when the last reference to the child goes away, both child and its parents shall be released. However, currently the resources of parent get released first, followed by the child's

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

[Fixed the linux-pci mailing list address] On Mon, Dec 14, 2015 at 2:33 PM, Rajat Jain wrote: > On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman > wrote: >> On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: >>> If the only remaining

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman wrote: > On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: >> If the only remaining reference to a parent, is the one taken by >> the child (in kobject_add_internal()), then when the last >> reference to the

Re: [PATCH] kobject: Ensure child's resources get released before parent's resources

On Mon, Dec 14, 2015 at 02:33:46PM -0800, Rajat Jain wrote: > On Mon, Dec 14, 2015 at 1:40 PM, Greg Kroah-Hartman > wrote: > > On Mon, Dec 14, 2015 at 11:02:46AM -0800, Rajat Jain wrote: > >> If the only remaining reference to a parent, is the one taken by > >> the