From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] Add perf tools support: this is the kernel patch to be applied to the kernel for kernel compile to go through; it basically adds a typedef.
Date: Thu, 3 Jan 2013 11:16:34 +0100 [thread overview]
Message-ID: <20130103111634.1338bb49@skate> (raw)
In-Reply-To: <CAPDLWs-2Jdyj5F_XaVyGW3kciq2Qmpz0ivbgBAvacXeNZSWy2w@mail.gmail.com>
Dear Kaiwan Billimoria,
On Thu, 3 Jan 2013 15:37:09 +0530, Kaiwan Billimoria wrote:
> Also, AFAIK, the Sub line has the phrase [PATCH n/3]; where n is 0, 1,
> 2 & 3, thus subject is unique (this is how git generated them). If
> this is not sufficient, pl let me know..
This is not sufficient. Everything between [...] is ignored when the
patch is applied. Each of your patches should have a different commit
message.
That said, there is no reason for those 3 patches to be separate. If
you apply patch 1 alone, you have a config option that does nothing. If
you apply patches 1 and 2, then things break because it will try to
apply perf.patch which does not exist.
So basically, you should merge all your patches.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-03 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 7:51 [Buildroot] [PATCH 3/3] Add perf tools support: this is the kernel patch to be applied to the kernel for kernel compile to go through; it basically adds a typedef Kaiwan Billimoria
2013-01-03 8:33 ` Carsten Schoenert
2013-01-03 10:07 ` Kaiwan Billimoria
2013-01-03 10:16 ` Thomas Petazzoni [this message]
2013-01-03 10:20 ` Thomas Petazzoni
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=20130103111634.1338bb49@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.