Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
	f.fainelli@gmail.com, netdev@vger.kernel.org,
	linux@armlinux.org.uk, chris.packham@alliedtelesis.co.nz,
	pabeni@redhat.com
Subject: Re: [PATCH v2 net 1/4] net: dsa: mv88e6xxx: Improve I/O related error logging
Date: Thu, 19 Dec 2024 16:32:36 +0200	[thread overview]
Message-ID: <20241219143236.udpywj7n56qahfrz@skbuf> (raw)
In-Reply-To: <20241219123106.730032-2-tobias@waldekranz.com> <20241219123106.730032-2-tobias@waldekranz.com>

On Thu, Dec 19, 2024 at 01:30:40PM +0100, Tobias Waldekranz wrote:
> +int mv88e6xxx_wait_mask(struct mv88e6xxx_chip *chip, int addr, int reg,
> +			u16 mask, u16 val)
> +{
> +	u16 last;
> +	int err;
> +
> +	err = _mv88e6xxx_wait_mask(chip, addr, reg, mask, val, &last);
> +	if (!err)
> +		return 0;
> +
> +	dev_err(chip->dev,
> +		"%s waiting for 0x%02x/0x%02x to match 0x%04x (mask:0x%04x last:0x%04x)\n",
> +		(err == -ETIMEDOUT) ? "Timed out" : "Failed",
> +		addr, reg, val, mask, last);

Would it help to use symbolic error names ("%pe", ERR_PTR(err))? You
wouldn't have to single out "Timed out", since it would print -ETIMEDOUT
and that should be pretty obvious already.

> +	return err;
> +}

  parent reply	other threads:[~2024-12-19 14:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 12:30 [PATCH v2 net 0/4] net: dsa: mv88e6xxx: Amethyst (6393X) fixes Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 1/4] net: dsa: mv88e6xxx: Improve I/O related error logging Tobias Waldekranz
2024-12-19 13:41   ` Andrew Lunn
2024-12-19 14:32   ` Vladimir Oltean [this message]
2024-12-19 12:30 ` [PATCH v2 net 2/4] net: dsa: mv88e6xxx: Give chips more time to activate their PPUs Tobias Waldekranz
2024-12-19 13:41   ` Andrew Lunn
2024-12-19 12:30 ` [PATCH v2 net 3/4] net: dsa: mv88e6xxx: Never force link on in-band managed MACs Tobias Waldekranz
2024-12-19 13:43   ` Andrew Lunn
2025-01-02 10:31   ` Russell King (Oracle)
2025-01-02 13:06     ` Tobias Waldekranz
2025-01-02 17:08       ` Russell King (Oracle)
2025-01-04 21:37         ` Tobias Waldekranz
2025-01-04 22:09           ` Russell King (Oracle)
2025-01-04 23:16             ` Tobias Waldekranz
2025-01-05 10:41               ` Russell King (Oracle)
2025-01-05 23:30                 ` Tobias Waldekranz
2025-01-06  8:20                   ` Russell King (Oracle)
2025-01-06 14:39                     ` Tobias Waldekranz
2024-12-19 12:30 ` [PATCH v2 net 4/4] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user ports on 6393X Tobias Waldekranz
2024-12-19 13:44   ` Andrew Lunn
2024-12-19 14:05   ` Vladimir Oltean
2024-12-19 14:14     ` Vladimir Oltean
2024-12-19 14:34     ` Tobias Waldekranz
2024-12-19 14:42       ` Vladimir Oltean
2024-12-19 14:52         ` Vladimir Oltean
2024-12-19 15:02           ` Tobias Waldekranz
2024-12-19 14:29   ` Vladimir Oltean

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=20241219143236.udpywj7n56qahfrz@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tobias@waldekranz.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