linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mattias Jacobsson <2pi@mok.nu>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<2pi@mok.nu>
Subject: Re: [PATCH] modpost: file2alias: define size of alias
Date: Tue, 19 Feb 2019 21:08:37 +0100	[thread overview]
Message-ID: <20190219200837.d34cxg2d7gqxlvhs@mok.nu> (raw)
In-Reply-To: <CAK7LNAQZ7PDZ4+uZu-FT4V8yw9oUGz6e++9xSshWJvALj3gN0Q@mail.gmail.com>

Hi Masahiro,

On 2019-02-18, Masahiro Yamada wrote:
> Hi Mattias,
> 
> On Thu, Feb 7, 2019 at 9:31 PM Mattias Jacobsson <2pi@mok.nu> wrote:
> >
> > The size of the variable alias provided to do_entry functions are
> > currently not readily available. Thus hindering do_entry functions to
> > perform bounds checking.
> >
> > Define the macro ALIAS_SIZE containing the size of the variable alias.
> >
> > Signed-off-by: Mattias Jacobsson <2pi@mok.nu>
> 
> 
> Sorry for late reply.
> 
> I can apply this to my kbuild tree shortly, but
> it looks like a prerequisite for your
> "platform/x86: wmi: use MODULE_DEVICE_TABLE() instead of MODULE_ALIAS()"
> 
> 
> If you want all the patches to go through x86 platform-driver tree,
> I am fine with that too.

I don't mind either way, however I've asked the x86 platform-driver
maintainers if they have a preference in this matter. You should have
received that mail otherwise see [1].

[1]: https://lkml.kernel.org/r/082d3d38b7dde6050b6b3e518ada439eade65b2c.1550603967.git.2pi@mok.nu

> 
> Please let me know what you want.
> 
> Thanks.
> 
> 
> 
> -- 
> Best Regards
> Masahiro Yamada

Thanks,
Mattias

  reply	other threads:[~2019-02-19 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 12:30 [PATCH] modpost: file2alias: define size of alias Mattias Jacobsson
2019-02-18  7:20 ` Masahiro Yamada
2019-02-19 20:08   ` Mattias Jacobsson [this message]
2019-02-19 23:47     ` Masahiro Yamada
2019-02-23 19:57       ` Mattias Jacobsson
2019-03-07  6:09         ` Darren Hart
2019-03-07  6:17           ` Darren Hart
2019-03-07  6:20             ` 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=20190219200837.d34cxg2d7gqxlvhs@mok.nu \
    --to=2pi@mok.nu \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=yamada.masahiro@socionext.com \
    /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).