netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: volodymyr.bendiuga@gmail.com,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH repost net-next] dsa: mv88e6xxx: Optimise atu_get
Date: Wed, 4 Jan 2017 22:45:51 +0100	[thread overview]
Message-ID: <20170104214551.GF4229@lunn.ch> (raw)
In-Reply-To: <20170104.162718.86114638722981428.davem@davemloft.net>

> Maybe I over-reacted.

I'm happy somebody other than me is thinking about this.

> I just ran some test programs in userspace on both little and big
> endian and they checked out.

Great, thanks for testing.

       Andrew

      reply	other threads:[~2017-01-04 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 18:56 [PATCH repost net-next] dsa: mv88e6xxx: Optimise atu_get Andrew Lunn
2017-01-04 21:11 ` David Miller
2017-01-04 21:19   ` Andrew Lunn
2017-01-04 21:27     ` Florian Fainelli
2017-01-04 21:27     ` David Miller
2017-01-04 21:45       ` Andrew Lunn [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=20170104214551.GF4229@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.com \
    --cc=volodymyr.bendiuga@gmail.com \
    /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).