From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Joe Perches <joe@perches.com>,
Tushar Sugandhi <tusharsu@linux.microsoft.com>,
zohar@linux.ibm.com, skhan@linuxfoundation.org,
linux-integrity@vger.kernel.org
Cc: sashal@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] IMA: Update KBUILD_MODNAME for IMA files to ima
Date: Tue, 11 Feb 2020 09:36:07 -0800 [thread overview]
Message-ID: <cde01d57-99d0-34f7-41dd-5eb5a24b5037@linux.microsoft.com> (raw)
In-Reply-To: <225b88ac1abcb293bf9d55ca53009015b1baa81c.camel@perches.com>
On 2/10/20 7:09 PM, Joe Perches wrote:
Hi Joe,
> Series seems sensible, thanks Tushar.
>
> Next time you might choose to use
>
> git format-patch --cover-letter
>
> and write in the 0/n cover letter what the point
> of the patch series is.
>
I was the one who suggested that we may not need a cover letter and
instead provide the details in the patch description. We can include the
cover letter in the next update.
thanks,
-lakshmi
next prev parent reply other threads:[~2020-02-11 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 2:47 [PATCH v2 1/3] IMA: Update KBUILD_MODNAME for IMA files to ima Tushar Sugandhi
2020-02-11 2:47 ` [PATCH v2 2/3] IMA: Add log statements for failure conditions Tushar Sugandhi
2020-02-11 3:23 ` Joe Perches
2020-02-11 19:14 ` Tushar Sugandhi
2020-02-11 20:09 ` Joe Perches
2020-02-11 2:47 ` [PATCH v2 3/3] IMA: Add module name and base name prefix to log Tushar Sugandhi
2020-02-11 3:09 ` [PATCH v2 1/3] IMA: Update KBUILD_MODNAME for IMA files to ima Joe Perches
2020-02-11 17:36 ` Lakshmi Ramasubramanian [this message]
2020-02-11 17:55 ` Tushar Sugandhi
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=cde01d57-99d0-34f7-41dd-5eb5a24b5037@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=joe@perches.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tusharsu@linux.microsoft.com \
--cc=zohar@linux.ibm.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).