[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190722182451.GB24412@kroah.com>
Date: Mon, 22 Jul 2019 20:24:51 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Ravi Chandra Sadineni <ravisadineni@...omium.org>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
x86@...nel.org, rjw@...ysocki.net, pavel@....cz,
len.brown@...el.com, bhe@...hat.com, dyoung@...hat.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
tbroch@...omium.org
Subject: Re: [PATCH] power: sysfs: Remove wakeup_abort_count attribute.
On Mon, Jul 22, 2019 at 10:04:07AM -0700, Ravi Chandra Sadineni wrote:
> wakeup_abort_count and wakeup_count sysfs entries print the
> same (wakeup_count) attribute. This patch removes the duplicate
> wakeup_abort_count sysfs entry.
>
> Signed-off-by: Ravi Chandra Sadineni <ravisadineni@...omium.org>
> ---
> Documentation/ABI/testing/sysfs-devices-power | 25 ++++++-------------
> drivers/base/power/sysfs.c | 19 --------------
> 2 files changed, 7 insertions(+), 37 deletions(-)
Isn't this the attribute you add back in a later patch?
If you have 2 patches that touch the same file, always make a patch
series so we have a chance to guess as to what patch comes first.
thanks,
greg k-h
Powered by blists - more mailing lists