From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B05D2C79F8B for ; Mon, 5 Jan 2026 12:48:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kernelnewbies.org; s=mail; h=Content-Transfer-Encoding:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:Cc: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=fQxUOqpdoSmszpXbl0RYkDChamRufeZA62C5DKquuu0=; b=frf67pwTeZ9KtqtK3RWEuHIO0x GTqhPs18XLdfrv3S6SfJoF0RkFYhWoBM6U0X9oHvRoQQJmAgRtR0Y3F69PEvpG5Dv2eJSIKo3eCBS 42fCoZP/+YUWrW0U9DuS3TH8qI2wq37aZ25JekytTcfCF1mKkE/Fe+HOb8iwLACTskYXge13ESNVa w7I2rXXie12eFTuDTuK531kgz8JL7eELs4aQCHuLsENvO1vOswEyTRObS0YiHX2CIZbeePbUa2Xno ZW4xPXgOZpD/vT0RwL2V5Kfp3TUAb5onGb5iK4EPBtVFaPV/cD5VOr7tVewGUHAILeT6jzkEdO7M6 e0RtsyQw==; Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.97.1) (envelope-from ) id 1vck09-000000003jB-0S0T; Mon, 05 Jan 2026 07:48:02 -0500 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1vcjxx-000000003gc-1N1H for kernelnewbies@kernelnewbies.org; Mon, 05 Jan 2026 07:45:46 -0500 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id 5C55F441CA; Mon, 5 Jan 2026 12:45:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C28ECC116D0; Mon, 5 Jan 2026 12:45:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1767617144; bh=IZKyOSx9wwmTyup00UpyWuMegvrjajTmAkoAVhd9AHA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vkwukVRgUkqkryuAFDubYOsmOBcLnQro3g3deZH1NMackn9lal46t4AJ7whkwAm3z aFDc7yBepIhKxyKGXQP4t8rDNv+p+5W1bpGaa0Ahhh6TtDzfUbxjHYArL2skXibdWf Iwes06L1aIj7FYuVafd5nuVPjlunRWPYSLvMv/mg= Date: Mon, 5 Jan 2026 13:45:41 +0100 From: Greg KH To: Kevin Bube Subject: Re: [PATCH 0/2] UIO: Optional custom threaded IRQ handler Message-ID: <2026010503-vitamins-slam-fa50@gregkh> References: <20260103200631.4759-1-k.bube@web.de> <2026010409-t-shirt-eliminate-f864@gregkh> <87ms2sqs03.fsf@web.de> <2026010526-aloe-postal-8f6d@gregkh> <87ikdgqm2m.fsf@web.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87ikdgqm2m.fsf@web.de> Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Mon, Jan 05, 2026 at 01:29:53PM +0100, Kevin Bube wrote: > Greg KH writes: > > On Mon, Jan 05, 2026 at 11:21:48AM +0100, Kevin Bube wrote: > >> Greg KH writes: > >> > On Sat, Jan 03, 2026 at 09:06:29PM +0100, Kevin Bube wrote: > >> >> Add an optional threaded IRQ handler to the generic UIO driver. This allows > >> >> driver developers to keep the fast IRQ handler small and move tasks to the IRQ > >> >> thread. We also update the documentation accordingly. > >> >> > >> >> Kevin Bube (2): > >> >> UIO: Add optional IRQ thread callback > >> >> Documentation: Document threaded IRQ handler for UIO > >> >> > >> >> Documentation/driver-api/uio-howto.rst | 8 ++++++++ > >> >> drivers/uio/uio.c | 6 +++++- > >> >> include/linux/uio_driver.h | 2 ++ > >> >> 3 files changed, 15 insertions(+), 1 deletion(-) > >> > > >> > But as no in-kernel driver now uses this, it will just be removed again > >> > :( > >> > > >> > Please always provide real users for api changes, otherwise we can't > >> > determine if they are actually working or not. > >> > >> I see. Thanks for taking a look. > > > > How was this tested if you don't have an actual user for it? Why add it > > if you don't have a user for it? > > We have special hardware with a FPGA that requires its own customized > driver at my dayjob. While the driver is GPL, the FPGA image is not (not > my decision). So it makes little sense to include the driver in > mainline. There's no reason not to include it, so why not submit it? > The patch is just a part of the whole change we make for our device. I > sent it because I think it may be useful for others, too. But I > understand that it is bad to add an API without knowing its users and > not being able to test it. My misunderstanding was that the generic UIO > driver is more of a framework to derive custom drivers. We can't ever support out-of-tree drivers for obvious reasons, so just submit your driver and then it should be fine. thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies