All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next v2 1/4] tsnep: Consistent naming of struct net_device
Date: Wed, 30 Nov 2022 23:39:18 +0100	[thread overview]
Message-ID: <Y4fblsj9w9FS9c48@lunn.ch> (raw)
In-Reply-To: <20221130193708.70747-2-gerhard@engleder-embedded.com>

On Wed, Nov 30, 2022 at 08:37:05PM +0100, Gerhard Engleder wrote:

It is normal to have some sort of commit message, even if it is just
the Subject: in different words.

> Signed-off-by: Gerhard Engleder <gerhard@engleder-embedded.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2022-11-30 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 19:37 [PATCH net-next v2 0/4] tsnep: Throttle interrupts, RX buffer allocation and ethtool_get_channels() Gerhard Engleder
2022-11-30 19:37 ` [PATCH net-next v2 1/4] tsnep: Consistent naming of struct net_device Gerhard Engleder
2022-11-30 22:39   ` Andrew Lunn [this message]
2022-11-30 19:37 ` [PATCH net-next v2 2/4] tsnep: Add ethtool::get_channels support Gerhard Engleder
2022-11-30 22:39   ` Andrew Lunn
2022-11-30 19:37 ` [PATCH net-next v2 3/4] tsnep: Throttle interrupts Gerhard Engleder
2022-11-30 22:53   ` Andrew Lunn
2022-11-30 19:37 ` [PATCH net-next v2 4/4] tsnep: Rework RX buffer allocation Gerhard Engleder
2022-12-02 11:20 ` [PATCH net-next v2 0/4] tsnep: Throttle interrupts, RX buffer allocation and ethtool_get_channels() patchwork-bot+netdevbpf

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=Y4fblsj9w9FS9c48@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gerhard@engleder-embedded.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.