linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
	"artem.bityutskiy@linux.intel.com"
	<artem.bityutskiy@linux.intel.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"ivan.djelic@parrot.com" <ivan.djelic@parrot.com>
Subject: Re: [PATCH v3 10/10] mtd: nand: omap2: use gpmc provided irqs
Date: Tue, 11 Sep 2012 11:21:07 -0700	[thread overview]
Message-ID: <20120911182106.GK23092@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9E1A11@DBDE01.ent.ti.com>

* Mohammed, Afzal <afzal@ti.com> [120910 23:40]:
> Hi Tony,
> 
> On Tue, Sep 11, 2012 at 11:12:27, Tony Lindgren wrote:
> > * Mohammed, Afzal <afzal@ti.com> [120910 22:36]:
> 
> > > I was not careful enough, sorry. Thanks for fixing it.
> > > 
> > > Another hunk as follows would also be required for error
> > > path even though compiler didn't complain.
> > > 
> > > Not sure whether you can fixup or I should post as a
> > > separate patch.
> > 
> > Oh OK, please just post a separate patch as I've
> > already pushed it out.
> 
> I have posted a separate patch, please consider for
> inclusion in your tree.
> 
> BTW, you original commit that fixes the compiler
> warning has some strange characters.

Ah thanks, that's a copy paste UTF-8 issue. I'll just fold
in the fixes and push them out to a new devel-gpmc-fixed
branch.

Regards,

Tony

  reply	other threads:[~2012-09-11 18:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  9:38 [PATCH v3 00/10] Prepare for GPMC driver conversion (w.r.t MTD) Afzal Mohammed
2012-08-21  9:41 ` [PATCH v3 01/10] ARM: OMAP2+: gpmc: update nand register helper Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 02/10] ARM: OMAP2+: gpmc-nand: update gpmc-nand regs Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 03/10] mtd: nand: omap2: handle nand on gpmc Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 04/10] ARM: OMAP2+: gpmc-nand: update resource with memory Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 05/10] ARM: OMAP2+: gpmc-onenand: provide memory as resource Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 06/10] mtd: nand: omap2: obtain memory from resource Afzal Mohammed
2012-08-21  9:43 ` [PATCH v3 07/10] mtd: onenand: " Afzal Mohammed
2012-08-21  9:44 ` [PATCH v3 08/10] ARM: OMAP2+: gpmc: Modify interrupt handling Afzal Mohammed
2012-08-21  9:44 ` [PATCH v3 09/10] ARM: OMAP2+: gpmc-nand: Modify Interrupt handling Afzal Mohammed
2012-08-21  9:44 ` [PATCH v3 10/10] mtd: nand: omap2: use gpmc provided irqs Afzal Mohammed
2012-08-24 19:29   ` Tony Lindgren
2012-08-25 11:48   ` Artem Bityutskiy
2012-08-30 19:53     ` Tony Lindgren
2012-09-11  0:17       ` Tony Lindgren
2012-09-11  5:36         ` Mohammed, Afzal
2012-09-11  5:42           ` Tony Lindgren
2012-09-11  6:40             ` Mohammed, Afzal
2012-09-11 18:21               ` Tony Lindgren [this message]
2012-09-12  9:21                 ` Mohammed, Afzal

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=20120911182106.GK23092@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=dedekind1@gmail.com \
    --cc=ivan.djelic@parrot.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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).