From: "Emilio López" <emilio@elopez.com.ar>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Cc: maxime.ripard@free-electrons.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: stmmac: potential circular locking dependency
Date: Mon, 03 Nov 2014 11:48:13 -0300 [thread overview]
Message-ID: <545795AD.6090303@elopez.com.ar> (raw)
In-Reply-To: <545793B6.5010109@st.com>
El 03/11/14 a las 11:39, Giuseppe CAVALLARO escibió:
> Hello Emilio
>
> I have a subset of new patches to review and fix locks in the
> driver. I will plan to send them in the next days.
Great then :) Please Cc: me on the patches when you send them
Cheers,
Emilio
prev parent reply other threads:[~2014-11-03 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 14:36 stmmac: potential circular locking dependency Emilio López
2014-11-03 14:39 ` Giuseppe CAVALLARO
2014-11-03 14:48 ` Emilio López [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=545795AD.6090303@elopez.com.ar \
--to=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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).