From: Artem Bityutskiy <dedekind1@gmail.com>
To: Vimal Singh <vimal.newwork@gmail.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] Fixing compilation warning for 'nand/omap2.c'
Date: Tue, 10 Nov 2009 16:26:41 +0200 [thread overview]
Message-ID: <1257863201.21596.766.camel@localhost> (raw)
In-Reply-To: <1257862827.21596.760.camel@localhost>
On Tue, 2009-11-10 at 16:20 +0200, Artem Bityutskiy wrote:
> On Tue, 2009-11-03 at 14:31 +0530, Vimal Singh wrote:
> > >> diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> > >> index 090ab87..92573d5 100644
> > >> --- a/drivers/mtd/nand/omap2.c
> > >> +++ b/drivers/mtd/nand/omap2.c
> > >> @@ -501,11 +501,13 @@ static void omap_read_buf_dma_pref(struct
> > >> mtd_info *mtd, u_char
> > >
> > > :-) It is the same again.
> > >
> > > Try to send the e-mail to yourself, then save it and apply with git-am.
> > > If it works, send to the mailing list.
> >
> > Below patch applies. Sorry for noise... :(
> >
> > Thanks,
> > vimal
> >
> >
> > From eebbd81141b196af2dc3f7a2650ce16b6b0d76ae Mon Sep 17 00:00:00 2001
> > From: Vimal Singh <vimalsingh@ti.com>
> > Date: Fri, 30 Oct 2009 11:31:34 +0530
> > Subject: [PATCH] Fixing compilation warning for 'nand/omap2.c'
> >
> > Fixing below warning in compilation:
> > drivers/mtd/nand/omap2.c: In function 'omap_write_buf_dma_pref':
> > drivers/mtd/nand/omap2.c:508: warning: passing argument 2 of
> > 'omap_nand_dma_transfer' discards qualifiers from pointer target type
> >
> > Signed-off-by: Vimal Singh <vimalsingh@ti.com>
> > ---
> > drivers/mtd/nand/omap2.c | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> > index 090ab87..92573d5 100644
> > --- a/drivers/mtd/nand/omap2.c
> > +++ b/drivers/mtd/nand/omap2.c
> > @@ -501,11 +501,13 @@ static void omap_read_buf_dma_pref(struct
> > static void omap_write_buf_dma_pref(struct mtd_info *mtd,
> > const u_char *buf, int len)
> > {
> > + u_char *p = (u_char *)buf;
> > +
> > if (len <= mtd->oobsize)
> > - omap_write_buf_pref(mtd, buf, len);
> > + omap_write_buf_pref(mtd, p, len);
> > else
> > /* start transfer in DMA mode */
> > - omap_nand_dma_transfer(mtd, buf, len, 0x1);
> > + omap_nand_dma_transfer(mtd, p, len, 0x1);
> > }
>
> I think that you should instead remove the 'const' modifier from the
> 'omap_write_buf_dma_pref()' function. Indeed, if it has the 'const'
> modifier, it should never change the bugger.
Sorry, s/bugger/buffer/
:-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-10 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ce9ab5790910292321nf230810v353c23f9c1ce1931@mail.gmail.com>
2009-10-30 8:42 ` [PATCH 1/3] Fixing compilation warning for 'nand/omap2.c' Vimal Singh
2009-11-03 8:18 ` Artem Bityutskiy
2009-11-03 8:38 ` Vimal Singh
2009-11-03 8:42 ` Artem Bityutskiy
2009-11-03 9:01 ` Vimal Singh
2009-11-10 14:20 ` Artem Bityutskiy
2009-11-10 14:26 ` Artem Bityutskiy [this message]
2009-11-11 4:40 ` Vimal Singh
2009-11-10 14:24 ` Artem Bityutskiy
2009-11-11 4:44 ` Vimal Singh
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=1257863201.21596.766.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=vimal.newwork@gmail.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