From: Andreas Schwab <schwab@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: [PATCH/RFC] m68k: atari - Rename "mfp" to "st_mfp"
Date: Fri, 06 Feb 2009 11:37:29 +0100 [thread overview]
Message-ID: <jeiqnnvok6.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0902052159220.16817@anakin> (Geert Uytterhoeven's message of "Thu, 5 Feb 2009 22:07:08 +0100 (CET)")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Atari guys: If I'm not mistaken, the first MFP is the ST-MFP?
Right.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2009-02-06 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 21:07 [PATCH/RFC] m68k: atari - Rename "mfp" to "st_mfp" Geert Uytterhoeven
2009-02-06 10:37 ` Andreas Schwab [this message]
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=jeiqnnvok6.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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