linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jsorensen@fb.com>
To: Eric Biggers <ebiggers@kernel.org>,
	Jes Sorensen <jes.sorensen@gmail.com>
Cc: <linux-fscrypt@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH v2 0/2] fsverity-utils Makefile fixes
Date: Wed, 20 May 2020 17:04:58 -0400	[thread overview]
Message-ID: <4417919f-01f4-4d4f-1a10-7dc24ba166b1@fb.com> (raw)
In-Reply-To: <20200520210335.GA218475@gmail.com>

On 5/20/20 5:03 PM, Eric Biggers wrote:
> On Wed, May 20, 2020 at 04:08:09PM -0400, Jes Sorensen wrote:
>> From: Jes Sorensen <jsorensen@fb.com>
>>
>> Hi
>>
>> This addresses the comments to the previous version of these Makefile
>> changes.
>>
>> Let me know if you have any additional issues with it?
>>
>> I'd really love to see an official release soon that includes these
>> changes, which I can point to when submitting the RPM patches. Any
>> chance of doing 1.1 or something like that?
>>
>> Cheers,
>> Jes
> 
> I'll release v1.1 after I merge the libfsverity patches, but I need to look over
> everything again first before committing to a stable API.  I'll try to get to it
> this weekend; I'm also busy with a lot of other things.
> 
> Also, could you look over my patches and leave your Reviewed-by?  I expected
> that you'd have a few more comments.

Sounds good, I'll go over them again and add the Reviewed-by lines once
I'm through.

Cheers,
Jes

      reply	other threads:[~2020-05-20 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 20:08 [PATCH v2 0/2] fsverity-utils Makefile fixes Jes Sorensen
2020-05-20 20:08 ` [PATCH 1/2] Fix Makefile to delete objects from the library on make clean Jes Sorensen
2020-05-20 20:08 ` [PATCH 2/2] Let package manager override CFLAGS and CPPFLAGS Jes Sorensen
2020-05-20 21:06   ` Eric Biggers
2020-05-20 21:20     ` Jes Sorensen
2020-05-20 21:03 ` [PATCH v2 0/2] fsverity-utils Makefile fixes Eric Biggers
2020-05-20 21:04   ` Jes Sorensen [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=4417919f-01f4-4d4f-1a10-7dc24ba166b1@fb.com \
    --to=jsorensen@fb.com \
    --cc=ebiggers@kernel.org \
    --cc=jes.sorensen@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=linux-fscrypt@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;
as well as URLs for NNTP newsgroup(s).