From: Markus Elfring <Markus.Elfring@web.de>
To: Paolo Perego <pperego@suse.de>, linux-wireless@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Benjamin Berg <benjamin.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@kernel.org>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Shaul Triebitz <shaul.triebitz@intel.com>,
Yedidya Benshimol <yedidya.ben.shimol@intel.com>
Subject: Re: wireless: Fix a dereference before null check issue
Date: Fri, 22 Nov 2024 08:50:18 +0100 [thread overview]
Message-ID: <d01e7201-1a7d-4097-b9fb-7f9878591e31@web.de> (raw)
In-Reply-To: <q3pul7n2axag5xcxzzjjrhwlu3m3vh64bz4ln6dt7w757z47hk@byhyujhanky4>
> Oops, I'm so sorry this was already fixed.
It can occasionally happen that some contributors would like to adjust
the same source code places somehow.
> In Coverity dashboard the
> item seemed to be still open.
It might occasionally be unclear with which delay corresponding items
will be synchronised.
> Apart from that, did I followed the right steps?
Partly, yes.
> Was my submission good
> enough? (I'm new to kernel hacking and I'm still in the learning phase)
I find details improvable.
1. Change description
2. Patch subject
Regards,
Markus
next prev parent reply other threads:[~2024-11-22 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 17:02 [PATCH] drivers:wireless: " Paolo Perego
2024-11-21 17:28 ` Johannes Berg
2024-11-21 17:35 ` Paolo Perego
2024-11-21 17:40 ` Johannes Berg
2024-11-22 7:50 ` Markus Elfring [this message]
2024-11-22 7:25 ` wireless: " Markus Elfring
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=d01e7201-1a7d-4097-b9fb-7f9878591e31@web.de \
--to=markus.elfring@web.de \
--cc=benjamin.berg@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=pperego@suse.de \
--cc=shaul.triebitz@intel.com \
--cc=yedidya.ben.shimol@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
all inboxes | Powered by JetHome®