From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ti-dma-crossbar: Fix possible race condition with dma_inuse
Date: Fri, 22 Sep 2017 14:13:01 +0530 [thread overview]
Message-ID: <20170922084300.GP30097@localhost> (raw)
In-Reply-To: <9ed74f0c-9363-efbf-3fdf-47ebd1fd4eea@ti.com>
On Fri, Sep 22, 2017 at 10:03:59AM +0300, Peter Ujfalusi wrote:
> Vinod,
>
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
> On 2017-09-21 20:30, Vinod Koul wrote:
> > On Thu, Sep 21, 2017 at 02:35:32PM +0300, Peter Ujfalusi wrote:
> >> When looking for unused xbar_out lane we should also protect the set_bit()
> >> call with the same mutex to protect against concurrent threads picking the
> >> same ID.
> >
> > Applied, thanks
> >
> > Just a note, somehow the patches from you only are getting mangled for me.
> > Curiously, the ones in patchworks are fine and I used to apply that, not sure
> > what mail servers at our work places are doing!!
>
> I'm afraid it is our mail servers where the mangling is happening :(
> We are trying to resolve this since early August when it first started
> to happen (and only for the guys in Finland).
> We are as frustrated as one can be, believe me.
>
> PS: And the mangler will add a footer on top of this mail
ah okay, consider sending using some other server then, or just put up a
linux box in the corner like we do (@linux.intel.com)
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: ti-dma-crossbar: Fix possible race condition with dma_inuse
Date: Fri, 22 Sep 2017 14:13:01 +0530 [thread overview]
Message-ID: <20170922084300.GP30097@localhost> (raw)
In-Reply-To: <9ed74f0c-9363-efbf-3fdf-47ebd1fd4eea@ti.com>
On Fri, Sep 22, 2017 at 10:03:59AM +0300, Peter Ujfalusi wrote:
> Vinod,
>
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
> On 2017-09-21 20:30, Vinod Koul wrote:
> > On Thu, Sep 21, 2017 at 02:35:32PM +0300, Peter Ujfalusi wrote:
> >> When looking for unused xbar_out lane we should also protect the set_bit()
> >> call with the same mutex to protect against concurrent threads picking the
> >> same ID.
> >
> > Applied, thanks
> >
> > Just a note, somehow the patches from you only are getting mangled for me.
> > Curiously, the ones in patchworks are fine and I used to apply that, not sure
> > what mail servers at our work places are doing!!
>
> I'm afraid it is our mail servers where the mangling is happening :(
> We are trying to resolve this since early August when it first started
> to happen (and only for the guys in Finland).
> We are as frustrated as one can be, believe me.
>
> PS: And the mangler will add a footer on top of this mail
ah okay, consider sending using some other server then, or just put up a
linux box in the corner like we do (@linux.intel.com)
--
~Vinod
next prev parent reply other threads:[~2017-09-22 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 11:35 [PATCH] dmaengine: ti-dma-crossbar: Fix possible race condition with dma_inuse Peter Ujfalusi
2017-09-21 11:35 ` Peter Ujfalusi
2017-09-21 11:35 ` Peter Ujfalusi
2017-09-21 17:30 ` Vinod Koul
2017-09-21 17:30 ` Vinod Koul
2017-09-22 7:03 ` Peter Ujfalusi
2017-09-22 7:03 ` Peter Ujfalusi
2017-09-22 7:03 ` Peter Ujfalusi
2017-09-22 8:43 ` Vinod Koul [this message]
2017-09-22 8:43 ` Vinod Koul
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=20170922084300.GP30097@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=stable@vger.kernel.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.