All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
	Thorsten Glaser <tg@debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: Increase initial mapping to 16MB if possible
Date: Sat, 28 Jun 2014 18:27:33 +0200	[thread overview]
Message-ID: <877g41dmoa.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdXz-ek=go9dV_rcDRKYYve3q80RASFjfJj4nTCe4aMVoQ@mail.gmail.com> (Geert Uytterhoeven's message of "Sat, 28 Jun 2014 17:55:14 +0200")

Geert Uytterhoeven <geert@linux-m68k.org> writes:

> I guess this failure can be triggered with some specific memory
> configuration with your original version, too.

No.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2014-06-28 16:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 10:24 [PATCH] m68k: Increase initial mapping to 16MB if possible Andreas Schwab
2014-04-25  9:37 ` Michael Schmitz
2014-04-29 10:11 ` Thorsten Glaser
2014-04-29 10:33   ` Andreas Schwab
2014-04-29 16:29     ` Geert Uytterhoeven
2014-04-29 16:43       ` Andreas Schwab
2014-04-30  7:38         ` Michael Schmitz
2014-05-25 16:57           ` Geert Uytterhoeven
2014-05-26  1:28             ` Michael Schmitz
2014-06-28 12:46             ` Andreas Schwab
2014-06-28 13:26               ` Geert Uytterhoeven
2014-06-28 13:49                 ` Andreas Schwab
2014-06-28 14:29                   ` Geert Uytterhoeven
2014-06-28 14:36                     ` Andreas Schwab
2014-06-28 15:55                       ` Geert Uytterhoeven
2014-06-28 16:27                         ` Andreas Schwab [this message]
2014-07-06  9:31                           ` Geert Uytterhoeven
2014-07-07 22:11                             ` Andreas Schwab
2014-07-08  7:23                               ` 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=877g41dmoa.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitzmic@gmail.com \
    --cc=tg@debian.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 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.