Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: new command 'maint flush dcache'
Date: Mon, 23 Nov 2020 17:28:52 +0200	[thread overview]
Message-ID: <83d004w0qz.fsf@gnu.org> (raw)
In-Reply-To: <cdf06509fe8cd2fa65cc7be6f2803922bcd2ef57.1606126286.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Mon, 23 Nov 2020 10:39:37 +0000)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Mon, 23 Nov 2020 10:39:37 +0000
> 
> Add a new command to flush the dcache.
> 
> gdb/ChangeLog:
> 
> 	* NEWS: Mention new commands.
> 	* target-dcache.c: Add 'cli/cli-cmds.h' include.
> 	(maint_flush_dcache_command): New function.
> 	(_initialize_target_dcache): Create new 'maint flush dcache'
> 	command.
> 
> gdb/doc/ChangeLog:
> 
> 	* gdb.texinfo (Caching Target Data): Document 'maint flush
> 	dcache'.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/dcache-flush.c: New file.
> 	* gdb.base/dcache-flush.exp: New file.

Thanks, the documentation parts are OK.

  reply	other threads:[~2020-11-23 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 10:39 [PATCH 0/2] Organise maintenance commands that flush caches Andrew Burgess
2020-11-23 10:39 ` [PATCH 1/2] gdb: introduce new 'maint flush ' prefix command Andrew Burgess
2020-11-23 15:28   ` Eli Zaretskii via Gdb-patches
2020-11-23 16:24   ` Luis Machado via Gdb-patches
2020-12-03 17:23     ` Tom Tromey
2020-12-13 12:43       ` Andrew Burgess
2020-11-23 10:39 ` [PATCH 2/2] gdb: new command 'maint flush dcache' Andrew Burgess
2020-11-23 15:28   ` Eli Zaretskii via Gdb-patches [this message]
2020-11-23 16:28   ` Luis Machado via Gdb-patches

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=83d004w0qz.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.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