This is an automated email from the ASF dual-hosted git repository.

xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git


The following commit(s) were added to refs/heads/master by this push:
     new 71d10bd8cf nuttx/fs:Rename node with inode.
71d10bd8cf is described below

commit 71d10bd8cf240a28dbee019033c4c79ebe2fceb3
Author: cuiziwei <[email protected]>
AuthorDate: Wed Nov 1 10:46:59 2023 +0800

    nuttx/fs:Rename node with inode.
    
    Signed-off-by: cuiziwei <[email protected]>
---
 fs/inode/fs_inoderelease.c | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/fs/inode/fs_inoderelease.c b/fs/inode/fs_inoderelease.c
index 651104c4d2..e9bb3060df 100644
--- a/fs/inode/fs_inoderelease.c
+++ b/fs/inode/fs_inoderelease.c
@@ -45,11 +45,11 @@
  *
  ****************************************************************************/
 
-void inode_release(FAR struct inode *node)
+void inode_release(FAR struct inode *inode)
 {
   int ret;
 
-  if (node)
+  if (inode)
     {
       /* Decrement the references of the inode */
 
@@ -66,9 +66,9 @@ void inode_release(FAR struct inode *node)
         }
       while (ret < 0);
 
-      if (node->i_crefs)
+      if (inode->i_crefs)
         {
-          node->i_crefs--;
+          inode->i_crefs--;
         }
 
       /* If the subtree was previously deleted and the reference
@@ -76,7 +76,7 @@ void inode_release(FAR struct inode *node)
        * now.
        */
 
-      if (node->i_crefs <= 0 && (node->i_flags & FSNODEFLAG_DELETED) != 0)
+      if (inode->i_crefs <= 0 && (inode->i_flags & FSNODEFLAG_DELETED) != 0)
         {
           /* If the inode has been properly unlinked, then the peer pointer
            * should be NULL.
@@ -84,8 +84,8 @@ void inode_release(FAR struct inode *node)
 
           inode_unlock();
 
-          DEBUGASSERT(node->i_peer == NULL);
-          inode_free(node);
+          DEBUGASSERT(inode->i_peer == NULL);
+          inode_free(inode);
         }
       else
         {

Reply via email to