From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS
Date: Thu, 12 Apr 2012 19:36:11 +0100 [thread overview]
Message-ID: <20120412183610.GD18049@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1334146730.23924.238.camel@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Wed, Apr 11, 2012 at 08:18:50AM -0400, Steven Rostedt wrote:
> Please change your subject when you submit a new patch. I've ignored
> your last one because I thought I already applied it.
I wrote the subject for the second patch completely from scratch when I
noticed the build error I'm afraid - more variation in the build errors
would mean more variation in the subjects!
> As with this one, has the same subject. I only noticed it as I was about
> to tell you that it was already applied.
Which wouldn't have been the end of the world, it'd at least have been a
response.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-12 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 8:20 [PATCH] trace: Fix build breakage without CONFIG_PERF_EVENTS Mark Brown
2012-04-11 12:18 ` Steven Rostedt
2012-04-12 18:36 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-13 8:52 Mark Brown
2012-03-26 13:33 Mark Brown
2012-02-28 11:02 Mark Brown
2012-02-28 11:10 ` Mark Brown
2012-02-28 14:57 ` Jiri Olsa
2012-03-13 22:33 ` Steven Rostedt
2012-03-13 23:03 ` Jiri Olsa
2012-02-28 11:10 ` Mark Brown
2012-02-28 13:21 ` Jiri Olsa
2012-02-28 13:37 ` Mark Brown
2012-02-28 14:02 ` Steven Rostedt
2012-02-28 14:03 ` Mark Brown
2012-02-28 14:43 ` Jiri Olsa
2012-02-28 14:52 ` Steven Rostedt
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=20120412183610.GD18049@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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 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.