From: Eric Biggers <ebiggers@kernel.org>
To: Jes Klinke <jbk@google.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, linux-integrity@vger.kernel.org
Subject: Re: PATCH: Google security chip, additional DID:VID
Date: Mon, 4 Apr 2022 16:58:43 -0700 [thread overview]
Message-ID: <YkuGMzkivenBgSmO@sol.localdomain> (raw)
In-Reply-To: <CANMTAZR-7UEeNXx0Syd+eS7L1K9xc6X9L01UoT50xpDPu4+xVQ@mail.gmail.com>
On Mon, Apr 04, 2022 at 04:44:57PM -0700, Jes Klinke wrote:
> I have sent a separate email to the list with the patch, in which I
> have cut out the long explanation, added Signed-off-by, and added the
> delimiter for the diff. Let me know if there are anything else I have
> overlooked.
>
> Regards
> Jes
Please use 'git format-patch', as submitting-patches.rst recommends. Also run
scripts/checkpatch.pl on your patch. That will ensure that your patch is in the
correct format. As-is, your patch doesn't apply.
- Eric
prev parent reply other threads:[~2022-04-05 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 23:00 PATCH: Google security chip, additional DID:VID Jes Klinke
2022-04-04 23:21 ` Eric Biggers
2022-04-04 23:44 ` Jes Klinke
2022-04-04 23:58 ` Eric Biggers [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=YkuGMzkivenBgSmO@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jbk@google.com \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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