mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
	"Hook, Gary" <Gary.Hook@amd.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"Hook, Gary" <Gary.Hook@amd.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	"Singh, Brijesh" <brijesh.singh@amd.com>
Subject: Re: [PATCH 1/2] Fix static checker warning
Date: Thu, 20 Sep 2018 15:43:48 +0000	[thread overview]
Message-ID: <7aa02bf8-8813-98e5-6729-af4ae63da7d0@amd.com> (raw)
In-Reply-To: <20180919135741.5icpyesntcfbgtcr@mwanda>

On 9/19/2018 8:57 AM, Dan Carpenter wrote:
> Sounds reasonable.  The subject needs a subsystem prefix and it might
> be better to make it more specific.  Like so:
>
> [PATCH 1/2] crypto: ccp - potential uninitialized variable

I'll put out a v2 with the subjects fixed.

Thanks.

>
> I don't know if Herbert fixes those things up himself normally?
>
> regards,
> dan carpenter
>


  reply	other threads:[~2018-09-20 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 22:32 [PATCH 0/2] Miscellaneous SEV fixes Janakarajan Natarajan
2018-09-14 22:32 ` [PATCH 1/2] Fix static checker warning Janakarajan Natarajan
2018-09-19 13:40   ` Gary R Hook
2018-09-19 13:57     ` Dan Carpenter
2018-09-20 15:43       ` Natarajan, Janakarajan [this message]
2018-09-21  4:52         ` Herbert Xu
2018-09-14 22:32 ` [PATCH 2/2] Allow SEV firmware to be chosen based on Family and Model Janakarajan Natarajan
2018-09-19 13:29   ` Lendacky, Thomas
2018-09-19 13:41   ` Gary R Hook
2018-09-21  5:46 ` [PATCH 0/2] Miscellaneous SEV fixes Herbert Xu

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=7aa02bf8-8813-98e5-6729-af4ae63da7d0@amd.com \
    --to=janakarajan.natarajan@amd.com \
    --cc=Gary.Hook@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=brijesh.singh@amd.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®