public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Leo Yan <leo.yan@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] coresight: Moving framework and drivers to SPDX identifier
Date: Mon, 23 Apr 2018 18:50:36 +0200	[thread overview]
Message-ID: <20180423165036.GA27119@kroah.com> (raw)
In-Reply-To: <CANLsYkyyRdyFOANZH8oprxuF9n9rFXj_mXasyeOuCp-sb5ZOsg@mail.gmail.com>

On Mon, Apr 23, 2018 at 10:30:38AM -0600, Mathieu Poirier wrote:
> On 23 April 2018 at 05:38, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Apr 17, 2018 at 10:16:57AM -0600, Mathieu Poirier wrote:
> >> Moving all kernel side CoreSight framework and drivers to SPDX identifier.
> >>
> >> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> >> Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> >> ---
> >> Change for V2:
> >> * Added drivers/hwtracing/stm/ftrace.c as pointed out by Alex.
> >
> > This doesn't apply to 4.17-rc2 :(
> 
> My goal was to "socialise" the patch before including it in my tree
> where there are other dependencies.  I will send you the whole tally
> around rc3 or rc4, as usual.

Ah, ok, sounds good.

greg k-h

      reply	other threads:[~2018-04-23 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 16:16 [PATCH v2] coresight: Moving framework and drivers to SPDX identifier Mathieu Poirier
2018-04-19 11:17 ` Alexander Shishkin
2018-04-23 11:38 ` Greg KH
2018-04-23 16:30   ` Mathieu Poirier
2018-04-23 16:50     ` Greg KH [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=20180423165036.GA27119@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.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