From: Pavel Machek <pavel@ucw.cz>
To: Julia Lawall <julia.lawall@lip6.fr>, lee.jones@linaro.org
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
pali.rohar@gmail.com, sre@kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com
Subject: Re: linux-next 2017-08-08 keyboard failure on Nokia N900
Date: Tue, 8 Aug 2017 23:44:01 +0200 [thread overview]
Message-ID: <20170808214400.GA18961@amd> (raw)
In-Reply-To: <alpine.DEB.2.20.1708082228400.4939@hadrien>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
Hi!
> > > > I've not precisely checked it, but smth is telling me that below
> > > > patch can cause this:
> > > >
> > > > commit 78daaca78ee57dead0f4aa5ee399f0499e81cd9e
...
> > > > mfd: twl4030-irq: Drop unnecessary static
> > > >
> > > > Drop static on a local variable, when the variable is initialized
> > > > before
> > > > any use, on every possible execution path through the function.
> > > >
> > > > --- a/drivers/mfd/twl4030-irq.c
> > > > +++ b/drivers/mfd/twl4030-irq.c
...
> > > > int twl4030_init_irq(struct device *dev, int irq_num)
> > > > {
> > > > - static struct irq_chip twl4030_irq_chip;
> > > > + struct irq_chip twl4030_irq_chip;
> > > >
> > > >
> > > > but if we will look at code - it can be seen that this variable is passed
> > > > by reference to
> > > > irq_set_chip_and_handler().
> > > > Ops. And what will happen when twl4030_init_irq() returns ;)
> > >
> > > The patch is not correct as was already noted when it was submitted:
..
> > Hm. This one is in linux-next, but shouldn't. Right?
> >
> > git log --oneline -10 linux-next/master
> > c0b96db Add linux-next specific files for 20170808
> >
> > git log --oneline linux-next/master | grep "Drop unnecessary static"
> > 78daaca mfd: twl4030-irq: Drop unnecessary static
>
> OK, it seems like the patch was made twice, the second one was commented
> on and the first one was applied. 78daaca should not be there.
Lee, it has your sign-off, can you drop the patch from your tree? It
is known bad.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next 2017-08-08 keyboard failure on Nokia N900
Date: Tue, 8 Aug 2017 23:44:01 +0200 [thread overview]
Message-ID: <20170808214400.GA18961@amd> (raw)
In-Reply-To: <alpine.DEB.2.20.1708082228400.4939@hadrien>
Hi!
> > > > I've not precisely checked it, but smth is telling me that below
> > > > patch can cause this:
> > > >
> > > > commit 78daaca78ee57dead0f4aa5ee399f0499e81cd9e
...
> > > > mfd: twl4030-irq: Drop unnecessary static
> > > >
> > > > Drop static on a local variable, when the variable is initialized
> > > > before
> > > > any use, on every possible execution path through the function.
> > > >
> > > > --- a/drivers/mfd/twl4030-irq.c
> > > > +++ b/drivers/mfd/twl4030-irq.c
...
> > > > int twl4030_init_irq(struct device *dev, int irq_num)
> > > > {
> > > > - static struct irq_chip twl4030_irq_chip;
> > > > + struct irq_chip twl4030_irq_chip;
> > > >
> > > >
> > > > but if we will look at code - it can be seen that this variable is passed
> > > > by reference to
> > > > irq_set_chip_and_handler().
> > > > Ops. And what will happen when twl4030_init_irq() returns ;)
> > >
> > > The patch is not correct as was already noted when it was submitted:
..
> > Hm. This one is in linux-next, but shouldn't. Right?
> >
> > git log --oneline -10 linux-next/master
> > c0b96db Add linux-next specific files for 20170808
> >
> > git log --oneline linux-next/master | grep "Drop unnecessary static"
> > 78daaca mfd: twl4030-irq: Drop unnecessary static
>
> OK, it seems like the patch was made twice, the second one was commented
> on and the first one was applied. 78daaca should not be there.
Lee, it has your sign-off, can you drop the patch from your tree? It
is known bad.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170808/bff17b2d/attachment.sig>
next prev parent reply other threads:[~2017-08-08 21:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 10:17 linux-next 2017-08-08 failure on Nokia N900 Pavel Machek
2017-08-08 10:17 ` Pavel Machek
2017-08-08 10:34 ` Pavel Machek
2017-08-08 10:34 ` Pavel Machek
2017-08-08 11:12 ` linux-next 2017-08-08 keyboard " Pavel Machek
2017-08-08 11:12 ` Pavel Machek
2017-08-08 19:59 ` Grygorii Strashko
2017-08-08 19:59 ` Grygorii Strashko
2017-08-08 19:59 ` Grygorii Strashko
2017-08-08 20:09 ` Julia Lawall
2017-08-08 20:09 ` Julia Lawall
2017-08-08 20:15 ` Grygorii Strashko
2017-08-08 20:15 ` Grygorii Strashko
2017-08-08 20:15 ` Grygorii Strashko
2017-08-08 20:30 ` Julia Lawall
2017-08-08 20:30 ` Julia Lawall
2017-08-08 21:44 ` Pavel Machek [this message]
2017-08-08 21:44 ` Pavel Machek
2017-08-09 12:45 ` Lee Jones
2017-08-09 12:45 ` Lee Jones
2017-08-10 17:10 ` Pavel Machek
2017-08-10 17:10 ` Pavel Machek
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=20170808214400.GA18961@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=khilman@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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 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.