From: Stephen Boyd <sboyd@codeaurora.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Satoru OKAMOTO <okamoto.satoru@socionext.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] clk: mb86s7x: Drop non-building driver
Date: Tue, 5 Sep 2017 11:46:55 -0700 [thread overview]
Message-ID: <20170905184655.GK21656@codeaurora.org> (raw)
In-Reply-To: <8601a2ec-33dc-0024-55ce-963f05faca75@suse.de>
On 09/04, Andreas Färber wrote:
> Thanks. Is this 4.14 or 4.15 material at this point? In particular I
4.14 or whatever the next kernel version will be.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: mb86s7x: Drop non-building driver
Date: Tue, 5 Sep 2017 11:46:55 -0700 [thread overview]
Message-ID: <20170905184655.GK21656@codeaurora.org> (raw)
In-Reply-To: <8601a2ec-33dc-0024-55ce-963f05faca75@suse.de>
On 09/04, Andreas F?rber wrote:
> Thanks. Is this 4.14 or 4.15 material at this point? In particular I
4.14 or whatever the next kernel version will be.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-09-05 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 22:52 [PATCH v2] clk: mb86s7x: Drop non-building driver Andreas Färber
2017-08-24 22:52 ` Andreas Färber
2017-09-01 20:32 ` Stephen Boyd
2017-09-01 20:32 ` Stephen Boyd
2017-09-04 15:46 ` Andreas Färber
2017-09-04 15:46 ` Andreas Färber
2017-09-05 18:46 ` Stephen Boyd [this message]
2017-09-05 18:46 ` Stephen Boyd
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=20170905184655.GK21656@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=okamoto.satoru@socionext.com \
--cc=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.