From: Johannes Berg <johannes@sipsolutions.net>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: linux-wireless@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH wireless] wifi: nl80211: call kfree without a NULL
Date: Mon, 20 Oct 2025 09:42:59 +0200 [thread overview]
Message-ID: <cee56c0828cbb555578aa09dfdf4bc9fa54f8f44.camel@sipsolutions.net> (raw)
In-Reply-To: <20251019120040.c62e9b9a0eec.Ice40c7be5447410ee74d48a6eeef1711c719c55f@changeid>
That subject doesn't make sense?
johannes
prev parent reply other threads:[~2025-10-20 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 9:00 [PATCH wireless] wifi: nl80211: call kfree without a NULL Miri Korenblit
2025-10-20 7:42 ` Johannes Berg [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=cee56c0828cbb555578aa09dfdf4bc9fa54f8f44.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).