linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Sinan Kaya <okaya@codeaurora.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	eric.auger.pro@gmail.com, wsa@the-dreams.de,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] i2c: fix ACPI_I2C_OPREGION dependency
Date: Wed, 3 Jan 2018 15:03:53 +0100	[thread overview]
Message-ID: <3a0ee0a5-f754-e484-836b-8258d45c2108@redhat.com> (raw)
In-Reply-To: <ccd69b15-9f3c-dbdf-f945-0323b60b4cac@codeaurora.org>

Hi Sinan,
On 03/01/18 14:39, Sinan Kaya wrote:
> On 1/2/2018 1:19 PM, Sinan Kaya wrote:
>> On 1/2/2018 1:10 PM, Randy Dunlap wrote:
>>>>>  config ACPI_I2C_OPREGION
>>>>>  	bool "ACPI I2C Operation region support"
>>>>> -	depends on I2C=y && ACPI
>>>>> +	depends on I2C && ACPI
>>>>>  	default y
>>>>>  	help
>>>>>  	  Say Y here if you want to enable ACPI I2C operation region support.
>>>>>
>>>> Anybody picking this up?
>>> Well.  It looks to me like the patch is reversed or the patch description
>>> needs some improvement.  Or I just don't understand it.
>>
>> I'll let Eric improve the description. 
>>
>> Issue is that if you compile I2C as a module, ACPI_I2C_OPREGION doesn't get selected.
>> Therefore, any ACPI opregion calls targeting I2C fail with no opregion found.
>>
>> The goal is to select ACPI_I2C_OPREGION independent of the I2C module type selection.
>>
> 
> I hope I was able to explain it. =y above is the problem. This config option will only
> be selected if module is built-in not for m case.

Thank you for your input. I just sent a v2 with reworded commit message.
Hope this makes more sense.

Thanks

Eric
> 

      reply	other threads:[~2018-01-03 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 17:05 [PATCH] i2c: fix ACPI_I2C_OPREGION dependency Eric Auger
2018-01-02 18:07 ` Sinan Kaya
2018-01-02 18:10   ` Randy Dunlap
2018-01-02 18:19     ` Sinan Kaya
2018-01-03 13:39       ` Sinan Kaya
2018-01-03 14:03         ` Auger Eric [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=3a0ee0a5-f754-e484-836b-8258d45c2108@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=eric.auger.pro@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okaya@codeaurora.org \
    --cc=rdunlap@infradead.org \
    --cc=wsa@the-dreams.de \
    /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).