All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Haiyan Song <haiyanx.song@intel.com>,
	jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2] perf vendor events: Add Icelake V1.00 event file
Date: Thu, 8 Aug 2019 10:53:22 -0300	[thread overview]
Message-ID: <20190808135322.GH19444@kernel.org> (raw)
In-Reply-To: <ffd8275f-6eaa-58b7-dc17-7058b42249d3@linux.intel.com>

Em Wed, Jul 24, 2019 at 09:08:56AM -0400, Liang, Kan escreveu:
> 
> 
> On 7/24/2019 2:32 AM, Haiyan Song wrote:
> > Hi,
> > 
> > This patch contains lines that longer than 998 characters,
> > I've sent it by 'git send-email', but when apply it,
> > prompt information "error: corrupt patch at line 2558".
> > 
> >     https://lkml.org/lkml/2019/6/24/1278
> > 
> > I checked the line at 2558, it is very short line.
> > So the patch may be truncated before applying it.
> > 
> > Could you let me to send this patch as attachment? Please check the
> > attachment in this mail.
> > 
> 
> The attached event list looks good to me.
> 
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>

Thanks, applied.

- Arnaldo

  reply	other threads:[~2019-08-08 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  2:27 [PATCH v2] perf vendor events: Add Icelake V1.00 event file Haiyan Song
2019-07-24  6:32 ` Haiyan Song
2019-07-24 13:08   ` Liang, Kan
2019-08-08 13:53     ` Arnaldo Carvalho de Melo [this message]
2019-07-30 19:08   ` Arnaldo Carvalho de Melo
2019-08-15  9:20   ` [tip:perf/core] perf vendor events intel: " tip-bot for Haiyan Song
  -- strict thread matches above, loose matches on Subject: below --
2019-06-27  3:10 [PATCH v2] perf vendor events: " Haiyan Song
2019-06-17  2:58 Haiyan Song
2019-06-24 19:03 ` Arnaldo Carvalho de Melo

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=20190808135322.GH19444@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=haiyanx.song@intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@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 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.