Hi -

On 2016-02-10 at 17:09 'Kanoj Sarcar' via Akaros wrote:
> Port over linux 4.1.15 drivers/infiniband/core logic essential for
> kernel bypass NIC access. Slight edits to adapt to Akaros environment
> (#if exclusion of non essential code blocks, panic stubs etc),
> described in README file.
> 
> Most of the interlock logic with core kernel (mm/vfs etc) is captured
> in compat.[ch].
> 
> Signed-off-by: Kanoj Sarcar <[email protected]>

It looks like this patch replaces the one you sent earlier in the
evening.

For future reference, you can have git send-email reply to your
original email with --in-reply-to, which will make it more clear which
is the right patch.

Here's the relevant blob from git help send-email:

--in-reply-to=<identifier>
    Make the first mail (or all the mails with --no-thread)
    appear as a reply to the given Message-Id, which avoids
    breaking threads to provide a new patch series.

    The second and subsequent emails will be sent as replies
    according to the --[no]-chain-reply-to setting.

    So for example when --thread and --no-chain-reply-to are specified,
    the second and subsequent patches will be replies to the first one
    like in the illustration below where [PATCH v2 0/3] is in reply to
    [PATCH 0/2]:

    [PATCH 0/2] Here is what I did...
        [PATCH 1/2] Clean up and tests
        [PATCH 2/2] Implementation
        [PATCH v2 0/3] Here is a reroll
            [PATCH v2 1/3] Clean up
            [PATCH v2 2/3] New tests
            [PATCH v2 3/3] Implementation

The identifier is the Message-id from the original email.  In the case
of your original "Port over linux" commit, it was:

        Message-Id: <[email protected]>

As another note, you can use git send-email to send an entire patch
set, which is a collection of commits that logically work together for
an overall change.  If there are dependencies between commits, then
this is especially important.

This site has a nice overview of how to use git send-email:
https://www.freedesktop.org/wiki/Software/PulseAudio/HowToUseGitSendEmail/

I'll take a look at all of your patches today.  

Thanks,
Barret

-- 
You received this message because you are subscribed to the Google Groups 
"Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to