All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH 0/4] crypto: refactor sha code
Date: Sat, 23 Nov 2019 09:25:44 +0100	[thread overview]
Message-ID: <3fccdf1a-1b4f-a52c-f362-c4e0105d2a5f@tessares.net> (raw)
In-Reply-To: 38edc6d00633c8617240d1e2c099339ff3e576be.camel@linux.intel.com

[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]

Hi Peter, Paolo,

On 22/11/2019 19:16, Peter Krystad wrote:
> 
> Hi Paolo & Matt -
> 
> On Fri, 2019-11-22 at 17:47 +0100, Matthieu Baerts wrote:
>> Hi Paolo,
>>
>> On 22/11/2019 17:41, Paolo Abeni wrote:
>>> On Fri, 2019-11-22 at 17:26 +0100, Matthieu Baerts wrote:
>>>> Hi Paolo,
>>>>
>>>> On 22/11/2019 15:30, Paolo Abeni wrote:
>>>>> On Fri, 2019-11-22 at 15:26 +0100, Paolo Abeni wrote:
>>>>>> patch 1/4 refactor the crypto code to make it easier transitioning to
>>>>>> sha256. It includes feedback from Peter about helper renaming.
>>>>
>>>> Thank you for this new version!
>>>>
>>>> It looks good to me after a very very quick review (but the first patch
>>>> is hard to read).
>>>>
>>>>>> The following patches update the rest of the tree to the new helper name.
>>>>>> Overall this should generate 3 conflicts along the rebase.
>>>>>
>>>>> Addendum:
>>>>>
>>>>> The squashed tree is avaialble here:
>>>>>
>>>>> https://github.com/pabeni/mptcp/tree/sha_cleanup_2
>>>>>
>>>>> I verified the new code ensuring that the genrated seq number matched
>>>>> the expectation of the wireshark dissector.
>>>>
>>>> Great!
>>>>
>>>> Because it looks OK and you checked different stuffs, do you want me to:
>>>> - replace the tree with the commits from your branch? (if needed, we can
>>>> of course do other fixes later)
>>>> - stop the CI job, wait for a proper review and then replace the tree?
>>>> - or wait for a proper review and then I apply the changes, looking at
>>>> your branch in case of conflict but doing all of that with TopGit to
>>>> ease the review? :)
>>>
>>> I think the first 2 options are the better ones.
>>>
>>> It would be nice if someone give this an additional review ;)
>>
>> OK for me!
>>
>> I just paused the CI job then. I hope not for too long :-)
> 
> This looks good to me. I'll double-check interop with mptcp.org after it is
> merged.

Great, thank you for the patches and the reviews!

I just recreated the tree using Paolo's branch. Tests are still OK!

Syncing with the latest net-next now and checking that all commits can 
still compile.

Cheers,
Matt
-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium

             reply	other threads:[~2019-11-23  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23  8:25 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-26  9:03 [MPTCP] Re: [PATCH 0/4] crypto: refactor sha code Matthieu Baerts
2019-11-26  1:40 Peter Krystad
2019-11-22 18:16 Peter Krystad
2019-11-22 16:47 Matthieu Baerts
2019-11-22 16:41 Paolo Abeni
2019-11-22 16:26 Matthieu Baerts
2019-11-22 14:30 Paolo Abeni

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=3fccdf1a-1b4f-a52c-f362-c4e0105d2a5f@tessares.net \
    --to=unknown@example.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 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.