All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 2/3] kernel/SRCU: provide a static initializer
Date: Mon, 08 Apr 2013 12:03:19 +0200	[thread overview]
Message-ID: <516295E7.70200@linutronix.de> (raw)
In-Reply-To: <515E7B79.2020707@cn.fujitsu.com>

On 04/05/2013 09:21 AM, Lai Jiangshan wrote:
> Hi, Sebastian

Hi Lai,

> I don't want to expose __SRCU_STRUCT_INIT(),
> due to it has strong coupling with the percpu array.
> 
> I hope other structure which uses SRCU should use init_srcu_struct().

I need a static initialization for this kind. Patch #3 shows one
example I have another one pending for crypto.
Do you have any idea how I could get it done without this? Do you want
to move/merge header files?

> 
> Thanks,
> Lai

Sebastian

  reply	other threads:[~2013-04-08 10:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 14:16 [PATCH 1/3] kernel/srcu: merge common code into a macro Sebastian Andrzej Siewior
2013-03-19 14:16 ` [PATCH 2/3] kernel/SRCU: provide a static initializer Sebastian Andrzej Siewior
2013-04-05  7:21   ` Lai Jiangshan
2013-04-08 10:03     ` Sebastian Andrzej Siewior [this message]
2013-04-09  1:09       ` Lai Jiangshan
2013-04-11 17:04         ` Sebastian Andrzej Siewior
2013-04-12  2:56           ` Lai Jiangshan
2013-04-16 18:20             ` Paul E. McKenney
2013-03-19 14:16 ` [PATCH 3/3] cpufreq: use static initializer for the SRCU notifier Sebastian Andrzej Siewior
2013-03-19 16:22 ` [PATCH 1/3] kernel/srcu: merge common code into a macro Joe Perches
2013-03-19 18:15   ` Sebastian Andrzej Siewior
2013-04-05  7:21 ` Lai Jiangshan
2013-04-08 10:05   ` Sebastian Andrzej Siewior

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=516295E7.70200@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.