Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: gregory.haskins@gmail.com (Gregory Haskins)
Subject: [ltt-dev] patches for 31-rc5?
Date: Thu, 20 Aug 2009 11:08:13 -0400	[thread overview]
Message-ID: <4A8D66DD.2050502@gmail.com> (raw)
Message-ID: <20090820150813.i1IjZl-zEFNrL_0FK5rFHuqEROUW88v0np7qMc5fF_g@z> (raw)
In-Reply-To: <20090813142324.GA32765@Krystal>

Hi Mathieu

Mathieu Desnoyers wrote:
> * Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
>> * Gregory Haskins (gregory.haskins at gmail.com) wrote:
>>> Are there any in the works?  If not, perhaps I can take a stab at the
>>> forward port.
>>>
>> Not yet, but -rc5 sounds like a good timing to start forward porting.
>> I'll look into this today.
>>
> 
> Hrm, the instrumentation part will take a while to port, because we have
> more and more clashes with ftrace.
> 
> If you want to start working on this, please provide patches in the
> form:
> 
> original-patch.reject-fix-2.6.31.patch
> 
> for each patch which has rejects, so I can look at the result and merge
> them through the patchset.

I thought I would try to automate this process a little bit, so I wrote
a script to run through and stop when it hits rejects, create the new
patch, etc.

I figured I should check to see if it is generating output like you
expect, before I do all the work.

What it does is refresh each patch with the non-conflicts, and then
generates a new patch with the same as the original, but with ".fixes"
appended to the end, and a "Fixes for 2.6.31-rc6" prologue.

(And yes, I know the "From:" attribution of the original patches is
wrong since it is assigning credit to me..I tried to fix this but it
didn't work...just ignore the "From" field in the original patch for now)

Here is a trial run of the first few patches.  When the original and
fixes patch is empty, I means "drop the patch" since its already upstream.

ftp://ftp.novell.com/dev/ghaskins/patch-2.6.31-rc6-0.155.tar.bz2

Does this look about right?

Kind Regards,
-Greg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090820/07c6596e/attachment-0002.pgp>


  parent reply	other threads:[~2009-08-20 15:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:20 Gregory Haskins
2009-08-12 15:20 ` Gregory Haskins
2009-08-12 15:20 ` Gregory Haskins
2009-08-13 13:52 ` Mathieu Desnoyers
2009-08-13 13:52   ` Mathieu Desnoyers
2009-08-13 13:52   ` Mathieu Desnoyers
2009-08-13 14:23   ` Mathieu Desnoyers
2009-08-13 14:23     ` Mathieu Desnoyers
2009-08-13 14:23     ` Mathieu Desnoyers
2009-08-14  2:24     ` Gregory Haskins
2009-08-14  2:24       ` Gregory Haskins
2009-08-14  2:24       ` Gregory Haskins
2009-08-20 15:08     ` Gregory Haskins [this message]
2009-08-20 15:08       ` Gregory Haskins
2009-08-20 15:08       ` Gregory Haskins
2009-08-20 15:20       ` Mathieu Desnoyers
2009-08-20 15:20         ` Mathieu Desnoyers
2009-08-20 15:20         ` Mathieu Desnoyers

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=4A8D66DD.2050502@gmail.com \
    --to=gregory.haskins@gmail.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