From: Artem Bityutskiy <dedekind@infradead.org>
To: apgmoorthy <moorthy.apg@samsung.com>
Cc: vishak.g@samsung.com, amul.saha@samsung.com,
kyungmin.park@samsung.com, linux-mtd@lists.infradead.org,
akpm@linux-foundation.org, dwmw2@infradead.org
Subject: Re: [patch 01/14] mtd: Flex-OneNAND support
Date: Mon, 25 May 2009 14:41:58 +0300 [thread overview]
Message-ID: <1243251718.21646.107.camel@localhost.localdomain> (raw)
In-Reply-To: <5205AB2678D945D194F6372BE9297942@sisodomain.com>
Hi,
On Mon, 2009-05-25 at 16:22 +0530, apgmoorthy wrote:
> On Sat May 23 05:35:19 EDT 2009 dedekind@infradead.org wrote :
>
> >I get the following warning when compile this:
>
> >drivers/mtd/onenand/onenand_base.c:3263: warning: 'flexonenand_setup'
> >defined but not used
>
> I tried on the MTD Git and have seen the warning as you mentioned.
> '#ifndef MODULE' around the function 'flexonenand_setup' should help to get away with that warning.
> We will post a patch.
>
> Against which Fork , the patch should be ?
Dunno. Probably 2.6.30-rc7? Also, I think the loooong printk's
lines in the patch are ugly. If you could make them nicer,
it'd be cool. But whole MTD is full of printk's like this, so
I did not complain about that.
I wanted to take your patch to my l2-mtd-2.6.git tree, and then
ping dwmw2 to pull from it. But because of the warning and
these ugly printk's I decided that I will rather not do this
so far.
Also, I'm not sure about #ifndef MODULE. AFAIK, the whole
'__setup()' thing is not supposed to be used in drivers.
But I'm not sure. I'll leave this for Andrew to comment on :-)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-25 11:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 10:52 [patch 01/14] mtd: Flex-OneNAND support apgmoorthy
2009-05-25 11:41 ` Artem Bityutskiy [this message]
2009-05-25 12:14 ` apgmoorthy
2009-05-27 13:55 ` Artem Bityutskiy
2009-06-09 13:38 ` David Woodhouse
2009-06-10 7:46 ` Amit Kumar Sharma
2009-06-11 9:22 ` Amul Saha
2009-06-11 9:23 ` Amul Saha
2009-06-11 9:35 ` Artem Bityutskiy
2009-06-12 10:22 ` Amul Saha
2009-06-12 10:26 ` Amul Saha
2009-06-12 10:42 ` Artem Bityutskiy
2009-06-12 11:57 ` Amul Saha
2009-06-12 12:03 ` Artem Bityutskiy
2009-06-12 12:52 ` David Woodhouse
2009-06-12 13:16 ` Amul Saha
2009-06-12 13:32 ` David Woodhouse
2009-06-12 13:49 ` Amul Saha
2009-06-16 5:54 ` Amul Saha
[not found] ` <42F6638D897B4BA7B729CBC244D9F6E4@sisodomain.com>
2009-06-22 19:15 ` MLC Support in JFFS2 David Woodhouse
2009-06-23 12:52 ` apgmoorthy
2009-06-23 13:19 ` David Woodhouse
2009-06-24 6:50 ` apgmoorthy
2010-03-31 9:53 ` Amul Kumar Saha
2010-03-31 13:07 ` massimo cirillo
2010-04-05 11:10 ` Amul Kumar Saha
2010-04-05 11:52 ` massimo cirillo
2010-04-09 9:21 ` Amul Kumar Saha
2010-04-13 9:45 ` massimo cirillo
[not found] ` <D4189C368A9B4BD986B7B98A0F05953B@sisodomain.com>
2010-04-15 21:03 ` massimo cirillo
2010-04-15 21:26 ` massimo cirillo
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 20:46 [patch 01/14] mtd: Flex-OneNAND support akpm
2009-05-15 15:38 ` Artem Bityutskiy
2009-05-15 15:39 ` Artem Bityutskiy
2009-05-15 22:07 ` Kevin Cernekee
2009-05-16 4:51 ` Andrew Morton
2009-05-23 9:35 ` 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=1243251718.21646.107.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=amul.saha@samsung.com \
--cc=dwmw2@infradead.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-mtd@lists.infradead.org \
--cc=moorthy.apg@samsung.com \
--cc=vishak.g@samsung.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