mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: nick <xerofoify@gmail.com>
Cc: Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] maibox:Remove unused functions in the file pcc.c
Date: Thu, 14 Jan 2016 15:32:10 -0500	[thread overview]
Message-ID: <45470.1452803530@turing-police.cc.vt.edu> (raw)
In-Reply-To: <5697F683.7010606@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On Thu, 14 Jan 2016 14:26:59 -0500, nick said:
>
>
> On 2016-01-14 12:32 PM, Valdis.Kletnieks@vt.edu wrote:

> >> Have you looked in -
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/cppc_acpi.c
> >> ?
> >
> > Of course he didn't.
> >
> Or maybe he did a allmodconfig build on x86_64 bit and either that file builds correctly on x86 with

That doesn't excuse not doing a 'git grep pcc_mbox_request_channel' or a
'grep -r pcc_mbox_request_channel .', both of which would have find the caller.

> the patch applied due to it never being use on x86 or Kconfig files incorrectly set for allmodconfig
> builds on x86 for this file, or maybe my compiler is broken but I doubt that as it works for all other
> build errors similar to this.

Or you don't have the foggiest clue how Kconfig works, and don't understand
why in a 'allmodconfig' this file is *NOT* built.

Hint 1:

grep cppc drivers/acpi/Makefile
obj-$(CONFIG_ACPI_CPPC_LIB)     += cppc_acpi.o

Hint 2: In the Kconfig:

config ACPI_CPPC_LIB
        bool
        depends on ACPI_PROCESSOR
        depends on !ACPI_CPU_FREQ_PSS

config ACPI_PROCESSOR
        tristate "Processor"
        depends on X86 || IA64 || ARM64
        select ACPI_PROCESSOR_IDLE if X86 || IA64
        select ACPI_CPU_FREQ_PSS if X86 || IA64

It's left as an exercise for the reader to figure out what happens
to ACPI_CPPC_LIB when 'make allmodconfig' sets ACPI_PROCESSOR=m




[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

      parent reply	other threads:[~2016-01-14 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1452577283-30122-1-git-send-email-xerofoify@gmail.com>
2016-01-14 16:37 ` Jassi Brar
2016-01-14 17:03   ` Ashwin Chaugule
2016-01-14 17:32     ` Valdis.Kletnieks
     [not found]       ` <5697F683.7010606@gmail.com>
2016-01-14 20:32         ` Valdis.Kletnieks [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=45470.1452803530@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=ashwin.chaugule@linaro.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xerofoify@gmail.com \
    /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

all inboxes | Powered by JetHome®