From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Andrey Pronin <apronin@chromium.org>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
groeck@chromium.org, smbarber@chromium.org,
dianders@chromium.org
Subject: Re: [PATCH 1/2] tpm: define constants for tpm2 properties
Date: Thu, 14 Jul 2016 21:08:10 -0600 [thread overview]
Message-ID: <20160715030810.GB9347@obsidianresearch.com> (raw)
In-Reply-To: <1468544838-9990-2-git-send-email-apronin@chromium.org>
On Thu, Jul 14, 2016 at 06:07:17PM -0700, Andrey Pronin wrote:
> Change-Id: I47cb1793736781fbea93e5bf80b783e0ac9e8628
These commit messages are no good, generally for all your
patches. Drop the internal change-id and provide a suitable
description.
Do not add dead code to the kernel, so this patch should be in a
series that actually uses the new constants.
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Andrey Pronin <apronin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
smbarber-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
groeck-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH 1/2] tpm: define constants for tpm2 properties
Date: Thu, 14 Jul 2016 21:08:10 -0600 [thread overview]
Message-ID: <20160715030810.GB9347@obsidianresearch.com> (raw)
In-Reply-To: <1468544838-9990-2-git-send-email-apronin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
On Thu, Jul 14, 2016 at 06:07:17PM -0700, Andrey Pronin wrote:
> Change-Id: I47cb1793736781fbea93e5bf80b783e0ac9e8628
These commit messages are no good, generally for all your
patches. Drop the internal change-id and provide a suitable
description.
Do not add dead code to the kernel, so this patch should be in a
series that actually uses the new constants.
Jason
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
next prev parent reply other threads:[~2016-07-15 3:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:07 [PATCH 0/2] tpm: better support for 32-bit tpm2 properties Andrey Pronin
2016-07-15 1:07 ` Andrey Pronin
2016-07-15 1:07 ` [PATCH 1/2] tpm: define constants for " Andrey Pronin
2016-07-15 1:07 ` Andrey Pronin
2016-07-15 3:08 ` Jason Gunthorpe [this message]
2016-07-15 3:08 ` Jason Gunthorpe
2016-07-18 18:58 ` Jarkko Sakkinen
2016-07-18 18:58 ` Jarkko Sakkinen
2016-07-15 1:07 ` [PATCH 2/2] tpm: fix byte-order for the value read by tpm2_get_tpm_pt Andrey Pronin
2016-07-15 1:07 ` Andrey Pronin
2016-07-15 3:10 ` Jason Gunthorpe
2016-07-15 3:17 ` Andrey Pronin
2016-07-15 3:17 ` Andrey Pronin
2016-07-15 3:35 ` Jason Gunthorpe
2016-07-15 3:35 ` Jason Gunthorpe
2016-07-15 19:31 ` Andrey Pronin
2016-07-15 19:39 ` Jason Gunthorpe
2016-07-18 19:05 ` Jarkko Sakkinen
2016-07-18 19:05 ` Jarkko Sakkinen
2016-07-18 19:04 ` Jarkko Sakkinen
2016-07-18 19:04 ` Jarkko Sakkinen
2016-07-18 19:09 ` Jarkko Sakkinen
2016-07-18 19:09 ` Jarkko Sakkinen
2016-07-18 19:13 ` Andrey Pronin
2016-07-18 19:13 ` Andrey Pronin
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=20160715030810.GB9347@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=apronin@chromium.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=smbarber@chromium.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.