From: Scott Wood <scottwood@freescale.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: igal.liberman@freescale.com, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, madalin.bucur@freescale.com
Subject: Re: [v2,9/9] fsl/fman: Add FMan MAC driver
Date: Thu, 25 Jun 2015 19:59:29 -0500 [thread overview]
Message-ID: <1435280369.2977.4.camel@freescale.com> (raw)
In-Reply-To: <1435273590.28572.11.camel@tiscali.nl>
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
> (Evolution 3.16 is basically unbearable for replying to patches.
> Anyone
> else running into this?)
If you mean the crazy lag when selecting moderate-to-large amounts of
text (for snipping), yes.
-Scott
next prev parent reply other threads:[~2015-06-26 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 19:37 [v2,9/9] fsl/fman: Add FMan MAC driver igal.liberman
2015-06-25 23:06 ` Paul Bolle
2015-06-26 0:59 ` Scott Wood [this message]
2015-06-26 2:21 ` Michael Ellerman
2015-06-26 2:25 ` Scott Wood
2015-06-29 1:55 ` Michael Ellerman
2015-06-26 7:01 ` Paul Bolle
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=1435280369.2977.4.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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).