From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
linux-input@vger.kernel.org, kbuild-all@01.org
Subject: Re: [input:next 1901/1903] drivers/input/misc/axp20x-pek.c:385:1-2: axp_pek_id_match is not NULL terminated at line 385 (fwd)
Date: Sun, 20 Aug 2017 09:32:29 -0700 [thread overview]
Message-ID: <20170820163229.GD1176@dtor-ws> (raw)
In-Reply-To: <1bf47905-c971-4a2b-f154-26f0d2474dad@free-electrons.com>
On Thu, Aug 17, 2017 at 12:14:22PM +0200, Quentin Schulz wrote:
> Hi Julia,
>
> Thanks for the report.
>
> @Dimitry: do I need to wait for the patches to come in next in order to
> add a Fixes tag or do I send a fix for this now?
I fixed it in place, no need to send the patch.
Thanks!
>
> Thanks,
> Quentin
>
> On 17/08/2017 11:20, Julia Lawall wrote:
> >
> >
> > ---------- Forwarded message ----------
> > Date: Thu, 17 Aug 2017 10:09:14 +0800
> > From: kbuild test robot <fengguang.wu@intel.com>
> > To: kbuild@01.org
> > Cc: Julia Lawall <julia.lawall@lip6.fr>
> > Subject: [input:next 1901/1903] drivers/input/misc/axp20x-pek.c:385:1-2:
> > axp_pek_id_match is not NULL terminated at line 385
> >
> > CC: kbuild-all@01.org
> > CC: linux-input@vger.kernel.org
> > TO: Quentin Schulz <quentin.schulz@free-electrons.com>
> > CC: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
> > head: 448f587d525d4fb5bda4b521e35ad6f15050cebd
> > commit: 2ebdfecef50840a9c6fd6a2236a1bdf2942dc1a7 [1901/1903] Input: axp20x-pek - use driver_data of platform_device_id instead of extended attributes
> > :::::: branch date: 83 minutes ago
> > :::::: commit date: 83 minutes ago
> >
> >>> drivers/input/misc/axp20x-pek.c:385:1-2: axp_pek_id_match is not NULL terminated at line 385
> >
> > # https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?id=2ebdfecef50840a9c6fd6a2236a1bdf2942dc1a7
> > git remote add input https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
> > git remote update input
> > git checkout 2ebdfecef50840a9c6fd6a2236a1bdf2942dc1a7
> > vim +385 drivers/input/misc/axp20x-pek.c
> >
> > 58be7689 Hans de Goede 2017-06-02 380
> > 2ebdfece Quentin Schulz 2017-08-14 381 static const struct platform_device_id axp_pek_id_match[] = {
> > 2ebdfece Quentin Schulz 2017-08-14 382 {
> > 2ebdfece Quentin Schulz 2017-08-14 383 .name = "axp20x-pek",
> > 2ebdfece Quentin Schulz 2017-08-14 384 .driver_data = (kernel_ulong_t)&axp20x_info,
> > 2ebdfece Quentin Schulz 2017-08-14 @385 },
> > 2ebdfece Quentin Schulz 2017-08-14 386 };
> > 2ebdfece Quentin Schulz 2017-08-14 387
> >
> > ---
> > 0-DAY kernel test infrastructure Open Source Technology Center
> > https://lists.01.org/pipermail/kbuild-all Intel Corporation
> >
>
> --
> Quentin Schulz, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
--
Dmitry
prev parent reply other threads:[~2017-08-20 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 9:20 [input:next 1901/1903] drivers/input/misc/axp20x-pek.c:385:1-2: axp_pek_id_match is not NULL terminated at line 385 (fwd) Julia Lawall
2017-08-17 10:14 ` Quentin Schulz
2017-08-20 16:32 ` Dmitry Torokhov [this message]
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=20170820163229.GD1176@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=quentin.schulz@free-electrons.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