Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <1553013349.65329.0.camel@acm.org>
Subject: Re: [PATCH v2 07/19] locking/lockdep: Update obsolete struct field
 description
From:   Bart Van Assche <bvanassche@acm.org>
To:     Yuyang Du <duyuyang@gmail.com>, peterz@infradead.org,
        will.deacon@arm.com, mingo@kernel.org
Cc:     ming.lei@redhat.com, linux-kernel@vger.kernel.org
Date:   Tue, 19 Mar 2019 09:35:49 -0700
In-Reply-To: <20190318085733.3143-8-duyuyang@gmail.com>
References: <20190318085733.3143-1-duyuyang@gmail.com>
         <20190318085733.3143-8-duyuyang@gmail.com>
Content-Type: text/plain; charset="UTF-7"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 2019-03-18 at 16:57 +-0800, Yuyang Du wrote:
+AD4  struct lock+AF8-chain +AHs
+AD4 -       /+ACo see BUILD+AF8-BUG+AF8-ON()s in lookup+AF8-chain+AF8-cache() +ACo-/
+AD4 +-       /+ACo
+AD4 +-        +ACo irq+AF8-context: the same as irq+AF8-context in held+AF8-lock below
+AD4 +-        +ACo depth:       the number of held locks in this chain
+AD4 +-        +ACo base:        the index in chain+AF8-hlocks for this chain
+AD4 +-        +ACo-/
+AD4         unsigned int                    irq+AF8-context :  2,
+AD4                                         depth       :  6,
+AD4                                         base        : 24+ADs

Have you considered to use the kernel-doc style for documenting these
structure members?

Thanks,

Bart.