From: David Miller <davem@davemloft.net>
To: agruenba@redhat.com
Cc: herbert@gondor.apana.org.au, cluster-devel@redhat.com,
tgraf@suug.ch, netdev@vger.kernel.org, tom@quantonium.net
Subject: Re: [PATCH 2/3] rhashtable: Add rhashtable_walk_curr
Date: Tue, 19 Dec 2017 09:35:37 -0500 (EST) [thread overview]
Message-ID: <20171219.093537.1970900952836204980.davem@davemloft.net> (raw)
In-Reply-To: <CAHc6FU5JLviUSt9SO3oXZfWRE5ScBZ7O2f+2YubPJwCxQGW-2g@mail.gmail.com>
From: Andreas Gruenbacher <agruenba@redhat.com>
Date: Tue, 19 Dec 2017 09:35:47 +0100
> By the way, git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> master doesn't merge cleanly with current mainline.
Yes, this is the case more often than not :-)
prev parent reply other threads:[~2017-12-19 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171218133122.29179-1-agruenba@redhat.com>
2017-12-18 13:31 ` [PATCH 2/3] rhashtable: Add rhashtable_walk_curr Andreas Gruenbacher
2017-12-18 23:38 ` Herbert Xu
2017-12-19 8:35 ` Andreas Gruenbacher
2017-12-19 14:35 ` David Miller [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=20171219.093537.1970900952836204980.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=tom@quantonium.net \
/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