All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: "Ingo Jürgensmann" <ij@2013.bluespice.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	"Debian m68k" <debian-68k@lists.debian.org>
Subject: Re: [RFC] m68k: Update defconfigs for v3.9
Date: Sat, 25 May 2013 11:15:01 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.1305251113540.5262@herc.mirbsd.org> (raw)
In-Reply-To: <51A07DD4.3020601@gmail.com>

Michael Schmitz dixit:

> It'll need a bit of backporting into 3.2.25 once it's ready to test, but I can

Don’t bother with that on account of Debian, it’s at 3.8 already,
and for the buildds, running a custom kernel until your driver is
merged in 3.10 and Debian has 3.10 will be no problem ;-)

bye,
//mirabilos
-- 
<gcc> ncal.c: In function 'parsemonth': warning: comparison between pointer
and integer  • <mirabilos> ↑ hab da „in function parselmouth“ gelesen
<Natureshadow> ICH AUCH! • <Natureshadow> Ich hab gerade gedacht "Häh? Wie,
hab da parselmouth gelesen ... steht da doch auch :o?"	-- too much fanfic…

  reply	other threads:[~2013-05-25 11:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 19:19 [RFC] m68k: Update defconfigs for v3.9 Geert Uytterhoeven
2013-05-23 20:28 ` Ingo Jürgensmann
2013-05-25  9:01   ` Michael Schmitz
2013-05-25 11:15     ` Thorsten Glaser [this message]
2013-05-24  7:27 ` Finn Thain
2013-05-24 10:54   ` Laurent Vivier
2013-05-25  8:04     ` Finn Thain
2013-05-24 12:59   ` Geert Uytterhoeven
2013-05-24 13:06     ` Geert Uytterhoeven
2013-05-25  8:06     ` Finn Thain
2013-05-25 19:33 ` Brad Boyer
2013-05-25 19:47   ` Ingo Jürgensmann
2013-05-26  7:53     ` Geert Uytterhoeven

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=Pine.BSM.4.64L.1305251113540.5262@herc.mirbsd.org \
    --to=tg@mirbsd.de \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=ij@2013.bluespice.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitzmic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.