net: dsa: mv88e6xxx: Make VTU miss violations less spammy

VTU miss violations can happen under normal conditions. Don't spam the
kernel log, downgrade the output to debug level only. The statistics
counter will indicate it is happening, if anybody not debugging is
interested.

Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Reported-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/drivers/net/dsa/mv88e6xxx/global1_vtu.c b/drivers/net/dsa/mv88e6xxx/global1_vtu.c
index 2cbaf946e7edf0bd6c3b1aa745901fc9532f77f0..058326924f3e2f955161f77bfbc7a7fbcb6d65f1 100644 (file)
--- a/drivers/net/dsa/mv88e6xxx/global1_vtu.c
+++ b/drivers/net/dsa/mv88e6xxx/global1_vtu.c
@@ -548,10 +548,11 @@ static irqreturn_t mv88e6xxx_g1_vtu_prob_irq_thread_fn(int irq, void *dev_id)
        }
 
        if (val & MV88E6XXX_G1_VTU_OP_MISS_VIOLATION) {
-               dev_err_ratelimited(chip->dev, "VTU miss violation for vid %d, source port %d\n",
+               dev_dbg_ratelimited(chip->dev, "VTU miss violation for vid %d, source port %d\n",
                                    entry.vid, spid);
                chip->ports[spid].vtu_miss_violation++;
        }
+
        mutex_unlock(&chip->reg_lock);
 
        return IRQ_HANDLED;