public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: xujialu <xujialu@vimux.org>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org,
	masahiroy@kernel.org, akpm@linux-foundation.org,
	mchehab+huawei@kernel.org
Subject: Re: [PATCH] scripts: gtags_files_generator.sh
Date: Tue, 28 Apr 2020 09:04:57 +0200	[thread overview]
Message-ID: <20200428070457.GA992660@kroah.com> (raw)
In-Reply-To: <20200428053509.19564-1-xujialu@vimux.org>

On Tue, Apr 28, 2020 at 01:35:08PM +0800, xujialu wrote:
> > Yes, please, just do proper email responses, like all the other
> > conversations on the mailing lists :)
> 
> Nice of you :)
> 
> > Perhaps you should read the email client documentation in the kernel
> > tree?
> 
> Also watched your interesting video:
>     <HOWTO - apply a Linux kernel patch to the stable tree>
> 
> > I still don't know what is wrong with 'make gtags'.  If it does not work
> > properly for you, why not fix that up instead of creating something
> > totally new that is not even hooked up to the kernel build system?
> 
> As you suggested, i walk through scripts/tags.sh, and suddenly found
> flag COMPILED_SOURCE, so i throw away my lasted stupid script, and tried
> to improve this 'compiled only' feature, seems much better now.
> 
> And about 'make gtags':
> 1. It picks up so many files, do you think 'all sources' is good for us?

When you modify kernel code, yes, you have to fix it up everywhere, you
can not ignore other architectures or drivers that your machine happens
to not use.

An "average" laptop only runs about 2-3 million lines of code or so, a
small percentage of the 25+ million lines that are in the kernel source
tree.

> 2. Seems gtags does not support source files from parrent directories,
> it gives warnning out of tree (global-6.6.3) or just segmentation fault
> (global-5.7.3) when we 'make gtags O=blabla', cause gtags.files is
> generated in dir 'blabla' but source files are out of dir 'blabla'.

Then fix that as a stand-alone patch please, do not mix it in with other
changes.

thanks,

greg k-h

  parent reply	other threads:[~2020-04-28  7:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200423095331.8032-1-xujialu@vimux.org>
2020-04-23 10:38 ` [PATCH] scripts: gtags_files_generator.sh Greg KH
     [not found]   ` <20200423143642.11788-1-xujialu@vimux.org>
     [not found]     ` <20200423143642.11788-2-xujialu@vimux.org>
2020-04-23 14:42       ` Greg KH
2020-04-23 14:44       ` Jonathan Corbet
     [not found]       ` <20200425073105.27796-1-xujialu@vimux.org>
2020-04-25  8:03         ` Greg KH
     [not found]           ` <20200426024436.7534-1-xujialu@vimux.org>
2020-04-26  7:09             ` Greg KH
2020-04-26  7:46               ` xujialu
2020-04-26  8:36                 ` gregkh
     [not found]                   ` <20200428053509.19564-1-xujialu@vimux.org>
2020-04-28  7:04                     ` Greg KH [this message]
     [not found]                     ` <20200428053509.19564-2-xujialu@vimux.org>
2020-04-28  7:06                       ` [PATCH v2] scripts: scripts/tags.sh Greg KH
     [not found]                         ` <20200502052619.26457-1-xujialu@vimux.org>
     [not found]                           ` <20200502052619.26457-2-xujialu@vimux.org>
2020-05-12  2:51                             ` [PATCH v4 1/2] scripts: Support compiled source, improved precise Masahiro Yamada
     [not found]                               ` <20200514170945.24964-1-xujialu@vimux.org>
2020-05-21  6:29                                 ` Masahiro Yamada
     [not found]                           ` <20200502052619.26457-3-xujialu@vimux.org>
2020-05-12  3:08                             ` [PATCH v4 2/2] scripts: Add a intermediate file for 'make gtags' Masahiro Yamada
2020-04-28  7:52             ` [PATCH] scripts: gtags_files_generator.sh Masahiro Yamada

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=20200428070457.GA992660@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=xujialu@vimux.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