From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: ext Kyungmin Park <kmpark@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH 0/4] MTD: OneNAND: Fix samsung SoCs various bugs
Date: Tue, 28 Sep 2010 13:03:29 +0300 [thread overview]
Message-ID: <1285668209.2437.70.camel@localhost> (raw)
In-Reply-To: <AANLkTi=d3YZEMBMKU9-RVjXQEfF3eWGxesVJ5japEwjX@mail.gmail.com>
On Tue, 2010-09-28 at 12:02 +0200, ext Kyungmin Park wrote:
> On Tue, Sep 28, 2010 at 3:25 PM, Artem Bityutskiy
> <Artem.Bityutskiy@nokia.com> wrote:
> > On Mon, 2010-09-27 at 16:24 +0900, Kyungmin Park wrote:
> >> The following changes since commit 32163f4b2cef28a5aab8b226ffecfc6379a53786:
> >> Al Viro (1):
> >> alpha: fix usp value in multithreaded coredumps
> >>
> >> Kyungmin Park (4):
> >> MTD: OneNAND: Remove unused cmd_map at s5pc110
> >> MTD: OneNAND: S5PC100: Only S5PC110 use the command map method
> >> MTD: OneNAND: S5PC110: Fix wrong DMA hanlding when HIGHMEM
> >> MTD: OneNAND: S5PC110: Add timeout to prevent the endless loop
> >>
> >> drivers/mtd/onenand/samsung.c | 45 +++++++++++++++++++++++++++-------------
> >> 1 files changed, 30 insertions(+), 15 deletions(-)
> >
> > Some patches are already in my l2-mtd-2.6.git tree, could you please
> > send the series against the l2 tree so that I could apply it?
>
> I tried to clone you tree. but it's too slow since internal network issue.
> I will send it tomorrow.
Always use --reference linux-2.6 when cloning linux trees and it'll be
faster.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-09-28 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 7:24 [PATCH 0/4] MTD: OneNAND: Fix samsung SoCs various bugs Kyungmin Park
2010-09-28 6:25 ` Artem Bityutskiy
2010-09-28 10:02 ` Kyungmin Park
2010-09-28 10:03 ` Artem Bityutskiy [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=1285668209.2437.70.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=dwmw2@infradead.org \
--cc=kmpark@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).