From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: jim.cromie@gmail.com
Cc: Greg KH <greg@kroah.com>, Varun Iyer <varun_iyer@posteo.net>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: is there a macro symbol for strlen($LINUX_SOURCE_PATH)
Date: Thu, 05 Sep 2019 16:23:21 -0400 [thread overview]
Message-ID: <742173.1567715001@turing-police> (raw)
In-Reply-To: <CAJfuBxwChECpA8j+GWdyy+wAtydFybjDLSCQjcf7C-L0Oa2iQA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]
On Thu, 05 Sep 2019 08:31:55 -0600, jim.cromie@gmail.com said:
> So I feel compelled to offer a fix for dynamic_debug, attached.
> hopefully it explains adequately, I have some doubts..
>
> maybe this should go to LKML now,
> but I guess Id prefer to make my obvious thinkos less publicly.
> Im happy to bikeshed the commit-msg or code.
You should find a way to test that this is TRTTD for all gcc releases still
supported for building a kernel (which may mean finding a 4.8 or 4.9 to
test on to see if it uses relative or full paths).
Removing these functions for kernels built with pre-change gcc will cause some
semantic changes. Probably the *right* thing to do is to figure out what
release it was changed in, and do some hacking to include/config/compiler-gcc.h.
In addition, any such patches should be at least non-hostile to the ongoing
effort to get a kernel tree that builds with clang rather than gcc.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-09-05 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 21:42 is there a macro symbol for strlen($LINUX_SOURCE_PATH) jim.cromie
2019-09-04 22:18 ` Varun Iyer
2019-09-05 14:31 ` jim.cromie
2019-09-05 20:23 ` Valdis Klētnieks [this message]
2019-09-05 5:47 ` Greg KH
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=742173.1567715001@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=varun_iyer@posteo.net \
/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;
as well as URLs for NNTP newsgroup(s).