From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Yan Zheng <zyan@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH 2/3] net/ceph: do not define list_entry_next
Date: Wed, 18 Nov 2015 22:24:03 +0900 [thread overview]
Message-ID: <20151118132403.GA802@swordfish> (raw)
In-Reply-To: <CAOi1vP8u-zP6+7sSbAq7Vnutt5o=AKh-MdazC8fz-Vu++gypxw@mail.gmail.com>
On (11/18/15 14:13), Ilya Dryomov wrote:
[..]
>
> Someone beat you to it ;)
>
> https://github.com/ceph/ceph-client/commit/76b4a27faebb369c1c50df01ef08b614a2854fc5
Oh, OK then :) Thanks!
-ss
prev parent reply other threads:[~2015-11-18 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 12:13 [PATCH 2/3] net/ceph: do not define list_entry_next Sergey Senozhatsky
2015-11-18 13:13 ` Ilya Dryomov
2015-11-18 13:24 ` Sergey Senozhatsky [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=20151118132403.GA802@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=zyan@redhat.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).