All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: hauke@hauke-m.de, davem@davemloft.net, kuba@kernel.org,
	robh+dt@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] net: lantiq_xrx200: Hardcode the burst length value
Date: Fri, 29 Oct 2021 11:30:11 +0000	[thread overview]
Message-ID: <163550701161.27301.7742022957993105556.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211026205902.335936-1-olek2@wp.pl>

Hello:

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

On Tue, 26 Oct 2021 22:59:01 +0200 you wrote:
> All SoCs with this IP core support 8 burst length. Hauke
> suggested to hardcode this value and simplify the driver.
> 
> Link: https://lkml.org/lkml/2021/9/14/1533
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
>  drivers/net/ethernet/lantiq_xrx200.c | 21 ++++-----------------
>  1 file changed, 4 insertions(+), 17 deletions(-)

Here is the summary with links:
  - [1/2] net: lantiq_xrx200: Hardcode the burst length value
    https://git.kernel.org/netdev/net-next/c/7e553c44f09a
  - [2/2] dt-bindings: net: lantiq-xrx200-net: Remove the burst length properties
    https://git.kernel.org/netdev/net-next/c/0b3f86397fee

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



      parent reply	other threads:[~2021-10-29 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 20:59 [PATCH 1/2] net: lantiq_xrx200: Hardcode the burst length value Aleksander Jan Bajkowski
2021-10-26 20:59 ` [PATCH 2/2] dt-bindings: net: lantiq-xrx200-net: Remove the burst length properties Aleksander Jan Bajkowski
2021-10-29 11:30 ` 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=163550701161.27301.7742022957993105556.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olek2@wp.pl \
    --cc=robh+dt@kernel.org \
    /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.