public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@vger.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] m68k/amiga: Fix specifying multiple debug= parameters
Date: Mon, 25 Nov 2013 20:03:33 +0100	[thread overview]
Message-ID: <87fvqkpam2.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdUUvzc1eGhJjqye7aOcNQoGgOEfT=TDLQgbef6-0vT=qQ@mail.gmail.com> (Geert Uytterhoeven's message of "Mon, 25 Nov 2013 17:16:10 +0100")

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

>>   2. Do we want to fix it this way? Alternatives are:
>>        a. Reject a second debug= parameter by checking for a non-NULL .write()
>>           method
>>           => only the first debug console will be used,
>>        b. Skip console registration in case of a non-NULL .write() method
>>           => only the last debug console will be used,
>>   3. Atari has a similar issue, with even more (4) debug consoles.

2b is backward compatible.

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:[~2013-11-25 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 19:46 [PATCH/RFC] m68k/amiga: Fix specifying multiple debug= parameters Geert Uytterhoeven
2013-11-25 16:16 ` Geert Uytterhoeven
2013-11-25 19:03   ` Andreas Schwab [this message]
2013-12-01 11:15     ` 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=87fvqkpam2.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@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