From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: a.zummo@towertech.it, lars@metafoo.de,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rtc: cmos: remove all __exit_p annotations
Date: Tue, 18 Oct 2016 16:24:53 +0200 [thread overview]
Message-ID: <20161018142453.GA7552@Red> (raw)
In-Reply-To: <20161018141639.owhkvkn4k2rvgspr@piout.net>
On Tue, Oct 18, 2016 at 04:16:39PM +0200, Alexandre Belloni wrote:
> Hi,
>
> On 18/10/2016 at 13:55:53 +0200, Corentin Labbe wrote :
> > Change since v1:
> > - restored __exit for module_exit function
> >
> > ---8<---
>
> I don't think this is the proper scissor symbol for git. At least, it is
> no recognized by patchwork and messes your patch.
>
> > From c04a24acebee4b4432afa7a2a7d4cfe114cc9a40 Mon Sep 17 00:00:00 2001
> > From: Corentin Labbe <clabbe.montjoie@gmail.com>
> > Date: Mon, 17 Oct 2016 14:17:49 +0200
> > Subject: [PATCH v2] rtc: cmos: remove all __exit_p annotations
> >
> > I got the following stack trace under qemu:
>
> [...]
> > When cmos_set_alarm() is called dev is NULL and so trigger the deref via
> > cmos->irq
> >
> > The problem comes from that the device is removed but no remove function
> > are called due to _exit_p().
> >
> > This patch remove all _exit_p() annotation.
> >
> > Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
> > ---
>
>
> The changelog should go here.
>
> > drivers/rtc/rtc-cmos.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
Sorry, could I just resent it with PATCH RESENT v2 ? or does I need to bump it to v3.
Regards
next prev parent reply other threads:[~2016-10-18 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 11:55 [PATCH v2] rtc: cmos: remove all __exit_p annotations Corentin Labbe
2016-10-18 14:16 ` Alexandre Belloni
2016-10-18 14:24 ` LABBE Corentin [this message]
2016-10-18 14:30 ` Alexandre Belloni
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=20161018142453.GA7552@Red \
--to=clabbe.montjoie@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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