From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Dan Robertson <danlrobertson89@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: felipe.balbi@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts/gdb: fix linux constants
Date: Fri, 15 Feb 2019 20:24:08 +0000 [thread overview]
Message-ID: <07923abd-117d-2a33-2700-7db0840eacad@ideasonboard.com> (raw)
In-Reply-To: <20190215191713.GA28287@nessie>
Hi Dan,
Thank you for the patch,
On 15/02/2019 19:17, Dan Robertson wrote:
> The linux constants MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK, MS_DIRSYNC,
> MS_NOATIME, and MS_NODIRATIME were previously defined in linux/fs.h.
> Following e262e32d6bde0f77fb0c95d977482fc872c51996 the constants are
> now defined in uapi/linux/mount.h. The new location of the defined
> constants needs to be included in constants.py template in order for the
> correct constants to be generated.
>
This commit was pipped to the post by a similar patch [0] from Felipe Balbi
[0]
https://lore.kernel.org/lkml/20190215112938.25574-1-felipe.balbi@linux.intel.com/
Combined together they would form a complete patch, but this one could
do with the Fixes: tag such as
Fixes: e262e32d6bde "vfs: Suppress MS_* flag defs within the kernel
unless explicitly enabled"
With a Fixes: tag:
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> Signed-off-by: Dan Robertson <dan@dlrobertson.com>
> ---
> scripts/gdb/linux/constants.py.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/gdb/linux/constants.py.in b/scripts/gdb/linux/constants.py.in
> index 7aad82406422..6c164761d986 100644
> --- a/scripts/gdb/linux/constants.py.in
> +++ b/scripts/gdb/linux/constants.py.in
> @@ -12,9 +12,9 @@
> *
> */
>
> -#include <linux/fs.h>
Whereas Felipe's patch does not include this change (which I think it
looks like it should)
How should we proceed with these two competing patches?
Any preference from anyone?
Content wise, I feel like this one is in the lead - just missing the
Fixes: tag, but Felipe's won the race...
--
Kieran
> #include <linux/mount.h>
> #include <linux/of_fdt.h>
> +#include <uapi/linux/mount.h>
>
> /* We need to stringify expanded macros so that they can be parsed */
>
> @@ -36,7 +36,7 @@
>
> import gdb
>
> -/* linux/fs.h */
> +/* uapi/linux/mount.h */
> LX_VALUE(MS_RDONLY)
> LX_VALUE(MS_SYNCHRONOUS)
> LX_VALUE(MS_MANDLOCK)
>
--
Regards
--
Kieran
next parent reply other threads:[~2019-02-15 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190215191713.GA28287@nessie>
2019-02-15 20:24 ` Kieran Bingham [this message]
2019-02-15 20:30 ` Dan Robertson
2019-02-18 13:25 ` [PATCH 0/1] " Dan Robertson
2019-02-18 13:25 ` [PATCH 1/1] " Dan Robertson
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=07923abd-117d-2a33-2700-7db0840eacad@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=danlrobertson89@gmail.com \
--cc=felipe.balbi@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®