Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mike Rapoport <rppt@kernel.org>
Cc: 3chas3@gmail.com, duncan.sands@free.fr,
	gregkh@linuxfoundation.org, johan@kernel.org,
	akpm@linux-foundation.org, david@kernel.org, willy@infradead.org,
	vbabka@kernel.org, accessrunner-general@lists.sourceforge.net,
	linux-atm-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] USB: replace page allocator calls with kmalloc()
Date: Thu, 03 Sep 2026 02:00:11 +0000	[thread overview]
Message-ID: <178840081114.3041656.13596134068099743678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260830-usb-v1-0-aa349c302246@kernel.org>

Hello:

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

On Sun, 30 Aug 2026 11:10:36 +0300 you wrote:
> This is a (small) part of larger work of replacing page allocator calls
> with kmalloc.
> 
> My initial intention a few month ago was to remove ugly casts [1], but then
> willy pointed out that Linus objected to something like this [2] and it
> looks like more than a decade old technical debt.
> 
> [...]

Here is the summary with links:
  - [1/4] USB: usbfs: replace __get_free_page() with kmalloc()
    (no matching commit)
  - [2/4] USB: cxacru: replace __get_free_page() with kmalloc()
    https://git.kernel.org/netdev/net-next/c/a3b4826138d4
  - [3/4] USB: speedtch: replace __get_free_page() with kmalloc()
    https://git.kernel.org/netdev/net-next/c/534b18813974
  - [4/4] USB: serial: wwan: replace __get_free_page() with kmalloc()
    (no matching commit)

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-03  2:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30  8:10 [PATCH 0/4] USB: replace page allocator calls with kmalloc() Mike Rapoport (Microsoft)
2026-08-30  8:10 ` [PATCH 1/4] USB: usbfs: replace __get_free_page() " Mike Rapoport (Microsoft)
2026-08-31 13:27   ` Oliver Neukum
2026-08-31 14:24     ` Mike Rapoport
2026-08-31 14:30     ` Alan Stern
2026-09-02 14:36       ` Vlastimil Babka (SUSE)
2026-08-30  8:10 ` [PATCH 2/4] USB: cxacru: " Mike Rapoport (Microsoft)
2026-08-30  8:10 ` [PATCH 3/4] USB: speedtch: " Mike Rapoport (Microsoft)
2026-08-30  8:10 ` [PATCH 4/4] USB: serial: wwan: " Mike Rapoport (Microsoft)
2026-09-03  2:00 ` patchwork-bot+netdevbpf [this message]
2026-09-03  6:20   ` [PATCH 0/4] USB: replace page allocator calls " Johan Hovold

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=178840081114.3041656.13596134068099743678.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=3chas3@gmail.com \
    --cc=accessrunner-general@lists.sourceforge.net \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=duncan.sands@free.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.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