From: David Woodhouse <dwmw2@infradead.org>
To: "Singh,
Vimal"
<IMCEAEX-_O=TI_OU=BD_CN=RECIPIENTS_CN=X0094262@dlee86.itg.ti.com>
Cc: "david-b@pacbell.net" <david-b@pacbell.net>,
"tom.leiming@gmail.com" <tom.leiming@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jzhang@ti.com" <jzhang@ti.com>
Subject: RE: [PATCH][MTD][NAND]: fix omap2.c compile failure and warning
Date: Fri, 26 Jun 2009 17:18:59 +0100 [thread overview]
Message-ID: <1246033139.663.35.camel@macbook.infradead.org> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404321C60D1@dbde02.ent.ti.com>
On Fri, 2009-06-26 at 21:15 +0530, Singh, Vimal wrote:
>
> That's correct David. I think 'cond_resched()' would be fine here.
Got a patch? I have you down as the person responsible for this driver,
given that jzhang@ti.com is bouncing...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
WARNING: multiple messages have this Message-ID (diff)
From: David Woodhouse <dwmw2@infradead.org>
To: "Singh,
Vimal"
<IMCEAEX-_O=TI_OU=BD_CN=RECIPIENTS_CN=X0094262@dlee86.itg.ti.com>
Cc: "tom.leiming@gmail.com" <tom.leiming@gmail.com>,
"jzhang@ti.com" <jzhang@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"david-b@pacbell.net" <david-b@pacbell.net>
Subject: RE: [PATCH][MTD][NAND]: fix omap2.c compile failure and warning
Date: Fri, 26 Jun 2009 17:18:59 +0100 [thread overview]
Message-ID: <1246033139.663.35.camel@macbook.infradead.org> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404321C60D1@dbde02.ent.ti.com>
On Fri, 2009-06-26 at 21:15 +0530, Singh, Vimal wrote:
>
> That's correct David. I think 'cond_resched()' would be fine here.
Got a patch? I have you down as the person responsible for this driver,
given that jzhang@ti.com is bouncing...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-06-26 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 13:21 [PATCH][MTD][NAND]: fix omap2.c compile failure and warning tom.leiming
2009-06-26 13:21 ` tom.leiming
2009-06-26 15:09 ` David Woodhouse
2009-06-26 15:09 ` David Woodhouse
2009-06-26 15:45 ` Singh, Vimal
2009-06-26 15:45 ` Singh, Vimal
2009-06-26 16:18 ` David Woodhouse [this message]
2009-06-26 16:18 ` David Woodhouse
[not found] <53729.192.168.10.89.1246035472.squirrel@dbdmail.itg.ti.com>
2009-06-26 17:02 ` vimal singh
2009-06-26 17:02 ` vimal singh
2009-06-26 17:14 ` David Woodhouse
2009-06-26 17:14 ` David Woodhouse
[not found] ` <57946.192.168.10.89.1246035774.squirrel@dbdmail.itg.ti.com>
2009-06-27 5:37 ` vimal singh
2009-06-27 5:37 ` vimal singh
2009-06-27 7:45 ` David Woodhouse
2009-06-27 7:45 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2009-06-28 5:40 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=1246033139.663.35.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=IMCEAEX-_O=TI_OU=BD_CN=RECIPIENTS_CN=X0094262@dlee86.itg.ti.com \
--cc=david-b@pacbell.net \
--cc=jzhang@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tom.leiming@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.