From: David Miller <davem@davemloft.net>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org, linus.walleij@stericsson.com,
sjurbren@gmail.com, daniel.martensson@stericsson.com
Subject: Re: [PATCHv2] caif: Add CAIF HSI Link Layer
Date: Mon, 11 Apr 2011 13:08:44 -0700 (PDT) [thread overview]
Message-ID: <20110411.130844.183063120.davem@davemloft.net> (raw)
In-Reply-To: <1302552320-11549-1-git-send-email-sjur.brandeland@stericsson.com>
From: sjur.brandeland@stericsson.com
Date: Mon, 11 Apr 2011 22:05:20 +0200
> I've made cfhsi_tx_frm lock protected (by moving some spin_unlock)
> and added a WARN_ON(!spin_is_locked(...)) to be safe.
spin_is_locked() always returns false on uniprocessor builds.
prev parent reply other threads:[~2011-04-11 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 20:05 [PATCHv2] caif: Add CAIF HSI Link Layer sjur.brandeland
2011-04-11 20:08 ` David Miller [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=20110411.130844.183063120.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.martensson@stericsson.com \
--cc=linus.walleij@stericsson.com \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.com \
--cc=sjurbren@gmail.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).