From: Jeff Garzik <jeff@garzik.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Christoph Raisch <raisch@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
Thomas Klein <tklein@de.ibm.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] net: ehea: semaphore to mutex
Date: Wed, 26 Mar 2008 00:40:21 -0400 [thread overview]
Message-ID: <47E9D3B5.8030004@garzik.org> (raw)
In-Reply-To: <20080307031621.590778480@mvista.com>
ACK from Jan-Bernd, Thomas, others?
next prev parent reply other threads:[~2008-03-26 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 8:00 [PATCH 1/5] net: ehea: semaphore to mutex Daniel Walker
2008-03-06 8:00 ` [PATCH 2/5] net: ehea: ehea_fw_handles " Daniel Walker
2008-03-06 8:00 ` [PATCH 3/5] net: ehea: locking order correction Daniel Walker
2008-03-06 8:00 ` [PATCH 4/5] net: ehea: bcmc_regs semaphore to mutex Daniel Walker
2008-03-06 8:00 ` [PATCH 5/5] net: ehea: port_lock " Daniel Walker
2008-03-26 4:40 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-06 8:00 [PATCH 1/5] net: ehea: " Daniel Walker
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=47E9D3B5.8030004@garzik.org \
--to=jeff@garzik.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raisch@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.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).