linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: rmk back but still recovering (was Re: Reminder - rmk still on vacation)
Date: Mon, 30 Jul 2012 16:25:41 +0100	[thread overview]
Message-ID: <20120730152541.GI7405@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CABxcv=msMZ7ufh2ROeEry1eY7HbXU8GRB5RkZx1x6asAx3CZ=w@mail.gmail.com>

On Mon, Jul 30, 2012 at 05:19:06PM +0200, Javier Martinez Canillas wrote:
> On Mon, Jul 30, 2012 at 4:46 PM, S, Venkatraman <svenkatr@ti.com> wrote:
> > On Mon, Jul 30, 2012 at 8:14 PM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> >> On Mon, Jul 30, 2012 at 04:37:09PM +0200, Shilimkar, Santosh wrote:
> >>> On Mon, Jul 30, 2012 at 4:33 PM, Russell King - ARM Linux
> >>> <linux@arm.linux.org.uk> wrote:
> >>> > So I take that as you wanting exactly what is in linux-next merged without
> >>> > any further changes?
> >>>
> >>> Just one patch[1] on top of that so that default omap2plus_defconfig
> >>> keeps working.
> >>
> >> Err, I don't see what that patch does.  Setting ret=-ENXIO at the
> >> start of the function, when it's subsequently overwritten by:
> >>
> >> +       int ret = -ENXIO, irq;
> >> ...
> >>         ret = omap_hsmmc_gpio_init(pdata);
> >> ...
> >>         ... dma stuff ...
> >>
> >> seems absurd.
> >
> > I think Santosh meant this patch..
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=commitdiff;h=55936cdfaaf11ac352b56bc58e42d6661e65ee13
> 
> That is the patch that fixes the DMA issue with the OMAP MMC and OMAP
> MMC HS drivers when OMAP_DMA option is not set, since they still don't
> support poll mode without DMA.
> 
> Russell, are you going to take the patch from Tony's linux-omap/master
> tree or do I have to add the patch to the patch system also?

It'd be better to have it via the patch system, because pulling it out
of a URL isn't an easy task.

  reply	other threads:[~2012-07-30 15:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 14:12 Reminder - rmk still on vacation Russell King - ARM Linux
2012-07-27 13:42 ` rmk back but still recovering (was Re: Reminder - rmk still on vacation) Russell King - ARM Linux
2012-07-27 15:20   ` Jon Hunter
2012-07-27 15:28     ` Russell King - ARM Linux
2012-07-27 16:08   ` Shilimkar, Santosh
2012-07-27 16:50     ` Russell King - ARM Linux
2012-07-28  8:10       ` Shilimkar, Santosh
2012-07-30  5:51         ` S, Venkatraman
2012-07-30  7:40           ` Shilimkar, Santosh
2012-07-30  8:26             ` Shubhrajyoti Datta
2012-07-30 14:33             ` Russell King - ARM Linux
2012-07-30 14:37               ` Shilimkar, Santosh
2012-07-30 14:44                 ` Russell King - ARM Linux
2012-07-30 14:46                   ` S, Venkatraman
2012-07-30 15:19                     ` Javier Martinez Canillas
2012-07-30 15:25                       ` Russell King - ARM Linux [this message]
2012-07-30 17:02                         ` Tony Lindgren
2012-07-30 17:17                           ` Javier Martinez Canillas
2012-07-30 14:45             ` Russell King - ARM Linux

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=20120730152541.GI7405@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@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).