From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: lenb@kernel.org, linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/5] acpi : remove index from acpi_processor_cx structure
Date: Fri, 13 Jul 2012 20:13:05 +0200 [thread overview]
Message-ID: <201207132013.05738.rjw@sisk.pl> (raw)
In-Reply-To: <4FFF4835.9030806@linaro.org>
On Thursday, July 12, 2012, Daniel Lezcano wrote:
> On 07/12/2012 11:44 PM, Rafael J. Wysocki wrote:
> > On Thursday, July 12, 2012, Daniel Lezcano wrote:
> >> Remove the index field. It could be given without adding extra
> >> information in the cx structure.
> >>
> >> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> >
> > I'm not sure about this one.
> >
> > The code seems to be more straightforward without it, actually.
> >
> > Why exactly do you need to remove the field?
>
> Actually, I am trying to cleaning up the different structure in the acpi
> and clearly separate what is for cpuidle and what is for acpi.
>
> I noticed there are some duplicated informations like the index and what
> is described in the cx state.
>
> I am trying to consolidate the code of the cpuidle drivers across the
> different platform and I have to admit the processor_idle is the most
> complicated as the cpuidle code is spreaded across different files
> (processor_driver.c, processor.h, arch/x86/kernel/acpi/cstate.c, etc
> ...). So these small patches are to litlle by little separate these two
> subsystems (acpi and cpuidle) and have everything related to cpuidle
> into the processor_idle file.
>
> For this patch, it is right it seems to introduce more complexity but
> the objective is to consolidate the code. I hope by cleaning the
> different structures we will gain in readability.
OK, I'm generally fine with that, but I'd prefer to defer this kind of
changes to 3.7 so as to avoid rushing them in.
Removing unused fields is entirely fine at this point, I don't see how
someone may see that objectionable, but let's just avoid playing with fields
that are used for now.
Thanks,
Rafael
next prev parent reply other threads:[~2012-07-13 18:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 21:03 [PATCH 1/5] acpi : remove latency_ticks from acpi_processor_cx structure Daniel Lezcano
2012-07-12 21:03 ` [PATCH 2/5] acpi : remove index " Daniel Lezcano
2012-07-12 21:44 ` Rafael J. Wysocki
2012-07-12 21:57 ` Daniel Lezcano
2012-07-13 18:13 ` Rafael J. Wysocki [this message]
2012-07-17 20:32 ` Rafael J. Wysocki
2012-07-17 20:34 ` Rafael J. Wysocki
2012-07-12 21:03 ` [PATCH 3/5] acpi : remove usage " Daniel Lezcano
2012-07-12 21:45 ` Rafael J. Wysocki
2012-07-17 20:35 ` Rafael J. Wysocki
2012-07-12 21:03 ` [PATCH 4/5] acpi : remove power " Daniel Lezcano
2012-07-12 21:45 ` Rafael J. Wysocki
2012-07-13 0:17 ` Konrad Rzeszutek Wilk
2012-07-13 7:36 ` Daniel Lezcano
2012-07-13 12:23 ` Daniel Lezcano
2012-07-13 18:14 ` Rafael J. Wysocki
2012-07-16 15:23 ` Konrad Rzeszutek Wilk
2012-07-12 21:03 ` [PATCH 5/5] acpi : remove time " Daniel Lezcano
2012-07-12 21:46 ` Rafael J. Wysocki
2012-07-17 20:35 ` Rafael J. Wysocki
2012-07-12 21:40 ` [PATCH 1/5] acpi : remove latency_ticks " Rafael J. Wysocki
2012-07-17 20:32 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201207132013.05738.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=daniel.lezcano@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).