From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dmaengine@vger.kernel.org, swathi.kovvuri@intel.com
Subject: Re: [PATCH] dmaengine: check device and channel list for empty
Date: Fri, 26 Jun 2020 12:09:15 +0530 [thread overview]
Message-ID: <20200626063915.GF6228@vkoul-mobl> (raw)
In-Reply-To: <c27b6058-a406-e6bd-55cd-15b67ab89f48@intel.com>
On 25-06-20, 11:31, Dave Jiang wrote:
>
>
> On 6/24/2020 12:29 AM, Vinod Koul wrote:
> > On 15-05-20, 12:22, Dave Jiang wrote:
> > > Check dma device list and channel list for empty before iterate as the
> > > iteration function assume the list to be not empty. With devices and
> > > channels now being hot pluggable this is a condition that needs to be
> > > checked. Otherwise it can cause the iterator to spin forever.
> >
> > Can you rebase and resend, they dont apply on next
>
> Hi Vinod. I'm trying to figure out how to do all the patches outstanding to
> avoid conflicts for you. Some will go to your fixes branch and some will go
> to the next branch. But next doesn't have the patches in fixes. So when you
> merge next later for 5.9, you are going to hit conflict from my patches that
> went in through the fixes branch for 5.8.
I dont typically merge fixes, unless we have a conflicts. I can merge if
there are conflicts, just let me know :-)
--
~Vinod
prev parent reply other threads:[~2020-06-26 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 19:22 [PATCH] dmaengine: check device and channel list for empty Dave Jiang
2020-06-05 18:58 ` Dave Jiang
2020-06-24 7:29 ` Vinod Koul
2020-06-25 18:31 ` Dave Jiang
2020-06-26 6:39 ` Vinod Koul [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=20200626063915.GF6228@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=swathi.kovvuri@intel.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 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).