linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vikas Gupta <vikas.gupta@broadcom.com>
To: David Miller <davem@davemloft.net>
Cc: zajec5@gmail.com,
	Sheetal Tigadoli <sheetal.tigadoli@broadcom.com>,
	netdev@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, sumit.garg@linaro.org,
	Vasundhara Volam <vasundhara-v.volam@broadcom.com>,
	Vikram Prakash <vikram.prakash@broadcom.com>
Subject: RE: [PATCH INTERNAL v2] firmware: tee_bnxt: Fix multiple call to tee_client_close_context
Date: Mon, 6 Jan 2020 11:55:22 +0530	[thread overview]
Message-ID: <96059280a7ebeb4e1ec92c78d053ccfe@mail.gmail.com> (raw)
In-Reply-To: <20200105.144746.2055568145717937218.davem@davemloft.net>

 "INTERNAL" and version "v2" added accidently. Please ignore this. I`ll
send updated patch.

-----Original Message-----
From: David Miller [mailto:davem@davemloft.net]
Sent: Monday, January 06, 2020 4:18 AM
To: vikas.gupta@broadcom.com
Cc: zajec5@gmail.com; sheetal.tigadoli@broadcom.com;
netdev@vger.kernel.org; linux-mips@vger.kernel.org;
linux-kernel@vger.kernel.org; sumit.garg@linaro.org;
vasundhara-v.volam@broadcom.com; vikram.prakash@broadcom.com
Subject: Re: [PATCH INTERNAL v2] firmware: tee_bnxt: Fix multiple call to
tee_client_close_context


What does "INTERNAL" mean in these patch Subject lines?

      reply	other threads:[~2020-01-06  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 16:20 [PATCH INTERNAL v2] firmware: tee_bnxt: Fix multiple call to tee_client_close_context Vikas Gupta
2020-01-03 16:20 ` [PATCH INTERNAL v2] firmware: tee_bnxt: Reduce shm mem size to 4K Vikas Gupta
2020-01-05 22:47 ` [PATCH INTERNAL v2] firmware: tee_bnxt: Fix multiple call to tee_client_close_context David Miller
2020-01-06  6:25   ` Vikas Gupta [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=96059280a7ebeb4e1ec92c78d053ccfe@mail.gmail.com \
    --to=vikas.gupta@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sheetal.tigadoli@broadcom.com \
    --cc=sumit.garg@linaro.org \
    --cc=vasundhara-v.volam@broadcom.com \
    --cc=vikram.prakash@broadcom.com \
    --cc=zajec5@gmail.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).