DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
To: 20260603041557.115956-1-denserg.edu@gmail.com
Cc: dev@dpdk.org, Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>,
	stable@dpdk.org, denserg.edu@gmail.com
Subject: RE: Inquiry about status of accepted patch net/bnxt/tf_core: fix null deref on pool use allocation
Date: Thu, 9 Jul 2026 12:09:35 -0400	[thread overview]
Message-ID: <6456b41e6775851acdf996127afffc35@mail.gmail.com> (raw)
In-Reply-To: <EAYPR13MB7316899D71B96849EDFB8BC0B4F2F02@EAYPR13MB731689.namprd13.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Hi Simakov,

Will get back once I check with the maintainers.

Thanks,
Kishore


-----Original Message-----
From: Simakov Aleksey <bigalex934@gmail.com>
Sent: Tuesday, July 7, 2026 4:05 AM
To: kishore.padmanabha@broadcom.com
Cc: dev@dpdk.org; ajit.khaparde@broadcom.com; stable@dpdk.org;
denserg.edu@gmail.com
Subject: Inquiry about status of accepted patch net/bnxt/tf_core: fix null
deref on pool use allocation

Hello!

I hope this message finds you well.

I am writing to inquire about the status of patch
https://patches.dpdk.org/project/dpdk/patch/20260603041557.115956-1-denser
g.edu@gmail.com/
It was marked as "Accepted" in Patchwork over a month ago, but I noticed
that it has not yet been merged into any of the DPDK branches.

Could you please clarify the current status of this patch?

Thank you for your time

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5493 bytes --]

      reply	other threads:[~2026-07-09 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  8:04 Inquiry about status of accepted patch net/bnxt/tf_core: fix null deref on pool use allocation Simakov Aleksey
2026-07-09 16:09 ` Kishore Padmanabha [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=6456b41e6775851acdf996127afffc35@mail.gmail.com \
    --to=kishore.padmanabha@broadcom.com \
    --cc=20260603041557.115956-1-denserg.edu@gmail.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=denserg.edu@gmail.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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