From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936455AbdJQPgA (ORCPT ); Tue, 17 Oct 2017 11:36:00 -0400 Received: from cloudserver094114.home.net.pl ([79.96.170.134]:58278 "EHLO cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932642AbdJQPf5 (ORCPT ); Tue, 17 Oct 2017 11:35:57 -0400 From: "Rafael J. Wysocki" To: Greg Kroah-Hartman Cc: Linux PM , Bjorn Helgaas , Alan Stern , LKML , Linux ACPI , Linux PCI , Linux Documentation , Mika Westerberg , Ulf Hansson , Andy Shevchenko , Kevin Hilman , Wolfram Sang , linux-i2c@vger.kernel.org, Lee Jones Subject: Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags Date: Tue, 17 Oct 2017 17:26:20 +0200 Message-ID: <79398495.qfC5mmSRrG@aspire.rjw.lan> In-Reply-To: <20171017071543.GB27293@kroah.com> References: <3806130.B2KCK0tvef@aspire.rjw.lan> <6007227.iNoRbQyInB@aspire.rjw.lan> <20171017071543.GB27293@kroah.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, October 17, 2017 9:15:43 AM CEST Greg Kroah-Hartman wrote: > On Tue, Oct 17, 2017 at 12:05:11AM +0200, Rafael J. Wysocki wrote: > > On Monday, October 16, 2017 8:28:52 AM CEST Greg Kroah-Hartman wrote: > > > On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > > > > struct dev_pm_info { > > > > pm_message_t power_state; > > > > unsigned int can_wakeup:1; > > > > @@ -561,6 +580,7 @@ struct dev_pm_info { > > > > bool is_late_suspended:1; > > > > bool early_init:1; /* Owned by the PM core */ > > > > bool direct_complete:1; /* Owned by the PM core */ > > > > + unsigned int driver_flags; > > > > > > Minor nit, u32 or u64? > > > > u32 I think, will update. > > > > BTW, there's a mess in this struct overall and I'd like all of the bit fileds > > to be the same type (and that shouldn't be bool IMO :-)). > > > > Do you prefer u32 or unsinged int? > > I always prefer an explicit size for variables, unless it's a "generic > loop" type thing. So I'll always say "u32" for this. > > And cleaning up the structure would be great, it's grown over time in > odd ways as you point out. OK, but that will be separate from this work. Thanks, Rafael