From: yalin wang <yalin.wang2010@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Kershner <david.kershner@unisys.com>,
tj@kernel.org, laijs@cn.fujitsu.com, nacc@linux.vnet.ibm.com,
nhorman@redhat.com, mingo@redhat.com,
linux-kernel@vger.kernel.org, jes.sorensen@redhat.com,
sparmaintainer@unisys.com
Subject: Re: [PATCH v2] kthread: Export kthread functions
Date: Thu, 30 Jul 2015 11:48:17 +0800 [thread overview]
Message-ID: <BC1DBE23-DF3E-49C1-BE59-A81EC98F5B1A@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507291233470.3825@nanos>
> On Jul 29, 2015, at 18:34, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, 28 Jul 2015, Andrew Morton wrote:
>
>> On Tue, 28 Jul 2015 11:59:01 -0400 David Kershner <david.kershner@unisys.com> wrote:
>>
>>> The s-Par visornic driver, currently in staging, processes a queue
>>> being serviced by the an s-Par service partition. We can get a message
>>> that something has happened with the Service Partition, when that
>>> happens, we must not access the channel until we get a message that the
>>> service partition is back again.
>>>
>>> The visornic driver has a thread for processing the channel, when we
>>> get the message, we need to be able to park the thread and then resume
>>> it when the problem clears.
>>>
>>> We can do this with kthread_park and unpark but they are not exported
>>> from the kernel, this patch exports the needed functions.
>>>
>>> Signed-off-by: David Kershner <david.kershner@unisys.com>
>>
>> Please accumulate the acked-by's and reviewed-by's in the changelog as
>> they are received. I presently have
>>
>> Acked-by: Ingo Molnar <mingo@kernel.org>
>> Acked-by: Neil Horman <nhorman@tuxdriver.com>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Richard Weinberger <richard.weinberger@gmail.com>
>> Cc: Tejun Heo <tj@kernel.org>
>>
>>
>> I'll scoot this into mainline probably this week to make life simpler
>> for the various trees.
>
i am curious why not make some tiny functions to be inline ?
so that don’t need EXPORT_SYMOBLS , shrink the kernel size.
Thanks
next prev parent reply other threads:[~2015-07-30 3:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 22:45 [PATCH] " David Kershner
2015-07-24 23:14 ` Neil Horman
2015-07-25 12:05 ` Richard Weinberger
2015-07-26 0:50 ` Kershner, David A
2015-07-26 8:46 ` Thomas Gleixner
2015-07-27 15:45 ` Ingo Molnar
2015-07-27 15:49 ` Neil Horman
2015-07-27 16:01 ` Kershner, David A
2015-07-28 15:59 ` [PATCH v2] " David Kershner
2015-07-28 21:27 ` Andrew Morton
2015-07-29 10:34 ` Thomas Gleixner
2015-07-30 3:48 ` yalin wang [this message]
2015-07-30 12:02 ` Neil Horman
2015-07-31 4:16 ` yalin wang
2015-07-31 8:19 ` Thomas Gleixner
2015-07-31 14:14 ` Thomas Gleixner
2015-08-01 7:12 ` yalin wang
2015-08-01 7:20 ` Thomas Gleixner
2015-08-01 13:32 ` Neil Horman
2015-08-03 2:23 ` yalin wang
2015-08-03 2:42 ` Jes Sorensen
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=BC1DBE23-DF3E-49C1-BE59-A81EC98F5B1A@gmail.com \
--to=yalin.wang2010@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david.kershner@unisys.com \
--cc=jes.sorensen@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nacc@linux.vnet.ibm.com \
--cc=nhorman@redhat.com \
--cc=sparmaintainer@unisys.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®