From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Chuanxiao Dong <chuanxiao.dong@intel.com>
Subject: Re: [PATCHv2 2/6] nand/denali: annotate pci init/exit functions with correct section
Date: Mon, 06 Jun 2011 16:16:24 +0300 [thread overview]
Message-ID: <1307366184.3112.70.camel@localhost> (raw)
In-Reply-To: <1307097169-11744-3-git-send-email-jamie@jamieiles.com>
On Fri, 2011-06-03 at 11:32 +0100, Jamie Iles wrote:
> The module init exit functions should be annotated with __init and
> __exit.
>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Chuanxiao Dong <chuanxiao.dong@intel.com>
> Cc: Artem Bityutskiy <dedekind1@gmail.com>
> Signed-off-by: Jamie Iles <jamie@jamieiles.com>
Would you please use "mtd: denali:" prefix?
I cannot apply this patch because it depends on the previous patch. You
could re-structure the code and make simpler patches like this go first,
then they could be taken quicker.
Thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-06-06 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 10:32 [PATCHv2 0/6] Further Denali NAND enhancements Jamie Iles
2011-06-03 10:32 ` [PATCHv2 1/6] nand/denali: convert to dev_() printk helpers Jamie Iles
2011-06-06 13:11 ` Artem Bityutskiy
2011-06-06 13:22 ` Jamie Iles
2011-06-06 13:51 ` Jamie Iles
2011-06-06 15:35 ` Artem Bityutskiy
2011-06-03 10:32 ` [PATCHv2 2/6] nand/denali: annotate pci init/exit functions with correct section Jamie Iles
2011-06-06 13:16 ` Artem Bityutskiy [this message]
2011-06-03 10:32 ` [PATCHv2 3/6] nand/denali: allow the number of ECC bits to be set by pdata Jamie Iles
2011-06-03 10:32 ` [PATCHv2 4/6] nand/denali: support hardware with internal ECC fixup Jamie Iles
2011-06-03 10:32 ` [PATCHv2 5/6] nand/denali: support MTD partitioning Jamie Iles
2011-06-03 10:32 ` [PATCHv2 6/6] mtd/denali: support for cmdline partitioning Jamie Iles
2011-06-06 13:18 ` Artem Bityutskiy
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=1307366184.3112.70.camel@localhost \
--to=dedekind1@gmail.com \
--cc=chuanxiao.dong@intel.com \
--cc=dwmw2@infradead.org \
--cc=jamie@jamieiles.com \
--cc=linux-mtd@lists.infradead.org \
/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