From: Jakub Kicinski <kuba@kernel.org>
To: Rakesh Sankaranarayanan <rakesh.sankaranarayanan@microchip.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <olteanv@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>
Subject: Re: [PATCH net-next 6/6] net: dsa: microchip: add dev_err_probe in probe functions
Date: Wed, 2 Nov 2022 20:50:47 -0700 [thread overview]
Message-ID: <20221102205047.10867032@kernel.org> (raw)
In-Reply-To: <20221102041058.128779-7-rakesh.sankaranarayanan@microchip.com>
On Wed, 2 Nov 2022 09:40:58 +0530 Rakesh Sankaranarayanan wrote:
> + return dev_err_probe(&mdiodev->dev,
> + PTR_ERR(dev->regmap[i])
> + "Failed to initialize regmap%i\n",
> + ksz8863_regmap_config[i].val_bits);
> }
Does not build.
next prev parent reply other threads:[~2022-11-03 3:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 4:10 [PATCH net-next 0/6] net: dsa: microchip: regmap range validation and ksz_pwrite status check for lan937x and irq and error checking updates for ksz series Rakesh Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 1/6] net: dsa: microchip: lan937x: add regmap range validation Rakesh Sankaranarayanan
2022-11-02 17:15 ` Florian Fainelli
2022-11-03 8:44 ` Rakesh.Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 2/6] net: dsa: microchip: add ksz9563 in ksz_switch_ops and select based on compatible string Rakesh Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 3/6] net: dsa: microchip: add irq in i2c probe Rakesh Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 4/6] net: dsa: microchip: add error checking for ksz_pwrite Rakesh Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 5/6] net: dsa: microchip: ksz8563: Add number of port irq Rakesh Sankaranarayanan
2022-11-02 4:10 ` [PATCH net-next 6/6] net: dsa: microchip: add dev_err_probe in probe functions Rakesh Sankaranarayanan
2022-11-03 3:50 ` Jakub Kicinski [this message]
2022-11-03 8:55 ` Rakesh.Sankaranarayanan
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=20221102205047.10867032@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rakesh.sankaranarayanan@microchip.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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).