patch "slimbus: messaging: start transaction ids from 1 instead of zero" added to char-misc-linus
Subsystems (2)
This is a note to let you know that I've just added the patch titled
slimbus: messaging: start transaction ids from 1 instead of zero
to my char-misc git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
in the char-misc-linus branch.
The patch will show up in the next release of the linux-next tree (usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the next -rc kernel release.
If you have any questions about this process, please let me know.
From 9659281ce78de0f15a4aa124da8f7450b1399c09 Mon Sep 17 00:00:00 2001
From: Srinivas Kandagatla <[email protected]>
Date: Mon, 9 Aug 2021 09:24:25 +0100
Subject: slimbus: messaging: start transaction ids from 1 instead of zero
As tid is unsigned its hard to figure out if the tid is valid or invalid. So Start the transaction ids from 1 instead of zero so that we could differentiate between a valid tid and invalid tids
This is useful in cases where controller would add a tid for controller specific transfers.
--- drivers/slimbus/messaging.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/slimbus/messaging.c +1 -1
@@ -66,7 +66,7 @@ int slim_alloc_txn_tid(struct slim_controller *ctrl, struct slim_msg_txn *txn)int ret =0 ;spin_lock_irqsave (&ctrl->txn_lock, flags); - ret =idr_alloc_cyclic (&ctrl->tid_idr, txn,0 , + ret =idr_alloc_cyclic (&ctrl->tid_idr, txn,1 ,SLIM_MAX_TIDS ,GFP_ATOMIC );if (ret <0 ) {spin_unlock_irqrestore (&ctrl->txn_lock, flags);
Signature · 1 line
2.32.0