public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	peter.lachner@intel.com, norbert.schulz@intel.com,
	keven.boell@intel.com, yann.fouassier@intel.com,
	laurent.fert@intel.com
Subject: Re: [PATCH v3 00/11] Introduce Intel Trace Hub support
Date: Wed, 5 Aug 2015 13:31:42 -0700	[thread overview]
Message-ID: <20150805203142.GA5055@kroah.com> (raw)
In-Reply-To: <CANLsYkyyRbmM2Rgct2dCpN_8Afvd+fQxp_iHijdU5qtxB21EEw@mail.gmail.com>

On Thu, Jul 23, 2015 at 09:27:53AM -0600, Mathieu Poirier wrote:
> On 22 July 2015 at 09:49, Alexander Shishkin
> <alexander.shishkin@linux.intel.com> wrote:
> > Alexander Shishkin <alexander.shishkin@linux.intel.com> writes:
> >
> >> Hi Greg and everybody,
> >
> > Seems like a polite nudge might be in order. :)
> >
> > Cheers,
> > --
> > Alex
> 
> Greg and all,
> 
> I have reviewed the portion of Alex's work that pertains to the
> generic STM interface - in its current form it is generic enough to
> cater to both Intel and ARM STM blocks.  A few modifications will
> likely be required when upstreaming of the coresight-stm driver but
> base on our (Alex and I) previous integration exercise, those should
> be minor.

So is that a "reviewed-by:" mark for some of these patches from you?
I'd really like that to feel better about applying these...

thanks,

greg k-h

  reply	other threads:[~2015-08-05 20:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 10:08 [PATCH v3 00/11] Introduce Intel Trace Hub support Alexander Shishkin
2015-07-06 10:08 ` [PATCH v3 01/11] stm class: Introduce an abstraction for System Trace Module devices Alexander Shishkin
2015-07-08 12:32   ` Chunyan Zhang
2015-07-08 12:49     ` Alexander Shishkin
2015-07-29  4:21   ` Chunyan Zhang
2015-07-29 13:25     ` Alexander Shishkin
2015-07-29 13:35       ` Mark Brown
2015-07-29 13:46         ` Alexander Shishkin
2015-07-30  3:38           ` Chunyan Zhang
2015-07-30  5:45             ` Alexander Shishkin
2015-07-30  6:15               ` Chunyan Zhang
2015-07-30  3:19       ` Chunyan Zhang
2015-07-30  6:37         ` Alexander Shishkin
2015-07-30  6:59           ` Chunyan Zhang
2015-07-30  7:11             ` Chunyan Zhang
2015-07-30  7:16             ` Alexander Shishkin
2015-08-05 23:01   ` Mathieu Poirier
2015-07-06 10:08 ` [PATCH v3 02/11] MAINTAINERS: add an entry for System Trace Module device class Alexander Shishkin
2015-07-06 10:08 ` [PATCH v3 03/11] stm class: dummy_stm: Add dummy driver for testing stm class Alexander Shishkin
2015-08-05 23:02   ` Mathieu Poirier
2015-07-06 10:08 ` [PATCH v3 04/11] stm class: stm_console: Add kernel-console-over-stm driver Alexander Shishkin
2015-08-05 23:03   ` Mathieu Poirier
2015-07-06 10:08 ` [PATCH v3 05/11] intel_th: Add driver infrastructure for Intel Trace Hub devices Alexander Shishkin
2015-07-06 10:08 ` [PATCH v3 06/11] intel_th: Add pci glue layer for Intel Trace Hub Alexander Shishkin
2015-07-06 10:09 ` [PATCH v3 07/11] intel_th: Add Global Trace Hub driver Alexander Shishkin
2015-07-06 10:09 ` [PATCH v3 08/11] intel_th: Add Software " Alexander Shishkin
2015-07-06 10:09 ` [PATCH v3 09/11] intel_th: Add Memory Storage Unit driver Alexander Shishkin
2015-07-06 10:09 ` [PATCH v3 10/11] intel_th: Add PTI output driver Alexander Shishkin
2015-07-06 10:09 ` [PATCH v3 11/11] MAINTAINERS: add an entry for Intel(R) Trace Hub Alexander Shishkin
2015-07-22 15:49 ` [PATCH v3 00/11] Introduce Intel Trace Hub support Alexander Shishkin
2015-07-23 15:27   ` Mathieu Poirier
2015-08-05 20:31     ` Greg Kroah-Hartman [this message]
2015-07-29 13:26   ` Alexander Shishkin
2015-07-31  5:16     ` Alexander Shishkin

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=20150805203142.GA5055@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=keven.boell@intel.com \
    --cc=laurent.fert@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=norbert.schulz@intel.com \
    --cc=peter.lachner@intel.com \
    --cc=yann.fouassier@intel.com \
    /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