From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Mark F. Brown" <mark.brown314@gmail.com>
Cc: linux-mtd@lists.infradead.org, Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: pxa3xx: fix build error when CONFIG_MTD_PARTITIONS is not defined
Date: Thu, 02 Sep 2010 02:20:14 +0300 [thread overview]
Message-ID: <1283383214.2209.63.camel@brekeke> (raw)
In-Reply-To: <1282813011-6187-2-git-send-email-mark.brown314@gmail.com>
On Thu, 2010-08-26 at 04:56 -0400, Mark F. Brown wrote:
> Signed-off-by: Mark F. Brown <mark.brown314@gmail.com>
> ---
> drivers/mtd/nand/pxa3xx_nand.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
Pushed to l2-mtd-2.6 / for-2.6.36, thanks.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pxa3xx: fix build error when CONFIG_MTD_PARTITIONS is not defined
Date: Thu, 02 Sep 2010 02:20:14 +0300 [thread overview]
Message-ID: <1283383214.2209.63.camel@brekeke> (raw)
In-Reply-To: <1282813011-6187-2-git-send-email-mark.brown314@gmail.com>
On Thu, 2010-08-26 at 04:56 -0400, Mark F. Brown wrote:
> Signed-off-by: Mark F. Brown <mark.brown314@gmail.com>
> ---
> drivers/mtd/nand/pxa3xx_nand.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
Pushed to l2-mtd-2.6 / for-2.6.36, thanks.
--
Best Regards,
Artem Bityutskiy (???????? ?????)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Mark F. Brown" <mark.brown314@gmail.com>
Cc: Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: pxa3xx: fix build error when CONFIG_MTD_PARTITIONS is not defined
Date: Thu, 02 Sep 2010 02:20:14 +0300 [thread overview]
Message-ID: <1283383214.2209.63.camel@brekeke> (raw)
In-Reply-To: <1282813011-6187-2-git-send-email-mark.brown314@gmail.com>
On Thu, 2010-08-26 at 04:56 -0400, Mark F. Brown wrote:
> Signed-off-by: Mark F. Brown <mark.brown314@gmail.com>
> ---
> drivers/mtd/nand/pxa3xx_nand.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
Pushed to l2-mtd-2.6 / for-2.6.36, thanks.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-09-01 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 8:56 [PATCH] ARM: pxa3xx: fix build error when CONFIG_MTD_PARTITIONS is not defined Mark F. Brown
2010-08-26 8:56 ` Mark F. Brown
2010-08-26 8:56 ` Mark F. Brown
2010-08-26 8:56 ` Mark F. Brown
2010-08-31 5:51 ` Haojian Zhuang
2010-08-31 5:51 ` Haojian Zhuang
2010-08-31 5:51 ` Haojian Zhuang
2010-08-31 23:31 ` Artem Bityutskiy
2010-08-31 23:31 ` Artem Bityutskiy
2010-08-31 23:31 ` Artem Bityutskiy
2010-09-01 23:20 ` Artem Bityutskiy [this message]
2010-09-01 23:20 ` Artem Bityutskiy
2010-09-01 23:20 ` 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=1283383214.2209.63.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.brown314@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 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.