From: Jim Rees <rees@umich.edu>
To: Tom Gundersen <teg@jklm.no>
Cc: linux-nfs@vger.kernel.org, "Steve Dickson" <steved@redhat.com>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>
Subject: Re: [PATCH] rpcbind: add support for systemd socket activation
Date: Thu, 22 Dec 2011 21:40:22 -0500 [thread overview]
Message-ID: <20111223024022.GA9044@umich.edu> (raw)
In-Reply-To: <1324602327-1789-1-git-send-email-teg@jklm.no>
Might it be time to break up init_transport? I see you're already using
some non-standard indentation to keep the AF_INET6 case from dropping off
the right side of the screen.
next prev parent reply other threads:[~2011-12-23 2:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:18 [PATCH v2] rpcbind: add support for systemd socket activation Tom Gundersen
2011-12-15 14:54 ` [systemd-devel] " Lennart Poettering
2011-12-19 23:42 ` Cristian Rodriguez
2011-12-23 1:05 ` [PATCH] " Tom Gundersen
2011-12-23 1:34 ` Cristian Rodríguez
2011-12-23 2:40 ` Jim Rees [this message]
2012-02-01 11:47 ` Tom Gundersen
2012-02-01 15:32 ` Chuck Lever
2012-02-01 16:37 ` Tom Gundersen
2012-02-01 18:16 ` Chuck Lever
2012-02-01 19:48 ` Tom Gundersen
2012-02-01 21:45 ` Lennart Poettering
2012-02-01 22:03 ` Chuck Lever
2012-02-01 22:30 ` Lennart Poettering
2012-02-03 10:58 ` [Libtirpc-devel] " Ian Kent
2012-02-03 17:03 ` Chuck Lever
2012-02-04 8:59 ` [PATCH v2] " Tom Gundersen
2012-02-01 19:59 ` [PATCH] " Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2014-11-25 17:05 [PATCH] rpcbind: systemd socket activation (v2) Steve Dickson
2014-11-25 17:05 ` [PATCH] rpcbind: add support for systemd socket activation Steve Dickson
2014-11-26 12:48 ` Steve Dickson
2014-11-21 16:43 [PATCH] rpcbind: " Steve Dickson
2014-11-21 16:43 ` [PATCH] rpcbind: add support for " Steve Dickson
2010-07-19 2:19 Lennart Poettering
2010-07-21 17:56 ` Chuck Lever
2010-07-21 21:56 ` Lennart Poettering
2010-07-23 15:13 ` Chuck Lever
2010-07-23 16:27 ` Lennart Poettering
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=20111223024022.GA9044@umich.edu \
--to=rees@umich.edu \
--cc=crrodriguez@opensuse.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=teg@jklm.no \
/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).