mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>,
	Greg KH <greg@kroah.com>, Rusty Russell <rusty@rustcorp.com.au>,
	Sam Ravnborg <sam@ravnborg.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Venkatesch Pallipadi <venkatesh.pallipadi@intel.com>,
	Mike Travis <travis@sgi.com>, Avi Kivity <avi@qumranet.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Glauber de Oliveira Costa <glommer@gmail.com>,
	Chris Wright <chrisw@sous-sol.org>,
	Christoph Lameter <clameter@sgi.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	Zachary Amsden <zach@vmware.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..
Date: Tue, 2 Oct 2007 22:12:13 +0200	[thread overview]
Message-ID: <200710022212.15219.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LRH.0.999.0710021019310.23586@www.tglx.de>

On Tuesday, 2 October 2007 11:17, Thomas Gleixner wrote:
> On Mon, 1 Oct 2007, Linus Torvalds wrote:
> > This is also a good time to warn about the fact that we're doing the x86 
> > merge very soon (as in the next day or two) after 2.6.23 is out, so if you 
> > have pending patches for the next series that touch arch/i386 or x86-64, 
> > you should get in touch with Thomas Gleixner and Ingo Molnar, who are the 
> > keepers of the merge scripts, and will help you prepare..
> > 
> > Doing it as early as possible in the 2.6.24-rc4 series (basically I'll do 
> > it first thing) will mean that we'll have the maximum amount of time to 
> > sort out any issues, and the thing is, Thomas and Ingo already have a tree 
> > ready to go, so people can check their work against that, and don't need 
> > to think that they have to do any fixups after it his *my* tree. It would 
> > be much better if everybody was just ready for it, and not taken by 
> > surprise.
> > 
> > In other words, people who know they may be affected and would want to 
> > prepare can look at (for example)
> > 
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
> > 
> > and generally get ready for the switch-over. 
> 
> I have uploaded an update of the arch/x86 tree based on -rc9 to
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
> 
> For convenience there is a patch fixup script which helps you to
> convert pending patches against this tree.
> 
> 	http://userweb.kernel.org/~tglx/x86/x86-fixup-patches.py
> 
> It's generated from the merge script and fixes the namespace of
> patches. There will still be some rejects which can not be fixed up
> automatically, but this should be rare.
> 
> I did a test with Andrews -mm series and only ~10 arch/x86 related
> patches had rejects, out of 230+ patches, so the 100%-painless
> conversion ratio is better than 95%. Those patches with rejects were
> trivial to fix.
> 
> Usage: x86-fixup-patches.py sourcepatch destpatch
> 
> source and dest can be the same.
> 
> A helper script to convert complete quilt series is here:
> 	http://userweb.kernel.org/~tglx/x86/fixupseries.sh
> 
> If there is anything we can help with the transition, please do not
> hesitate to ask.

Well, there are several arch-dependent power management patches in -mm queued
up for merging.  Do I need to take care of converting them myself, or will that
be done automatically, or ...?

Greetings,
Rafael

  parent reply	other threads:[~2007-10-02 19:57 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.0.999.0710012029400.3579@woody.linux-foundation.org >
2007-10-02  3:41 ` Linus Torvalds
2007-10-02  9:17   ` Thomas Gleixner
2007-10-02  9:21     ` Andi Kleen
2007-10-02 10:37       ` Jeff Garzik
2007-10-02 10:48         ` Andi Kleen
2007-10-02 11:05           ` Thomas Gleixner
2007-10-02 14:07             ` Ingo Molnar
2007-10-02 14:23               ` Andi Kleen
2007-10-02 14:31                 ` Ingo Molnar
2007-10-02 14:54                   ` Andi Kleen
2007-10-02 14:58                   ` Sam Ravnborg
2007-10-02 15:24                     ` Andi Kleen
2007-10-02 15:27                     ` Ingo Molnar
2007-10-02 15:30                     ` Thomas Gleixner
2007-10-02 15:40                       ` Sam Ravnborg
2007-10-02 12:04       ` Jiri Kosina
2007-10-02 20:12     ` Rafael J. Wysocki [this message]
2007-10-02 20:11       ` Andrew Morton
2007-10-02 20:31         ` Rafael J. Wysocki
2007-10-02 20:32         ` Roland Dreier
2007-10-03  3:53     ` Eric St-Laurent
2007-10-02 12:07   ` Mel Gorman
2007-10-02 12:15     ` Ingo Molnar
2007-10-02 17:21       ` Mel Gorman
2007-10-02 22:09         ` Bill Davidsen
2007-10-03  0:37           ` Mel Gorman
2007-10-03  8:21             ` Ingo Molnar
2007-10-03 12:51               ` Mel Gorman
2007-10-22 15:56                 ` Ingo Molnar
2007-10-03  8:19         ` Ingo Molnar
2007-10-02 14:44   ` John Stoffel
2007-10-02 15:03     ` Ingo Molnar
2007-10-02 15:45     ` John Stoffel
2007-10-02 22:13     ` Bill Davidsen
2007-10-02 22:44   ` Willy Tarreau
2007-10-02 22:51   ` Alistair John Strachan
2007-10-02 23:00     ` Glauber de Oliveira Costa
2007-10-05  5:41       ` Ingo Molnar
2007-10-05  5:38     ` Ingo Molnar
2007-10-05  6:11       ` Sam Ravnborg
2007-10-05  8:32         ` Thomas Gleixner
2007-10-07 23:44           ` Alistair John Strachan
2007-10-02 23:07   ` Diego Calleja
2007-10-02 23:32     ` Linus Torvalds
2007-10-03 15:28       ` Diego Calleja
2007-10-03  8:46   ` [bug] crash when reading /proc/mounts (was: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..) Ingo Molnar
2007-10-03  8:50     ` Ingo Molnar
2007-10-03  9:12       ` Ingo Molnar
2007-10-03  9:23         ` Ingo Molnar
2007-10-03 13:34     ` Al Viro
2007-10-03 14:08       ` Ingo Molnar
2007-10-03 14:26         ` Al Viro
2007-10-03 15:12           ` Arjan van de Ven
2007-10-03 15:11     ` Linus Torvalds
2007-10-03 15:40       ` Ingo Molnar
2007-10-03 16:07         ` Linus Torvalds
2007-10-03 15:47       ` Linus Torvalds
2007-10-03 15:49         ` Ingo Molnar
2007-10-03 16:07           ` Ingo Molnar
2007-10-03 15:51       ` Alan Cox
2007-10-03 16:09         ` Linus Torvalds
2007-10-03 16:25           ` Jan Engelhardt
2007-10-03 17:07             ` Linus Torvalds
2007-10-04 14:12       ` Adrian Bunk
2007-10-04 15:08         ` Alexey Dobriyan
2007-10-03 14:21   ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Timo Jantunen
2007-10-03 19:07   ` Jeff Garzik
2007-10-03 19:25     ` Linus Torvalds
2007-10-04 11:55   ` [patch] net, 9p: build fix with !CONFIG_SYSCTL Ingo Molnar
2007-10-04 17:05   ` [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES Mathieu Chouquet-Stringer
2007-10-04 17:17     ` Peter Zijlstra
2007-10-04 20:47       ` Mathieu Chouquet-Stringer
2007-10-04 21:58       ` Mathieu Chouquet-Stringer
2007-10-04 17:27     ` Linus Torvalds
2007-10-04 20:44       ` Mathieu Chouquet-Stringer
2007-10-04 21:21         ` Linus Torvalds
2007-10-04 22:27           ` Paul Mackerras
2007-10-05  0:12             ` Linus Torvalds
2007-10-05  3:22               ` Mathieu Chouquet-Stringer
2007-10-05  7:43                 ` Peter Zijlstra
2007-10-04 21:50     ` Chuck Ebbert
2007-10-04 21:54       ` Mathieu Chouquet-Stringer
2007-10-06  8:29     ` Hans-Peter Jansen
2007-10-06 11:29       ` Hans-Peter Jansen
2007-10-06 17:36     ` Bill Davidsen

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=200710022212.15219.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=avi@qumranet.com \
    --cc=chrisw@sous-sol.org \
    --cc=clameter@sgi.com \
    --cc=ebiederm@xmission.com \
    --cc=glommer@gmail.com \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=jason.wessel@windriver.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=travis@sgi.com \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=zach@vmware.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

Powered by JetHome