mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: David Woodhouse <dwmw2@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Wolfgang Grandegger <wg@grandegger.com>,
	linux-kernel Kernel <linux-kernel@vger.kernel.org>,
	linux-ppc list <linuxppc-dev@ozlabs.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH for 2.6.28] NAND: fsl_upm: fix build problem with 2.6.28-rc2
Date: Wed, 3 Dec 2008 10:43:12 -0600	[thread overview]
Message-ID: <965E56B6-4317-448E-9541-9CB1615E623B@kernel.crashing.org> (raw)
In-Reply-To: <20081203162723.GA32301@oksana.dev.rtsoft.ru>


On Dec 3, 2008, at 10:27 AM, Anton Vorontsov wrote:

> On Wed, Dec 03, 2008 at 09:47:53AM -0600, Kumar Gala wrote:
> [...]
>>> The patch fixes following build error:
>>>
>>> CC      drivers/mtd/nand/fsl_upm.o
>>> drivers/mtd/nand/fsl_upm.c: In function 'fun_chip_init':
>>> drivers/mtd/nand/fsl_upm.c:168: warning: passing argument 2 of
>>> 'of_mtd_parse_partitions' from incompatible pointer type
>>> drivers/mtd/nand/fsl_upm.c:168: warning: passing argument 3 of
>>> 'of_mtd_parse_partitions' from incompatible pointer type
>>> drivers/mtd/nand/fsl_upm.c:168: error: too many arguments to  
>>> function
>>> 'of_mtd_parse_partitions'
>>> make[1]: *** [drivers/mtd/nand/fsl_upm.o] Error 1
>>>
>>> The breakage was introduced in
>>> 69fd3a8d098faf41a04930afa83757c0555ee360
>>> ("[MTD] remove unused mtd parameter in of_mtd_parse_partitions()").
>>>
>>> While at it, also add a check for the of_mtd_parse_partitions()  
>>> return
>>> value.
>>>
>>> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
>>> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> [...]
>> David,
>>
>> what's going on with this patch?
>
> Recently I got email from Andrew's patch tracking system that
> the patch was merged into subsystem tree. Here it is:
>
> http://git.infradead.org/mtd-2.6.git?a=commitdiff;h=29b65861fbece04cfdf3fee352d5247369131850

is it going into 2.6.28 or waiting for .29?

- k

      reply	other threads:[~2008-12-03 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 16:38 Anton Vorontsov
2008-12-03 15:47 ` Kumar Gala
2008-12-03 16:27   ` Anton Vorontsov
2008-12-03 16:43     ` Kumar Gala [this message]

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=965E56B6-4317-448E-9541-9CB1615E623B@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=wg@grandegger.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

all inboxes | Powered by JetHome®