From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: wei.fang@nxp.com, shenwei.wang@nxp.com, xiaoning.wang@nxp.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, linux-imx@nxp.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] net: fec: Fix device_get_match_data usage
Date: Thu, 19 Oct 2023 01:00:23 +0000 [thread overview]
Message-ID: <169767722372.5576.17707408430157555954.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231017063419.925266-1-alexander.stein@ew.tq-group.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Oct 2023 08:34:17 +0200 you wrote:
> Hi,
>
> this is v2 adressing the regression introduced by commit b0377116decd
> ("net: ethernet: Use device_get_match_data()").
>
> Changes in v2:
> * Update the OF device data pointers to the actual device specific struct
> fec_devinfo.
> * Add Patch 2 (unrelated to regression) to remove platform IDs for
> non-Coldfire
>
> [...]
Here is the summary with links:
- [v2,1/2] net: fec: Fix device_get_match_data usage
https://git.kernel.org/netdev/net-next/c/e6809dba5ec3
- [v2,2/2] net: fec: Remove non-Coldfire platform IDs
https://git.kernel.org/netdev/net-next/c/50254bfe1438
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-19 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 6:34 [PATCH v2 0/2] net: fec: Fix device_get_match_data usage Alexander Stein
2023-10-17 6:34 ` [PATCH v2 1/2] " Alexander Stein
2023-10-18 11:33 ` Simon Horman
2023-10-17 6:34 ` [PATCH v2 2/2] net: fec: Remove non-Coldfire platform IDs Alexander Stein
2023-10-18 11:33 ` Simon Horman
2023-10-17 14:37 ` [PATCH v2 0/2] net: fec: Fix device_get_match_data usage Rob Herring
2023-10-19 1:00 ` 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=169767722372.5576.17707408430157555954.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.