netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: <davem@davemloft.net>
Cc: <jon.maloy@ericsson.com>, <Paul.Gortmaker@windriver.com>,
	<erik.hugne@ericsson.com>, <netdev@vger.kernel.org>,
	<tipc-discussion@lists.sourceforge.net>,
	<wangweidong1@huawei.com>
Subject: [PATCH net 0/2] tipc: clean up components initialization code
Date: Thu, 20 Feb 2014 11:32:48 +0800	[thread overview]
Message-ID: <1392867171-31020-1-git-send-email-ying.xue@windriver.com> (raw)

In this series, we will fix a regression issue involved by commit
6e967adf7(tipc: relocate common functions from media to bearer)
But before the issue is fixed, we firstly adjust the process of
components initialization so as to remove all enabled flags from
necessary tipc components. Otherwise, without the change, we also
have to add an extra enabled flag into bearer layer indicating
whether bearer setup is finshed or not.

Ying Xue (2):
  tipc: remove all enabled flags from all tipc components
  tipc: make bearer set up in module insertion stage

 net/tipc/bearer.c     |    7 +++-
 net/tipc/config.c     |    2 +-
 net/tipc/core.c       |  109 ++++++++++++++++++++++++++-----------------------
 net/tipc/core.h       |    1 -
 net/tipc/name_table.c |    3 --
 net/tipc/netlink.c    |    8 ----
 net/tipc/ref.c        |    3 --
 net/tipc/server.c     |    5 ---
 net/tipc/server.h     |    2 -
 net/tipc/socket.c     |    8 ----
 10 files changed, 66 insertions(+), 82 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2014-02-20  3:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  3:32 Ying Xue [this message]
2014-02-20  3:32 ` [PATCH net 1/2] tipc: remove all enabled flags from all tipc components Ying Xue
2014-02-20  3:32 ` [PATCH net 2/2] tipc: make bearer set up in module insertion stage Ying Xue
2014-02-22  5:01 ` [PATCH net 0/2] tipc: clean up components initialization code David Miller

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=1392867171-31020-1-git-send-email-ying.xue@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=Paul.Gortmaker@windriver.com \
    --cc=davem@davemloft.net \
    --cc=erik.hugne@ericsson.com \
    --cc=jon.maloy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=wangweidong1@huawei.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).