mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@elte.hu>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: m68k libc5 regression
Date: Sun, 1 Jun 2008 02:41:05 -0700	[thread overview]
Message-ID: <20080601024105.b350d1b7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080601092205.GA18045@uranus.ravnborg.org>

On Sun, 1 Jun 2008 11:22:05 +0200 Sam Ravnborg <sam@ravnborg.org> wrote:

> On Sun, Jun 01, 2008 at 01:48:24AM -0700, Andrew Morton wrote:
> > On Sun, 1 Jun 2008 10:37:59 +0200 (CEST) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > 
> > > > I shall merge this fix into my tree (y'know - the one where memory
> > > > management patches are hosted) and I'll get it into 2.6.26 and shall
> > > > offer it to the -stable team.  This will cause me to get collisions
> > > > with the duplicated patch in linux-next but fortunately it is small. 
> > > > This time.
> > > 
> > > So what's the appropriate way to handle this?
> > 
> > Well at least please reply letting people know what's happening with it.
> > 
> > Ask me to merge it and remind me that it's needed in -stable.  Or just
> > send the thing to Linus and -stable immediately.
> 
> I recall adding:
> Cc: stable@kernel.org
> 
> will automagically tell the stable team when this is
> merged and that it is a -stable candidate.
> 

Yup.  Except I always use the <> wrappers around the email address.  In
fact my scripts require that (and probably shouldn't).  We don't seem
very consistent with that.

  reply	other threads:[~2008-06-01  9:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 20:38 Geert Uytterhoeven
2008-05-26 22:19 ` Jiri Kosina
2008-05-29 11:03   ` Jiri Kosina
2008-05-29 11:28     ` Geert Uytterhoeven
2008-05-29 19:38   ` Geert Uytterhoeven
2008-06-02 10:28     ` Jiri Kosina
2008-06-01  7:53   ` Andrew Morton
2008-06-01  8:37     ` Geert Uytterhoeven
2008-06-01  8:48       ` Andrew Morton
2008-06-01  9:22         ` Sam Ravnborg
2008-06-01  9:41           ` Andrew Morton [this message]
2008-06-01 10:34             ` Sam Ravnborg
2008-06-01  9:56         ` Geert Uytterhoeven
2008-06-01 13:26     ` Diagnosing linux-next (Was: Re: m68k libc5 regression) Stephen Rothwell
2008-06-01 21:04       ` Andrew Morton
2008-06-02  0:39         ` Paul Mackerras
2008-06-02  1:06           ` Andrew Morton
2008-06-02  2:12             ` Paul Mackerras
2008-06-02  5:37               ` Andrew Morton
2008-06-02  5:49                 ` Paul Mackerras
2008-06-02  6:22                   ` Andrew Morton
2008-06-02 10:27     ` m68k libc5 regression Jiri Kosina

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=20080601024105.b350d1b7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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

Powered by JetHome