From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: Remove mach-msm: some leftovers
Date: Tue, 07 Apr 2015 15:57:29 -0700 [thread overview]
Message-ID: <552460D9.5000807@codeaurora.org> (raw)
In-Reply-To: <CAD3Xx4J46RkKMPWQ_m0hqxDfR0bS=+8AiE+2h0MAXcTNbaLZtw@mail.gmail.com>
On 04/07/15 07:12, Valentin Rothberg wrote:
> On Tue, Apr 7, 2015 at 4:07 PM, Valentin Rothberg
> <valentinrothberg@gmail.com> wrote:
>> Hi Stephen,
>>
>> your commit c0c89fafa289 ("ARM: Remove mach-msm and associated ARM
>> architecture code") removes config ARCH_MSM from Kconfig but leaves a
>> few references untouched:
>>
>> arch/arm/Kconfig.debug:1563: default "debug/uncompress.h" if
>> ARCH_MULTIPLATFORM || ARCH_MSM || \
>> drivers/phy/Kconfig:289: depends on OF && ARCH_MSM
>> drivers/scsi/ufs/Kconfig:76: depends on SCSI_UFSHCD_PLATFORM && ARCH_MSM
>> drivers/video/fbdev/Kconfig:2331: depends on FB && ARCH_MSM
>>
>> Is there a reason to keep those leftovers or is it an accident?
>>
>> I detected this issues with ./scripts/checkkconfigsymbols.py by
>> comparing today's and the previous linux-next tree (--diff
>> commit1..commit2).
>>
>> Kind regards,
>> Valentin
> Same issue applies to the Kconfig option MSM_SMD:
>
> drivers/char/Kconfig:596: depends on MSM_SMD
> drivers/tty/serial/Kconfig:1384: depends on MSM_SMD
I'm currently waiting on the maintainers of said subsystems to apply the
patches that I've already sent to the list. I can resend the series
minus the patches that have already been picked up, but I can't do much
more than that.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-04-07 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 14:07 ARM: Remove mach-msm: some leftovers Valentin Rothberg
2015-04-07 14:12 ` Valentin Rothberg
2015-04-07 22:57 ` Stephen Boyd [this message]
2015-04-27 6:37 ` Valentin Rothberg
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=552460D9.5000807@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).