From: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: leon@kernel.org, Selvin Xavier <selvin.xavier@broadcom.com>,
linux-rdma@vger.kernel.org
Subject: RE: [PATCH for-rc] RDMA/core: Fix GID entry ref leak when create_ah fails
Date: Fri, 24 Mar 2023 20:42:25 +0530 [thread overview]
Message-ID: <b56efc58da3c2bd2a7d0de6d61ec02c4@mail.gmail.com> (raw)
In-Reply-To: <ZB21phfIzgJlTlYk@ziepe.ca>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
On Wed, Mar 22, 2023 at 10:21:40PM -0700, Saravanan Vajravel wrote:
> This electronic communication and the information and any files
> transmitted with it, or attached to it, are confidential and are
> intended solely for the use of the individual or entity to whom it is
> addressed and may contain information that is confidential, legally
> privileged, protected by privacy laws, or otherwise restricted from
> disclosure to anyone else. If you are not the intended recipient or
> the person responsible for delivering the e-mail to the intended
> recipient, you are hereby notified that any use, copying,
> distributing, dissemination, forwarding, printing, or copying of this
> e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer,
and destroy any printed copy of it.
> I have to throw out patches that have these trailers, please fix your
mailer
Oops! I will check and fix it.
> Jason
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4227 bytes --]
prev parent reply other threads:[~2023-03-24 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 5:21 [PATCH for-rc] RDMA/core: Fix GID entry ref leak when create_ah fails Saravanan Vajravel
2023-03-24 14:37 ` Jason Gunthorpe
2023-03-24 15:12 ` Saravanan Vajravel [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=b56efc58da3c2bd2a7d0de6d61ec02c4@mail.gmail.com \
--to=saravanan.vajravel@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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