From mboxrd@z Thu Jan 1 00:00:00 1970 From: brendanhiggins at google.com (Brendan Higgins) Date: Tue, 14 May 2019 16:19:02 -0700 Subject: [PATCH v3 15/18] Documentation: kunit: add documentation for KUnit In-Reply-To: <20190514121623.0314bf07@lwn.net> References: <20190514054251.186196-1-brendanhiggins@google.com> <20190514054251.186196-16-brendanhiggins@google.com> <20190514073422.4287267c@lwn.net> <20190514180810.GA109557@google.com> <20190514121623.0314bf07@lwn.net> Message-ID: <20190514231902.GA12893@google.com> On Tue, May 14, 2019 at 12:16:23PM -0600, Jonathan Corbet wrote: > On Tue, 14 May 2019 11:08:10 -0700 > Brendan Higgins wrote: > > > > Naturally, though, I have one request: I'd rather not see this at the top > > > level, which is more than crowded enough as it is. Can this material > > > please go into the development tools book, alongside the kselftest > > > documentation? Hmmm...probably premature to bring this up, but Documentation/dev-tools/ is kind of thrown together. It would be nice to provide a coherent overview, maybe provide some basic grouping as well. It would be nice if there was kind of a gentle introduction to the tools, which ones you should be looking at, when, why, etc. > > Oh yeah, that seems like the obvious home for this in hindsight. Sorry > > about that. Will fix in next revision! > > No need to apologize - I have to say the same thing to everybody :) From mboxrd@z Thu Jan 1 00:00:00 1970 From: brendanhiggins@google.com (Brendan Higgins) Date: Tue, 14 May 2019 16:19:02 -0700 Subject: [PATCH v3 15/18] Documentation: kunit: add documentation for KUnit In-Reply-To: <20190514121623.0314bf07@lwn.net> References: <20190514054251.186196-1-brendanhiggins@google.com> <20190514054251.186196-16-brendanhiggins@google.com> <20190514073422.4287267c@lwn.net> <20190514180810.GA109557@google.com> <20190514121623.0314bf07@lwn.net> Message-ID: <20190514231902.GA12893@google.com> Content-Type: text/plain; charset="UTF-8" Message-ID: <20190514231902.RVFBw_KUMz9XGwSuY3QCe4LrhMgaIQgGyQ5yuOVLJVo@z> On Tue, May 14, 2019@12:16:23PM -0600, Jonathan Corbet wrote: > On Tue, 14 May 2019 11:08:10 -0700 > Brendan Higgins wrote: > > > > Naturally, though, I have one request: I'd rather not see this at the top > > > level, which is more than crowded enough as it is. Can this material > > > please go into the development tools book, alongside the kselftest > > > documentation? Hmmm...probably premature to bring this up, but Documentation/dev-tools/ is kind of thrown together. It would be nice to provide a coherent overview, maybe provide some basic grouping as well. It would be nice if there was kind of a gentle introduction to the tools, which ones you should be looking at, when, why, etc. > > Oh yeah, that seems like the obvious home for this in hindsight. Sorry > > about that. Will fix in next revision! > > No need to apologize - I have to say the same thing to everybody :)