From: Jiri Olsa <jolsa@redhat.com>
To: Vladimir Nikulichev <nvs@tbricks.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Correctly handle symbols in VDSO
Date: Wed, 9 Apr 2014 18:13:10 +0200 [thread overview]
Message-ID: <20140409161310.GB19506@krava.brq.redhat.com> (raw)
In-Reply-To: <20140409153546.GA19506@krava.brq.redhat.com>
On Wed, Apr 09, 2014 at 05:35:46PM +0200, Jiri Olsa wrote:
> On Wed, Apr 09, 2014 at 10:46:13AM +0400, Vladimir Nikulichev wrote:
> > Hi,
> >
> > On Apr 8, 2014, at 7:41 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > > hi,
> > > could you please put explanation from first email
> > > into the patch changelog?
> > >
> > > cc-ing lkml
> > >
> > > thanks,
> > > jirka
> >
> >
> > OK, pasting it together:
>
> ook
>
> hum, your email's encoding kills my 'git am' :-\
> also 'perf tools: Adjust symbols in VDSO' should go into the
> email subject
>
> I processed this patch by hand this time
actually I'll have to ask you to resend your patch
with proper subject and coding, refer to:
https://www.kernel.org/doc/Documentation/email-clients.txt
"Emailed patches should be in ASCII or UTF-8 encoding only."
Please CC lkml (linux-kernel@vger.kernel.org). Strangely enough,
I don't see your patch there at the moment..
thanks,
jirka
prev parent reply other threads:[~2014-04-09 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6A5CDD8-F8F1-4C9D-8BCF-83A739FD6A2F@tbricks.com>
[not found] ` <87eh19y8cm.fsf@sejong.aot.lge.com>
[not found] ` <3C60FB26-A78B-4E37-B4A6-E6F7283CEB4C@tbricks.com>
2014-04-08 15:41 ` Jiri Olsa
[not found] ` <A7CC2084-4F71-436C-9AEC-394F66A4981E@tbricks.com>
2014-04-09 15:35 ` Jiri Olsa
2014-04-09 16:13 ` Jiri Olsa [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=20140409161310.GB19506@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nvs@tbricks.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®