workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Doug Anderson <dianders@chromium.org>
Cc: linux-doc@vger.kernel.org,
	Sebastian Fricke <sebastian.fricke@collabora.com>,
	Jonathan Corbet <corbet@lwn.net>,
	workflows@vger.kernel.org,
	Jason Wessel <jason.wessel@windriver.com>,
	Daniel Thompson <danielt@kernel.org>,
	linux-debuggers@vger.kernel.org,
	kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH] Documentation: move dev-tools debugging files to process/debugging/
Date: Wed, 4 Dec 2024 15:09:19 -0800	[thread overview]
Message-ID: <e3e78060-0939-4078-989c-acd7ca1c90d2@infradead.org> (raw)
In-Reply-To: <CAD=FV=WhQFxUNr6vyMVBn9CmZPnnntDP2nH=Tp1Rm=xH+YsE2w@mail.gmail.com>



On 12/4/24 3:07 PM, Doug Anderson wrote:
> Hi,
> 
> On Wed, Dec 4, 2024 at 2:17 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> Move gdb and kgdb debugging documentation to the dedicated
>> debugging directory (Documentation/process/debugging/).
>> Adjust the index.rst files to follow the file movement.
>> Update location of kgdb.rst in MAINTAINERS file.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Sebastian Fricke <sebastian.fricke@collabora.com>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: workflows@vger.kernel.org
>> Cc: Jason Wessel <jason.wessel@windriver.com>
>> Cc: Daniel Thompson <danielt@kernel.org>
>> Cc: Douglas Anderson <dianders@chromium.org>
>> Cc: linux-debuggers@vger.kernel.org
>> Cc: kgdb-bugreport@lists.sourceforge.net
>> ---
>>  Documentation/dev-tools/index.rst                                       | 2 --
>>  Documentation/{dev-tools => process/debugging}/gdb-kernel-debugging.rst | 0
> 
> After applying your patch and doing `git grep
> gdb-kernel-debugging.rst`, I still see several references to the old
> location. Those should be updated as part of this patch, right?
> 
> 
> 
>>  Documentation/process/debugging/index.rst                               | 2 ++
>>  Documentation/{dev-tools => process/debugging}/kgdb.rst                 | 0
> 
> Similarly `git grep kgdb.rst` still has several references to the old location.


Thanks. I should have done that.  :(

>>  MAINTAINERS                                                             | 2 +-
>>  5 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/dev-tools/index.rst b/Documentation/dev-tools/index.rst
>> index 3c0ac08b2709..c1e73e75f551 100644
>> --- a/Documentation/dev-tools/index.rst
>> +++ b/Documentation/dev-tools/index.rst
>> @@ -27,8 +27,6 @@ Documentation/dev-tools/testing-overview.rst
>>     kmemleak
>>     kcsan
>>     kfence
>> -   gdb-kernel-debugging
>> -   kgdb
>>     kselftest
>>     kunit/index
>>     ktap
>> diff --git a/Documentation/dev-tools/gdb-kernel-debugging.rst b/Documentation/process/debugging/gdb-kernel-debugging.rst
>> similarity index 100%
>> rename from Documentation/dev-tools/gdb-kernel-debugging.rst
>> rename to Documentation/process/debugging/gdb-kernel-debugging.rst
>> diff --git a/Documentation/process/debugging/index.rst b/Documentation/process/debugging/index.rst
>> index f6e4a00dfee3..bc4a816e3d32 100644
>> --- a/Documentation/process/debugging/index.rst
>> +++ b/Documentation/process/debugging/index.rst
>> @@ -12,6 +12,8 @@ general guides
>>
>>     driver_development_debugging_guide
>>     userspace_debugging_guide
>> +   gdb-kernel-debugging
>> +   kgdb
> 
> Should the list above be kept alphabetical. The list you removed these
> entries from was _almost_ alphabetical...

Not that I know of.  I'll listen for other opinions though.

Thanks.

-- 
~Randy


  reply	other threads:[~2024-12-04 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 22:17 Randy Dunlap
2024-12-04 23:07 ` Doug Anderson
2024-12-04 23:09   ` Randy Dunlap [this message]
2024-12-05  9:09     ` Sebastian Fricke
2024-12-05 17:08       ` Randy Dunlap
2024-12-06 16:38 ` Jonathan Corbet
2024-12-06 23:57   ` Randy Dunlap
2024-12-07  8:50     ` Sebastian Fricke
2024-12-07 23:11       ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3e78060-0939-4078-989c-acd7ca1c90d2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=danielt@kernel.org \
    --cc=dianders@chromium.org \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-debuggers@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=sebastian.fricke@collabora.com \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox