From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-kernel-dev@beckhoff.com, Stephen Boyd <sboyd@kernel.org>
Cc: Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/1] Add several Beckhoff Automation boards to critclk_systems DMI table
Date: Mon, 6 May 2019 16:50:59 +0200 [thread overview]
Message-ID: <21677236-b7fc-c51b-958a-269b5e65af54@redhat.com> (raw)
In-Reply-To: <CAHp75Vc4xWbnGoaS8tRDV4_F-Qifh7K1hoFn0V-OObun2Sd0DA@mail.gmail.com>
Hi,
On 06-05-19 14:40, Andy Shevchenko wrote:
> On Thu, May 2, 2019 at 4:04 PM <linux-kernel-dev@beckhoff.com> wrote:
>>
>> From: Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>
>>
>> There are several Beckhoff Automation industrial PC boards which use
>> pmc_plt_clk* clocks for ethernet controllers. The patch adds affected boards
>> to critclk_systems DMI table so the clocks are marked as CLK_CRITICAL and
>> not turned off.
>> This should be applied on top of another patch as both change
>> the same table:
>> [PATCH] platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI table
>
> Yes, that's why it either should go via CLK tree, or I need an
> immutable tag or branch from them.
> Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com>
As I just mentioned in your reply to the "[PATCH] platform/x86: pmc_atom:
Add Lex 3I380D industrial PC to critclk_systems DMI table":
"Stephen added the patches this depends on to his fixes branch, so they
are in the 5.1 / Torvald's master branch, since we are now in the 5.2 merge
window, you should be able to cleanly apply this directly."
So both that patch and this patch should be able to go through the d-p-x86 tree
unless I'm missing something?
Regards,
Hans
>
>>
>> Steffen Dirkwinkel (1):
>> platform/x86: pmc_atom: Add several Beckhoff Automation boards to
>> critclk_systems DMI table
>>
>> drivers/platform/x86/pmc_atom.c | 24 ++++++++++++++++++++++++
>> 1 file changed, 24 insertions(+)
>>
>> --
>> 2.21.0
>
>
>
prev parent reply other threads:[~2019-05-06 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 13:03 linux-kernel-dev
2019-05-02 13:03 ` [PATCH 1/1] platform/x86: pmc_atom: " linux-kernel-dev
2019-05-06 12:40 ` [PATCH 0/1] " Andy Shevchenko
2019-05-06 14:50 ` Hans de Goede [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=21677236-b7fc-c51b-958a-269b5e65af54@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel-dev@beckhoff.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=s.dirkwinkel@beckhoff.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®