Netdev List
 help / color / mirror / Atom feed
From: Sandeep Haemoon <sandeeph@loljews.com>
To: netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>, Felix Fietkau <nbd@nbd.name>,
	Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH net-next v7 0/3] net: ethernet: mtk_eth_soc: 9K jumbo frame support
Date: Sun, 22 Nov 2026 21:05:18 +0200	[thread overview]
Message-ID: <patch-db1bbade1b6d0ed25afcb4f551133e85@loljews.com> (raw)
In-Reply-To: <20261121164714.5b0ae08f@kernel.org>

On Sat, Nov 21, 2026 at 04:47:14PM -0800, Jakub Kicinski wrote:
> Please use git send-email or b4 to send patches.
> You submitted patches with a date which looks 1 week old.

Right, thanks for pointing it out.  My sending helper copied the Date
from the format-patch output, which is the commit author date; the
series was rebased before this posting, so the mails carried dates from
the previous revision.  I have fixed it to stamp every mail with the
send time, and will use b4 or git send-email for the next revision.


      reply	other threads:[~2026-11-22 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 19:55 [PATCH net-next v7 0/3] net: ethernet: mtk_eth_soc: 9K jumbo frame support Sandeep Haemoon
2026-11-13 22:34 ` [PATCH net-next v7 1/3] net: ethernet: mtk_eth_soc: fix the RX Sandeep Haemoon
2026-11-21 20:21   ` netdev-bot+sashiko
2026-11-13 22:34 ` [PATCH net-next v7 2/3] net: ethernet: mtk_eth_soc: skip page_pool Sandeep Haemoon
2026-11-21 20:22   ` netdev-bot+sashiko
2026-11-13 22:40 ` [PATCH net-next v7 3/3] net: ethernet: mtk_eth_soc: add 9K jumbo Sandeep Haemoon
2026-11-21 20:22   ` netdev-bot+sashiko
2026-11-17 19:57 ` [PATCH net-next v7 0/3] net: ethernet: mtk_eth_soc: 9K jumbo frame support netdev-bot+sinfo
2026-11-22 19:05   ` Sandeep Haemoon
2026-11-22  0:47 ` Jakub Kicinski
2026-11-22 19:05   ` Sandeep Haemoon [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=patch-db1bbade1b6d0ed25afcb4f551133e85@loljews.com \
    --to=sandeeph@loljews.com \
    --cc=kuba@kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox