From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Jessica Yu <jeyu@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org, dave.martin@arm.com
Subject: Re: [PATCH v5 2/2] ARM: module: Fix function kallsyms on Thumb-2
Date: Fri, 14 Dec 2018 17:07:25 +0100 [thread overview]
Message-ID: <20181214160725.kfhatfi47dz3guts@axis.com> (raw)
In-Reply-To: <20181206172920.GA2728@linux-8ccs>
On Thu, Dec 06, 2018 at 06:29:20PM +0100, Jessica Yu wrote:
> Also, do you mind if I drop the module_ prefix from
> module_kallsyms_symbol_value()? I recently submitted some internal
> module kallsyms cleanups [1] and there we have the newly renamed
> kallsyms_symbol_name(), so I think it'd be nice if we kept the naming
> scheme consistent with just kallsyms_symbol_value(). I could just do
> this myself if you don't want to respin a v6.
I've sent out a v6 with this change. I also rebased the change on top
of your cleanups in modules-next.
Thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Jessica Yu <jeyu@kernel.org>
Cc: linux@armlinux.org.uk, dave.martin@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] ARM: module: Fix function kallsyms on Thumb-2
Date: Fri, 14 Dec 2018 17:07:25 +0100 [thread overview]
Message-ID: <20181214160725.kfhatfi47dz3guts@axis.com> (raw)
In-Reply-To: <20181206172920.GA2728@linux-8ccs>
On Thu, Dec 06, 2018 at 06:29:20PM +0100, Jessica Yu wrote:
> Also, do you mind if I drop the module_ prefix from
> module_kallsyms_symbol_value()? I recently submitted some internal
> module kallsyms cleanups [1] and there we have the newly renamed
> kallsyms_symbol_name(), so I think it'd be nice if we kept the naming
> scheme consistent with just kallsyms_symbol_value(). I could just do
> this myself if you don't want to respin a v6.
I've sent out a v6 with this change. I also rebased the change on top
of your cleanups in modules-next.
Thanks.
next prev parent reply other threads:[~2018-12-14 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:14 [PATCH v5 1/2] module: Overwrite st_size instead of st_info Vincent Whitchurch
2018-12-04 14:14 ` Vincent Whitchurch
2018-12-04 14:14 ` [PATCH v5 2/2] ARM: module: Fix function kallsyms on Thumb-2 Vincent Whitchurch
2018-12-04 14:14 ` Vincent Whitchurch
2018-12-06 17:29 ` Jessica Yu
2018-12-06 17:29 ` Jessica Yu
2018-12-14 16:07 ` Vincent Whitchurch [this message]
2018-12-14 16:07 ` Vincent Whitchurch
2018-12-06 9:45 ` [PATCH v5 1/2] module: Overwrite st_size instead of st_info Miroslav Benes
2018-12-06 9:45 ` Miroslav Benes
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=20181214160725.kfhatfi47dz3guts@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=dave.martin@arm.com \
--cc=jeyu@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.