[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251118154107.3100-1-dawei.li@linux.dev>
Date: Tue, 18 Nov 2025 23:41:04 +0800
From: Dawei Li <dawei.li@...ux.dev>
To: andersson@...nel.org,
mathieu.poirier@...aro.org
Cc: linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org,
dawei.li@...ux.dev,
set_pte_at@...look.com
Subject: [PATCH v4 0/3] Fixes and rework of rpmsg_eptdev_add()
This is V4 of series fixing fallout introduced by anonymous inode eptdev
code and rework the exception handing paths.
And it tries to address a long suffering issue related to WARN() in
error path.
Change for v4:
- Re-layout the patches in series
1/3: Fix potential WARN In error patch of rpmsg_eptdev_add().
2/3: Rework exception handling of rpmsg_eptdev_add() and callers.
3/3: Merge branches in rpmsg_eptdev_add().
Link to v3:
https://lore.kernel.org/all/20251113153909.3789-1-dawei.li@linux.dev/
Change for v3:
- Split it into 3 patches:
1/3: Fix legacy bug.
2/3: Fix new bug introduced by anonymous eptdev code.
3/3: Rework error handling code.
Link to v2:
https://lore.kernel.org/all/20251112150108.49017-1-dawei.li@linux.dev/
Change for v2:
- Add put_device() when __rpmsg_eptdev_open() failed.
Link to v1:
https://lore.kernel.org/all/20251112142813.33708-1-dawei.li@linux.dev/
Dawei Li (3):
rpmsg: char: Fix WARN() in error path of rpmsg_eptdev_add()
rpmsg: char: Rework of rpmsg_eptdev_add() and its callers
rpmsg: char: Merge cdev branches in rpmsg_eptdev_add()
drivers/rpmsg/rpmsg_char.c | 60 ++++++++++++++++++++------------------
1 file changed, 31 insertions(+), 29 deletions(-)
--
2.25.1
Powered by blists - more mailing lists