public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rakesh Sankaranarayanan <rakesh.sankaranarayanan@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@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,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v2 0/5] net: dsa: microchip: ksz_pwrite status check for lan937x and irq and error checking updates for ksz series
Date: Wed, 09 Nov 2022 13:10:16 +0000	[thread overview]
Message-ID: <166799941602.26002.4075414669051316393.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221107092922.5926-1-rakesh.sankaranarayanan@microchip.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 7 Nov 2022 14:59:17 +0530 you wrote:
> This patch series include following changes,
> - Add KSZ9563 inside ksz_switch_chips. As per current structure,
> KSZ9893 is reused inside ksz_switch_chips structure, but since
> there is a mismatch in number of irq's, new member added for KSZ9563
> and sku detected based on Global Chip ID 4 Register. Compatible
> string from device tree mapped to KSZ9563 for spi and i2c mode
> probes.
> - Assign device interrupt during i2c probe operation.
> - Add error checking for ksz_pwrite inside lan937x_change_mtu. After v6.0,
> ksz_pwrite updated to have return type int instead of void, and
> lan937x_change_mtu still uses ksz_pwrite without status verification.
> - Add port_nirq as 3 for KSZ8563 switch family.
> - Use dev_err_probe() instead of dev_err() to have more standardized error
> formatting and logging.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] net: dsa: microchip: add ksz9563 in ksz_switch_ops and select based on compatible string
    https://git.kernel.org/netdev/net-next/c/ef912fe443ad
  - [net-next,v2,2/5] net: dsa: microchip: add irq in i2c probe
    https://git.kernel.org/netdev/net-next/c/a9c6db3bc9d8
  - [net-next,v2,3/5] net: dsa: microchip: add error checking for ksz_pwrite
    https://git.kernel.org/netdev/net-next/c/e06999c3dc62
  - [net-next,v2,4/5] net: dsa: microchip: ksz8563: Add number of port irq
    https://git.kernel.org/netdev/net-next/c/4630d1420f84
  - [net-next,v2,5/5] net: dsa: microchip: add dev_err_probe in probe functions
    https://git.kernel.org/netdev/net-next/c/9b1833170632

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-09 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  9:29 [PATCH net-next v2 0/5] net: dsa: microchip: ksz_pwrite status check for lan937x and irq and error checking updates for ksz series Rakesh Sankaranarayanan
2022-11-07  9:29 ` [PATCH net-next v2 1/5] net: dsa: microchip: add ksz9563 in ksz_switch_ops and select based on compatible string Rakesh Sankaranarayanan
2022-11-07  9:29 ` [PATCH net-next v2 2/5] net: dsa: microchip: add irq in i2c probe Rakesh Sankaranarayanan
2022-11-07  9:29 ` [PATCH net-next v2 3/5] net: dsa: microchip: add error checking for ksz_pwrite Rakesh Sankaranarayanan
2022-11-07  9:29 ` [PATCH net-next v2 4/5] net: dsa: microchip: ksz8563: Add number of port irq Rakesh Sankaranarayanan
2022-11-07  9:29 ` [PATCH net-next v2 5/5] net: dsa: microchip: add dev_err_probe in probe functions Rakesh Sankaranarayanan
2022-11-09 13:10 ` patchwork-bot+netdevbpf [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=166799941602.26002.4075414669051316393.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --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