Linux wireless drivers development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Brendan Jackman <jackmanb@google.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Stanislaw Gruszka <stf_xl@wp.pl>,
	Alexander Potapenko <glider@google.com>,
	Marco Elver <elver@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Allison Henderson <allison.henderson@oracle.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
	<linux-wireless@vger.kernel.org>, <kasan-dev@googlegroups.com>,
	<linux-mm@kvack.org>, <netdev@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <rds-devel@oss.oracle.com>
Subject: Re: [PATCH v2 0/4] treewide: fixup gfp_t printks
Date: Tue, 12 May 2026 14:05:32 -0700	[thread overview]
Message-ID: <20260512140532.f16379be75ab006f2cca4747@linux-foundation.org> (raw)
In-Reply-To: <DIGPS83BGEGA.5I7VLH8TV7XE@google.com>

On Tue, 12 May 2026 12:58:20 +0000 Brendan Jackman <jackmanb@google.com> wrote:

> On Thu Mar 26, 2026 at 12:31 PM UTC, Brendan Jackman wrote:
> > This patchset used to be about switching gfp_t to unsigned long. That is
> > probably not gonna happen any more but while writing it I found these
> > cleanups that seem worthwhile regardless.
> >
> 
> ...
>
> Any chance someone can take these?

[2/4] is merged into the wireless tree (I assume) and the other three
are in mm.git's mm-unstable branch.


  reply	other threads:[~2026-05-12 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 12:31 [PATCH v2 0/4] treewide: fixup gfp_t printks Brendan Jackman
2026-03-26 12:31 ` [PATCH v2 1/4] drm/managed: Use special gfp_t format specifier Brendan Jackman
2026-03-26 12:31 ` [PATCH v2 2/4] iwlegacy: 3945-mac: Fixup allocation failure log Brendan Jackman
2026-03-27 11:45   ` Stanislaw Gruszka
2026-03-26 12:31 ` [PATCH v2 3/4] mm/kfence: Use special gfp_t format specifier Brendan Jackman
2026-03-26 12:32 ` [PATCH v2 4/4] net/rds: " Brendan Jackman
2026-04-02 17:16   ` Allison Henderson
2026-03-27 11:57 ` [PATCH v2 0/4] treewide: fixup gfp_t printks Stanislaw Gruszka
2026-05-12 12:58 ` Brendan Jackman
2026-05-12 21:05   ` Andrew Morton [this message]
2026-05-13  9:11     ` Brendan Jackman

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=20260512140532.f16379be75ab006f2cca4747@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=airlied@gmail.com \
    --cc=allison.henderson@oracle.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=horms@kernel.org \
    --cc=jackmanb@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rds-devel@oss.oracle.com \
    --cc=simona@ffwll.ch \
    --cc=stf_xl@wp.pl \
    --cc=tzimmermann@suse.de \
    /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