From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF8B627CCEE; Mon, 17 Nov 2025 11:26:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763378790; cv=none; b=la2raFf4ddfP16JZkw6MkVJ0NWqb6JBXHfVtB8Tb6JB5E66FgszbP0ZNT4k0ccG2uw/TdE5x6/tNaRrfRNfLxj/oUJ8W6aCVql2XaFc4XCblnXY0yvW0cid2cKRNHb5GWrX2BlSf5yVhm52Q94Wlth2QBfyQhAqhTVjiHemzxzQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763378790; c=relaxed/simple; bh=Q3AuxCkGANqkre0I3GtuOq07feggiAZr4gMwz1atsaY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=g9YwVocmhFqz+xLfw5/jPZCXiJ6rR2d14WTf9kKSUHoxJzokp2oMSXAOvFObePjbGHoXfzRRgLDEZADTO8p2+0n6oCMt0p/hET2dt8aKjI6IYE8uh1QoFlsCEhMf5qdrlq6N7hIOZoGOmYVRJFtZNhe2Ta4bE0FGCNWvCTzZ7fk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=xcilKv0z; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=4Z1wt0kS; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="xcilKv0z"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="4Z1wt0kS" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1763378787; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Q3AuxCkGANqkre0I3GtuOq07feggiAZr4gMwz1atsaY=; b=xcilKv0zKc0VzJf3qXBzT7Djt1ZHZytJgvQZFOVKpgf1YZm3sL5esgIR1Xz6b05qhPzE5j JuFRTvlY6XiFmTeI61Al2ihY0TXCHfP3HK3x14z2ZhC1VECd/UupsonhVxFTuHJXLoODTY 3N/oeeNuZyLaRvAV1YiW/fxEkkn6DLLHf3E1QWrsflHVJrqm3tZUwCT5gpC0XwdfDDh0RC gnpZ72L609ergXOD2Imk5BUzMwHORvchSvgvo1qPttSasGVCasWKBIJOM6Xe3a0VQ8JrXf ZFOCtkj17s18IyVjBxunPm+e+O5EejYtbgU7Bl178+Wt2567J8aUOBMuwjc6xQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1763378787; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Q3AuxCkGANqkre0I3GtuOq07feggiAZr4gMwz1atsaY=; b=4Z1wt0kSfmZ2a70PBFr8EAvrlTz2NmSnB1j4Mt4YlvPcWRRwOTivqg7kVmVXReegNeaFc0 UiDxksH6EtIjIfCA== To: Tobias Schumacher , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Christian Borntraeger , Sven Schnelle , Niklas Schnelle , Gerald Schaefer , Gerd Bayer , Halil Pasic , Matthew Rosato Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, Tobias Schumacher Subject: Re: [PATCH v2 1/2] genirq: Change hwirq parameter to irq_hw_number_t In-Reply-To: <20251117-implement-msi-domain-v2-1-a110ea0721fe@linux.ibm.com> References: <20251117-implement-msi-domain-v2-0-a110ea0721fe@linux.ibm.com> <20251117-implement-msi-domain-v2-1-a110ea0721fe@linux.ibm.com> Date: Mon, 17 Nov 2025 12:26:26 +0100 Message-ID: <87346c99y5.ffs@tglx> Precedence: bulk X-Mailing-List: linux-s390@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Mon, Nov 17 2025 at 09:59, Tobias Schumacher wrote: > The irqdomain implementation internally represents hardware IRQs as > irq_hw_number_t, which is defined as unsigned long int. When providing > an irq_hw_number_t to the generic_handle_domain() functions that expect > and unsigned int hwirq, this can lead to a loss of information. Change > the hwirq parameter to irq_hw_number_t to support the full range of > hwirqs. > > Signed-off-by: Tobias Schumacher Reviewed-by: Thomas Gleixner