From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-next@vger.kernel.org,
Linux/m68k <linux-m68k@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 26
Date: Tue, 27 May 2008 10:51:44 +1000 [thread overview]
Message-ID: <20080527105144.82b975d7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0805261430020.4417@anakin>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
Hi Geert,
On Mon, 26 May 2008 16:20:43 +0200 (CEST) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Now multi_defconfig is in Linus' tree, do you mind enabling builds for
> m68k multi_defconfig and sun3_defconfig using Linus' tree, too?
OK, will do.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-27 0:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 7:22 linux-next: Tree for May 26 Stephen Rothwell
2008-05-26 9:42 ` [BUG] linux-next: Tree for May 26 - kernel oops at __alloc_pages_internal () Kamalesh Babulal
2008-05-26 14:20 ` linux-next: Tree for May 26 Geert Uytterhoeven
2008-05-27 0:51 ` Stephen Rothwell [this message]
2008-05-27 3:00 ` Stephen Rothwell
2008-05-26 14:46 ` drivers/char/dsp56k.c breakage [was: Re: linux-next: Tree for May 26] Geert Uytterhoeven
2008-05-26 14:56 ` Jonathan Corbet
2009-05-26 7:15 linux-next: Tree for May 26 Stephen Rothwell
2010-05-26 5:34 Stephen Rothwell
2011-05-26 6:39 Stephen Rothwell
2014-05-26 9:38 Stephen Rothwell
2015-05-26 8:18 Stephen Rothwell
2016-05-26 4:20 Stephen Rothwell
2017-05-26 3:11 Stephen Rothwell
2020-05-26 10:39 Stephen Rothwell
2021-05-26 7:46 Stephen Rothwell
2022-05-26 7:24 Stephen Rothwell
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=20080527105144.82b975d7.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).