From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm: cti: fix build for cti.h
Date: Fri, 20 Feb 2015 19:37:03 +0000 [thread overview]
Message-ID: <20150220193702.GF1767@arm.com> (raw)
In-Reply-To: <1424326185-31463-1-git-send-email-dinguyen@opensource.altera.com>
On Thu, Feb 19, 2015 at 06:09:44AM +0000, dinguyen at opensource.altera.com wrote:
> I would to like check to see if this is right thing to do for cti.h. Our
> downstream kernel's PMU support is using cti.h. But I don't see any other
> upstream driver using cti.h, so I'm not sure if this file should be removed?
The file was originally added because there was some pending OMAP code to
make use of it. However, then the upstream OMAP development more or less
stopped and the follow-up patches never came.
I'd vote for removing the file if it's not used in mainline.
Will
prev parent reply other threads:[~2015-02-20 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 6:09 [RFC PATCH] arm: cti: fix build for cti.h dinguyen at opensource.altera.com
2015-02-19 6:09 ` [RFC PATCH] arm: cti: fix up cti pmu build dinguyen at opensource.altera.com
2015-02-20 19:37 ` Will Deacon [this message]
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=20150220193702.GF1767@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).