From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Thorsten Glaser <tg@mirbsd.de>
Subject: Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable
Date: Wed, 29 Jun 2011 13:19:57 +0200 [thread overview]
Message-ID: <BANLkTik6-eEhu23Vzjs6TS6dC_912ZCafQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinH6+cyubYpo+cfOuLiKqTjKdmZvg@mail.gmail.com>
On Mon, Jun 27, 2011 at 08:56, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Mon, Jun 27, 2011 at 01:49, Michael Schmitz
> <schmitzmic@googlemail.com> wrote:
>> after making sure I had a good patch file, the patch applied sort of
>> cleanly (I had used DEBUG in the stram pool code) and the resulting
>> kernel runs fine on my Falcon. Geert's resource allocator appears to
>> do the right thing and provides ST-RAM where needed so the old ST-RAM
>> allcocator can go.
>
> Good. Will queue for 3.1.
I folded it into your previous patch and pushed it out for 3.1.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2011-06-29 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QNV5z-0006jD-Ej@franck.debian.org>
[not found] ` <20110521122605.GA16345@chumley.earth.sol>
[not found] ` <Pine.BSM.4.64L.1105211232060.14234@herc.mirbsd.org>
[not found] ` <Pine.BSM.4.64L.1105211327140.14234@herc.mirbsd.org>
2011-05-24 12:22 ` linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable Geert Uytterhoeven
2011-05-30 17:14 ` Michael Schmitz
2011-05-30 17:22 ` Geert Uytterhoeven
2011-06-13 18:49 ` Geert Uytterhoeven
2011-06-13 20:35 ` Michael Schmitz
2011-06-19 4:30 ` Michael Schmitz
2011-06-19 7:37 ` Andreas Schwab
2011-06-19 20:08 ` Michael Schmitz
2011-06-26 23:49 ` Michael Schmitz
2011-06-27 6:56 ` Geert Uytterhoeven
2011-06-29 11:19 ` Geert Uytterhoeven [this message]
2011-06-29 17:38 ` Thorsten Glaser
2011-06-29 19:33 ` Geert Uytterhoeven
2011-06-29 20:05 ` [m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable) Thorsten Glaser
2011-06-29 21:53 ` maximilian attems
2011-06-29 21:59 ` [m68k] Patches for 3.0 Thorsten Glaser
2011-07-03 18:18 ` maximilian attems
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=BANLkTik6-eEhu23Vzjs6TS6dC_912ZCafQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.com \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
/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