All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] mdio-mux: fix typo "framwork" in comment
Date: Tue, 08 Sep 2026 01:00:11 +0000	[thread overview]
Message-ID: <178882921138.3227186.56921221399363588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904104107.12832-2-hemanth.selam@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri,  4 Sep 2026 16:11:04 +0530 you wrote:
> Correct "framwork" to "framework", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt.  Only touches comments, no
> code changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> 
> [...]

Here is the summary with links:
  - [1/2] mdio-mux: fix typo "framwork" in comment
    https://git.kernel.org/netdev/net-next/c/32ca12fbcf6b
  - [2/2] mii: fix typo "asymetric" in comment
    https://git.kernel.org/netdev/net-next/c/4e2554eab15a

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



  parent reply	other threads:[~2026-09-08  1:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260904104107.12832-1-hemanth.selam@gmail.com>
2026-09-04 10:41 ` [PATCH 1/2] mdio-mux: fix typo "framwork" in comment Hemanth Selam
2026-09-04 13:16   ` Andrew Lunn
2026-09-08  1:00   ` patchwork-bot+netdevbpf [this message]
2026-09-04 10:41 ` [PATCH 2/2] mii: fix typo "asymetric" " Hemanth Selam
2026-09-04 13:17   ` Andrew Lunn

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=178882921138.3227186.56921221399363588.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=hemanth.selam@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --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 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.