From: Tom Rini <trini@konsulko.com>
To: Philip Richard Oberfichtner <pro@denx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [RFC] CTAGS prototypes
Date: Fri, 20 Oct 2023 13:50:10 -0400 [thread overview]
Message-ID: <20231020175010.GO3119521@bill-the-cat> (raw)
In-Reply-To: <20231020104606.23305-2-pro@denx.de>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
On Fri, Oct 20, 2023 at 12:46:07PM +0200, Philip Richard Oberfichtner wrote:
> Hi,
>
> is there a specific reason why the ctags make target is compiled without
> using '--kinds-c=+p'? Maybe it would make sense to (optionally) include
> that in the Makefile?
>
> I personally find it useful to jump to the header where a function is
> declared to view the documentary comment. Or am I missing another option
> to quickly get there?
To answer the first half of this, it's whatever the last person to use
ctags related things was. Perhaps looking at and syncing that part of
the kernel tree would be helpful?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2023-10-20 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 10:46 [RFC] CTAGS prototypes Philip Richard Oberfichtner
2023-10-20 17:50 ` Tom Rini [this message]
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=20231020175010.GO3119521@bill-the-cat \
--to=trini@konsulko.com \
--cc=pro@denx.de \
--cc=u-boot@lists.denx.de \
/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