From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/5200: make BestComm gen_bd microcode exchangeable
Date: Sat, 03 Oct 2009 17:09:46 +0200 [thread overview]
Message-ID: <1254582586.3331.1@antares> (raw)
In-Reply-To: <20091003144026.GA27519@pengutronix.de> (from w.sang@pengutronix.de on Sat Oct 3 16:40:26 2009)
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Am 03.10.09 16:40 schrieb(en) Wolfram Sang:
> Sorry, I hardly know anything about the microcode. From what I know,
> it shouldn't be much fun due to various bugs in the Bestcomm engine.
Ummm. That's not encouraging! :-/
> Hey! No need for insults! ;)
Sorry, that wasn't my intention, but it's a MUA I *know* it doesn't
understand it... most OSS clients do (like Balsa, Thunderbird, kmail,
etc.).
> > Or is '3676 in general not acceptable for patches?
>
> Maybe. Could you try without next time, and we will see if it works
> better?
Actually, it's in Documentation/email-clients.txt - '3676 must not be
used. Sorry, should have read that before! (However, messages
*without* folding *and* with lines > 78 characters violate RFC2822...)
> Yup, since -rc1. (git log --grep=mtd-ram)
Thanks!
Cheers, Albrecht.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2009-10-03 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 19:55 [PATCH] powerpc/5200: make BestComm gen_bd microcode exchangeable Albrecht Dreß
2009-10-03 9:44 ` Wolfram Sang
2009-10-03 13:50 ` Albrecht Dreß
2009-10-03 14:40 ` Wolfram Sang
2009-10-03 15:09 ` Albrecht Dreß [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=1254582586.3331.1@antares \
--to=albrecht.dress@arcor.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=w.sang@pengutronix.de \
/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).