All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Cory Maccarrone <darkstar6262@gmail.com>
Cc: Ladislav Michl <ladis@linux-mips.org>,
	linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
	Marek Belisko <marek.belisko@open-nandra.com>
Subject: Re: [PATCH v5 resubmit] mmc-omap: Add support for 16-bit and 32-bit registers
Date: Mon, 11 Jan 2010 15:31:54 -0800	[thread overview]
Message-ID: <20100111233153.GG5055@atomide.com> (raw)
In-Reply-To: <6cb013311001111114g6cd49663ja9f2099b6431d28@mail.gmail.com>

* Cory Maccarrone <darkstar6262@gmail.com> [100111 11:13]:
> On Mon, Jan 11, 2010 at 2:44 AM, Ladislav Michl
> <Ladislav.Michl@seznam.cz> wrote:
> >
> > This patch differs from v5 you sent earlier:
> >  Subject: [PATCH v5] mmc-omap: Add support for 16-bit and 32-bit registers
> >  Date: Mon, 23 Nov 2009 10:37:28 -0800
> >  Message-Id: <1259001448-9574-1-git-send-email-darkstar6262@gmail.com>
> >
> > Patch below is not going to work with 32-bit wide registers. Whoever is going
> > to apply it, please don't. Use original version referred above.
> >
> > <snip>
> >
> > This is not going to work       ^^^^^^^^^^^^
> 
> Ah, right, good catch.  I thought I got the same one submitted -- this
> is an older one.  Sorry about that.

I'll add the working v5 into omap-testing so we can make sure it works with
other omaps. Will not merge it further, it still needs to get to mainline
via linux-mmc list.

Regards,

Tony

      reply	other threads:[~2010-01-11 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 17:52 [PATCH v5 resubmit] mmc-omap: Add support for 16-bit and 32-bit registers Cory Maccarrone
2010-01-11 10:44 ` Ladislav Michl
2010-01-11 19:14   ` Cory Maccarrone
2010-01-11 23:31     ` Tony Lindgren [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=20100111233153.GG5055@atomide.com \
    --to=tony@atomide.com \
    --cc=darkstar6262@gmail.com \
    --cc=ladis@linux-mips.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@open-nandra.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.