From: Timur Tabi <timur@codeaurora.org>
To: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Cc: Prashanth Prakash <pprakash@codeaurora.org>,
linux acpi <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linaro ACPI Mailman List <linaro-acpi@lists.linaro.org>
Subject: Re: [Linaro-acpi] [PATCH V2 1/4] ACPI / CPPC: Optimize PCC Read Write operations
Date: Mon, 25 Jan 2016 14:48:03 -0600 [thread overview]
Message-ID: <56A68A03.4090101@codeaurora.org> (raw)
In-Reply-To: <CAJ5Y-eZ5w7o2GFaqn8M3JciCQi5OPDJ8THfQGN9JijQi0H-qNw@mail.gmail.com>
Ashwin Chaugule wrote:
> Prashanth has been doing the right thing all along. I was CC'd on all
> his patchwork, but you changed it (and removed me) while replying.
I did not remove your CC:.
I can't explain it, but the patch "[Linaro-acpi] [PATCH V2 1/4] ACPI /
CPPC: Optimize PCC Read Write operations" in my inbox does not list you
on the CC: This is what the header says:
From: Prashanth Prakash <pprakash@codeaurora.org>
To: rjw@rjwysocki.net
Date: Fri, 22 Jan 2016 18:07:17 -0700
Message-Id: <1453511240-20792-2-git-send-email-pprakash@codeaurora.org>
X-Mailer: git-send-email 1.8.2.1
In-Reply-To: <1453511240-20792-1-git-send-email-pprakash@codeaurora.org>
References: <1453511240-20792-1-git-send-email-pprakash@codeaurora.org>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: linux-acpi@vger.kernel.org, Prashanth Prakash <pprakash@codeaurora.org>,
linaro-acpi@lists.linaro.org
Subject: [Linaro-acpi] [PATCH V2 1/4] ACPI / CPPC: Optimize PCC Read Write
operations
X-BeenThere: linaro-acpi@lists.linaro.org
When I look at the spinics.net archive, I see you are on it:
http://www.spinics.net/lists/linux-acpi/msg63274.html
I do not understand why my email does not have your CC: on it.
> Unless Rafael thinks otherwise, I see no major issues in V2, so there
> is no need for a respin.
I think stripping away the __iomem is wrong. The whole point behind the
'sparse' tool is to catch invalid accesses to I/O memory. When you
typecast it away, then prevent sparse from catching those problem.
next prev parent reply other threads:[~2016-01-25 20:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 1:07 [PATCH V2 0/4] acpi: cppc optimization patches Prashanth Prakash
2016-01-23 1:07 ` [PATCH V2 1/4] ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash
2016-01-25 17:19 ` [Linaro-acpi] " Timur Tabi
2016-01-25 20:26 ` Ashwin Chaugule
2016-01-25 20:48 ` Timur Tabi [this message]
2016-01-26 16:41 ` Prakash, Prashanth
2016-02-01 19:38 ` Alexey Klimov
2016-02-01 21:06 ` Prakash, Prashanth
2016-01-23 1:07 ` [PATCH V2 2/4] acpi: cppc: optimized cpc_read and cpc_write Prashanth Prakash
2016-01-25 17:22 ` [Linaro-acpi] " Timur Tabi
2016-01-23 1:07 ` [PATCH V2 3/4] mailbox: pcc: optimized pcc_send_data Prashanth Prakash
2016-01-25 17:34 ` [Linaro-acpi] " Timur Tabi
2016-01-25 18:26 ` Ashwin Chaugule
2016-01-25 18:52 ` Timur Tabi
2016-01-23 1:07 ` [PATCH V2 4/4] acpi: cppc: replace writeX/readX to PCC with relaxed version Prashanth Prakash
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=56A68A03.4090101@codeaurora.org \
--to=timur@codeaurora.org \
--cc=ashwin.chaugule@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--cc=rjw@rjwysocki.net \
/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).