From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Lee Jones <lee.jones@linaro.org>,
Jean Delvare <jdelvare@suse.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Max Staudt <max@enpas.org>, Stefan Roese <sr@denx.de>,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mfd: ensure that AXP20X_I2C will have the right deps on X86
Date: Wed, 20 May 2020 16:46:43 +0300 [thread overview]
Message-ID: <ac3c9490-6f2b-e0a4-c817-39979a39afe0@linux.intel.com> (raw)
In-Reply-To: <20200520133429.GC5759@ninjato>
On 5/20/20 4:34 PM, Wolfram Sang wrote:
>
>>> With that said I'm fine with giving this another try, maybe let
>>> the test builders / rand config builds play with it for a while
>>> and see what happens?
>>
>> Yeah, it makes sense to me.
>
> I'd like to see an ACK from the designware maintainers before sending
> this upstream. Testing is all fine, of course.
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
prev parent reply other threads:[~2020-05-20 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:42 [PATCH v3 0/3] Fix dependencies for ACPI drivers with OpRegion settings Mauro Carvalho Chehab
2020-05-18 11:42 ` [PATCH v3 3/3] mfd: ensure that AXP20X_I2C will have the right deps on X86 Mauro Carvalho Chehab
2020-05-18 12:17 ` Hans de Goede
2020-05-18 12:53 ` Mauro Carvalho Chehab
2020-05-20 13:34 ` Wolfram Sang
2020-05-20 13:46 ` Jarkko Nikula [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=ac3c9490-6f2b-e0a4-c817-39979a39afe0@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=jdelvare@suse.de \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=max@enpas.org \
--cc=mchehab+huawei@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sr@denx.de \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).