All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: vinod.koul@intel.com, devicetree-discuss@lists.ozlabs.org,
	spear-devel@list.st.com, linux-kernel@vger.kernel.org,
	andriy.shevchenko@linux.intel.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Fri, 26 Oct 2012 14:40:56 +0530	[thread overview]
Message-ID: <1351242656.7077.20.camel@vkoul-udesk3> (raw)
In-Reply-To: <CAKohpo=4QDBuFZJrdCkXzijx4aD0rNXf1X2wS9LG17zg_LeAYg@mail.gmail.com>

On Fri, 2012-10-26 at 14:35 +0530, Viresh Kumar wrote:
> >> I can see that you applied these patches and they are present in
> >> linux-next. But i feel
> >> the order of patches is bad.
> > Yes looks like I forgot to sort the mbox series :(
> >
> > since all patches were applied nicely, and they seem fairly independent
> > of each other it should cause issue. Let me know if you wnat me to redo
> > my -next.
> 
> yes. The ARCH specific patch 3/3 uses a routine created in 2/3. So they have
> to be in right order for git bisect to work. 

Done, it should reflect now.
Sorry for the mess.

-- 
Vinod Koul
Intel Corp.


WARNING: multiple messages have this Message-ID (diff)
From: vkoul@infradead.org (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Fri, 26 Oct 2012 14:40:56 +0530	[thread overview]
Message-ID: <1351242656.7077.20.camel@vkoul-udesk3> (raw)
In-Reply-To: <CAKohpo=4QDBuFZJrdCkXzijx4aD0rNXf1X2wS9LG17zg_LeAYg@mail.gmail.com>

On Fri, 2012-10-26 at 14:35 +0530, Viresh Kumar wrote:
> >> I can see that you applied these patches and they are present in
> >> linux-next. But i feel
> >> the order of patches is bad.
> > Yes looks like I forgot to sort the mbox series :(
> >
> > since all patches were applied nicely, and they seem fairly independent
> > of each other it should cause issue. Let me know if you wnat me to redo
> > my -next.
> 
> yes. The ARCH specific patch 3/3 uses a routine created in 2/3. So they have
> to be in right order for git bisect to work. 

Done, it should reflect now.
Sorry for the mess.

-- 
Vinod Koul
Intel Corp.

  reply	other threads:[~2012-10-26  9:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16  4:19 [PATCH V3 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Viresh Kumar
2012-10-16  4:19 ` Viresh Kumar
2012-10-16  4:19 ` [PATCH V3 2/3] dmaengine: dw_dmac: Enhance device tree support Viresh Kumar
2012-10-16  4:19   ` Viresh Kumar
2012-10-26  8:55   ` Viresh Kumar
2012-10-26  8:55     ` Viresh Kumar
2012-10-26  8:48     ` Vinod Koul
2012-10-26  8:48       ` Vinod Koul
2012-10-26  9:05       ` Viresh Kumar
2012-10-26  9:05         ` Viresh Kumar
2012-10-26  9:10         ` Vinod Koul [this message]
2012-10-26  9:10           ` Vinod Koul
2012-12-10 22:08   ` Arnd Bergmann
2012-12-10 22:08     ` Arnd Bergmann
2012-12-10 22:21     ` Arnd Bergmann
2012-12-10 22:21       ` Arnd Bergmann
2012-12-12  3:00     ` Viresh Kumar
2012-12-12  3:00       ` Viresh Kumar
2012-12-12  8:40       ` Andy Shevchenko
2012-12-12  8:40         ` Andy Shevchenko
2012-12-12  8:43         ` Viresh Kumar
2012-12-12  8:43           ` Viresh Kumar
2012-12-12  8:43           ` Viresh Kumar
2013-01-08 23:09       ` Arnd Bergmann
2013-01-08 23:09         ` Arnd Bergmann
2012-12-12  8:42     ` Andy Shevchenko
2012-12-12  8:42       ` Andy Shevchenko
2012-10-16  4:19 ` [PATCH V3 3/3] ARM: SPEAr13xx: Pass DW DMAC platform data from DT Viresh Kumar
2012-10-16  4:19   ` Viresh Kumar

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=1351242656.7077.20.camel@vkoul-udesk3 \
    --to=vkoul@infradead.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spear-devel@list.st.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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 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.