[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUhuC-8vfXKNLmONexnQeokX4xFLNR=MVXFOSWE1O3Hsg@mail.gmail.com>
Date: Mon, 6 Jul 2015 11:24:20 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Lee Jones <lee.jones@...aro.org>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Vinod Koul <vinod.koul@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dmaengine@...r.kernel.org,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
Mike Turquette <mturquette@...aro.org>
Subject: Re: [PATCH v4 6/8] mfd: make mfd_remove_devices() iterate in reverse order
On Mon, Jul 6, 2015 at 11:10 AM, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
> On Wed, 2015-06-24 at 12:31 +0100, Lee Jones wrote:
>> On Mon, 15 Jun 2015, Andy Shevchenko wrote:
>>
>> > The newly introduced device_for_each_child_reverse() would be used
>> > when MFD
>> > core removes the device.
>> >
>> > After this patch applied the devices will be removed in a reversed
>> > order. This
>> > behaviour is useful when devices have implicit dependency on order,
>> > i.e.
>> > consider MFD device with serial bus controller, such as SPI, and
>> > DMA IP that is
>> > attached to serial bus controller: before remove the DMA driver we
>> > have to be
>> > ensured that no DMA transfers is ongoing and the requested channel
>> > are unused.
>> >
>> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>> > ---
>> > drivers/mfd/mfd-core.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Applied, thanks.
>
> Hmm… Seems kinda mistake. I can't see this applied (and required
> previous patches 4 and 5) to any of your branch neither in (today's)
> linux-next.
New stuff applied after v4.1 couldn't show up in -next before v4.2-rc1 was
released (which just happened last night)?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists