Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754843AbbGYMFS (ORCPT ); Sat, 25 Jul 2015 08:05:18 -0400 Received: from mail-ob0-f171.google.com ([209.85.214.171]:35146 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753236AbbGYMFQ (ORCPT ); Sat, 25 Jul 2015 08:05:16 -0400 MIME-Version: 1.0 In-Reply-To: <1437777920-31156-1-git-send-email-david.kershner@unisys.com> References: <1437777920-31156-1-git-send-email-david.kershner@unisys.com> Date: Sat, 25 Jul 2015 14:05:15 +0200 Message-ID: Subject: Re: [PATCH] kthread: Export kthread functions From: Richard Weinberger To: David Kershner Cc: Andrew Morton , Tejun Heo , laijs@cn.fujitsu.com, nacc@linux.vnet.ibm.com, nhorman@redhat.com, Thomas Gleixner , Ingo Molnar , LKML , jes.sorensen@redhat.com, sparmaintainer@unisys.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1102 Lines: 27 On Sat, Jul 25, 2015 at 12:45 AM, David Kershner 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. Are you sure that you need these function? You would be the first user. Please see: https://lkml.org/lkml/2015/7/8/1150 -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/