From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>, Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v2] clk: meson: use SPDX license identifiers consistently
Date: Fri, 18 May 2018 12:10:34 +0200 [thread overview]
Message-ID: <1526638234.2897.74.camel@baylibre.com> (raw)
In-Reply-To: <152649194881.210890.1329258497783697194@swboyd.mtv.corp.google.com>
On Wed, 2018-05-16 at 10:32 -0700, Stephen Boyd wrote:
> Quoting Jerome Brunet (2018-05-16 08:14:13)
> > On Wed, 2018-05-16 at 08:03 -0700, Stephen Boyd wrote:
> > > Quoting Jerome Brunet (2018-05-16 01:50:40)
> > > > Replace every license notices in drivers/clk/meson by SPDX license
> > > > identifiers, as described in license-rules.rst
> > > >
> > > > Acked-by: Neil Armstrong <narmstrong@baylibre.com>
> > > > Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> > > > ---
> > >
> > > Acked-by: Stephen Boyd <sboyd@kernel.org>
> > >
> > > I take it this will come through a PR? Otherwise I can apply it to
> > > clk-meson branch.
> >
> > We may have a few other patches coming this week. I was planning on making
> > another PR sometime next week, if this is OK with you.
> >
>
> Sounds fine. Thanks.
>
Applied with Stephen's Ack
prev parent reply other threads:[~2018-05-18 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:50 [PATCH v2] clk: meson: use SPDX license identifiers consistently Jerome Brunet
2018-05-16 15:03 ` Stephen Boyd
2018-05-16 15:14 ` Jerome Brunet
2018-05-16 17:32 ` Stephen Boyd
2018-05-18 10:10 ` Jerome Brunet [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=1526638234.2897.74.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=festevam@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).