netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCHv2 net-next 3/5] net: dsa: mv88e6xxx: Remove SERDES flag
Date: Wed, 24 May 2017 10:59:56 -0400	[thread overview]
Message-ID: <87o9uiti4z.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <1495573486-31827-4-git-send-email-andrew@lunn.ch>

Hi Andrew,

Andrew Lunn <andrew@lunn.ch> writes:

> Now that we use an op for SERDES operations, we don't need a flag for
> it. Remove it.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>

Reviewed-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>

Thanks,

        Vivien

  reply	other threads:[~2017-05-24 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 21:04 [PATCHv2 net-next 0/5] net: dsa: mv88e6xxx: Add basic SERDES support Andrew Lunn
2017-05-23 21:04 ` [PATCHv2 net-next 1/5] net: dsa: mv88e6xxx: Move phy functions into phy.[ch] Andrew Lunn
2017-05-24 15:31   ` Vivien Didelot
2017-05-25 16:35   ` David Miller
2017-05-23 21:04 ` [PATCHv2 net-next 2/5] net: dsa: mv88e6xxx: Refactor mv88e6352 SERDES code into an op Andrew Lunn
2017-05-24 15:03   ` Vivien Didelot
2017-05-23 21:04 ` [PATCHv2 net-next 3/5] net: dsa: mv88e6xxx: Remove SERDES flag Andrew Lunn
2017-05-24 14:59   ` Vivien Didelot [this message]
2017-05-23 21:04 ` [PATCHv2 net-next 4/5] net: dsa: mv88e6xxx: mv88e6390X SERDES support Andrew Lunn
2017-05-24 14:59   ` Vivien Didelot
2017-05-23 21:04 ` [PATCHv2 net-next 5/5] dsa: mv88e6xxx: Enable/Disable SERDES on port enable/disable Andrew Lunn
2017-05-24 14:58   ` Vivien Didelot

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=87o9uiti4z.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me \
    --to=vivien.didelot@savoirfairelinux.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).