From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general@lists.sourceforge.net,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] atmel/spi: fix missing probe during the switch to module_platform_driver
Date: Thu, 3 Nov 2011 17:51:13 +0100 [thread overview]
Message-ID: <20111103165113.GL7136@game.jcrosoft.org> (raw)
In-Reply-To: <20111103151855.GP12913@n2100.arm.linux.org.uk>
On 15:18 Thu 03 Nov , Russell King - ARM Linux wrote:
> On Thu, Nov 03, 2011 at 11:10:42PM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > in commit 940ab889
>
> This kind of commit message is, frankly, utter crap.
>
> With all the complaints that have been on this mailing list about raw
> commit IDs without saying what the commit was, it completely astounds
> me that someone in your position (allegedly a co-maintainer of a SoC)
> would make such an error.
>
> Please generate a much better commit message. Maybe something like:
>
> ----
> Commit 940ab889 (blah blah blah) converted this driver to use
> module_platform_driver, but due to the use of platform_driver_probe(),
> this resulted in the call to atmel_spi_probe being lost. Place the
> call to this function into the driver structure.
>
> As atmel_spi_probe is marked __init, this will cause a section mismatch
> error, so ... <fill this in for the point below>
> ----
>
> And, you're forgetting to fix this properly (maybe you don't care about
> section mismatch errors - are you going to create another patch for that
> as well?) Did you even build-test this patch and pay attention to any
> warnings issued, or were you just pleased to get a zImage at the end?
>
> static int __init atmel_spi_probe(struct platform_device *pdev)
>
> __init is not compatible with having a pointer in the platform driver
> structure. It needs to be __devinit.
this is an other fix I do not want to fix 2 issue in one commit and I do care
of mismatch erros I fix them all the time I send patch for some rm9200 few
weeks ago
Best Regards,
J.
WARNING: multiple messages have this Message-ID (diff)
From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] atmel/spi: fix missing probe during the switch to module_platform_driver
Date: Thu, 3 Nov 2011 17:51:13 +0100 [thread overview]
Message-ID: <20111103165113.GL7136@game.jcrosoft.org> (raw)
In-Reply-To: <20111103151855.GP12913@n2100.arm.linux.org.uk>
On 15:18 Thu 03 Nov , Russell King - ARM Linux wrote:
> On Thu, Nov 03, 2011 at 11:10:42PM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > in commit 940ab889
>
> This kind of commit message is, frankly, utter crap.
>
> With all the complaints that have been on this mailing list about raw
> commit IDs without saying what the commit was, it completely astounds
> me that someone in your position (allegedly a co-maintainer of a SoC)
> would make such an error.
>
> Please generate a much better commit message. Maybe something like:
>
> ----
> Commit 940ab889 (blah blah blah) converted this driver to use
> module_platform_driver, but due to the use of platform_driver_probe(),
> this resulted in the call to atmel_spi_probe being lost. Place the
> call to this function into the driver structure.
>
> As atmel_spi_probe is marked __init, this will cause a section mismatch
> error, so ... <fill this in for the point below>
> ----
>
> And, you're forgetting to fix this properly (maybe you don't care about
> section mismatch errors - are you going to create another patch for that
> as well?) Did you even build-test this patch and pay attention to any
> warnings issued, or were you just pleased to get a zImage at the end?
>
> static int __init atmel_spi_probe(struct platform_device *pdev)
>
> __init is not compatible with having a pointer in the platform driver
> structure. It needs to be __devinit.
this is an other fix I do not want to fix 2 issue in one commit and I do care
of mismatch erros I fix them all the time I send patch for some rm9200 few
weeks ago
Best Regards,
J.
next prev parent reply other threads:[~2011-11-03 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 14:48 [PATCH 1/1] atmel/spi: fix missing probe during the switch to module_platform_driver Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 14:48 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 14:55 ` Deepak Saxena
2011-11-03 14:55 ` Deepak Saxena
2011-11-03 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 15:10 ` [PATCH v2] " Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 15:10 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 15:18 ` Russell King - ARM Linux
2011-11-03 15:18 ` Russell King - ARM Linux
2011-11-03 16:51 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-11-03 16:51 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 17:43 ` Russell King - ARM Linux
2011-11-03 17:43 ` Russell King - ARM Linux
2011-11-03 18:03 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 18:03 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-03 18:08 ` Russell King - ARM Linux
2011-11-03 18:08 ` Russell King - ARM Linux
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=20111103165113.GL7136@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=spi-devel-general@lists.sourceforge.net \
/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.