From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lee Jones <lee.jones@linaro.org>, Sinan Kaya <okaya@kernel.org>
Cc: linux-next@vger.kernel.org, linux-acpi@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [for next][PATCH 1/2] mfd: Fix unmet dependency warning for MFD_TPS68470
Date: Thu, 31 Jan 2019 00:55:33 +0100 [thread overview]
Message-ID: <2030742.Xi8Ns1LLnS@aspire.rjw.lan> (raw)
In-Reply-To: <20190128072156.GE4678@dell>
On Monday, January 28, 2019 8:21:56 AM CET Lee Jones wrote:
> On Thu, 24 Jan 2019, Sinan Kaya wrote:
>
> > On 1/24/2019 5:51 AM, Rafael J. Wysocki wrote:
> > > Is anyone taking this or should I?
> >
> > Nobody replied to this yet. I was hoping this series to go through acpi
> > tree like the rest of the other fixes.
>
> [post-vacation reply]
>
> That's not how these things are usually handled, but I taking into
> consideration the trivialises of the patch, I don't really mind.
>
> Acked-by: Lee Jones <lee.jones@linaro.org>
I've applied this one, thanks!
prev parent reply other threads:[~2019-01-30 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 23:19 [for next][PATCH 1/2] mfd: Fix unmet dependency warning for MFD_TPS68470 Sinan Kaya
2019-01-21 23:19 ` [for next][PATCH 2/2] x86/Kconfig: Select PCI_LOCKLESS_CONFIG if PCI is enabled Sinan Kaya
2019-01-22 12:54 ` Borislav Petkov
2019-01-22 14:39 ` Sinan Kaya
2019-01-24 10:51 ` Rafael J. Wysocki
2019-01-24 17:42 ` Sinan Kaya
2019-01-24 10:51 ` [for next][PATCH 1/2] mfd: Fix unmet dependency warning for MFD_TPS68470 Rafael J. Wysocki
2019-01-24 17:43 ` Sinan Kaya
2019-01-28 7:21 ` Lee Jones
2019-01-30 23:55 ` Rafael J. Wysocki [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=2030742.Xi8Ns1LLnS@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=okaya@kernel.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).