From: Andrew Morton <akpm@osdl.org>
To: minyard@acm.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
Rocky Craig <rocky.craig@hp.com>
Subject: Re: [PATCH 11/12] IPMI: Fix BT long busy
Date: Sun, 3 Dec 2006 13:26:36 -0800 [thread overview]
Message-ID: <20061203132636.a7ac969d.akpm@osdl.org> (raw)
In-Reply-To: <20061202043921.GG30531@localdomain>
On Fri, 1 Dec 2006 22:39:21 -0600
Corey Minyard <minyard@acm.org> wrote:
>
> The IPMI BT subdriver has been patched to survive "long busy"
> timeouts seen during firmware upgrades and resets. The patch
> never returns the HOSED state, synthesizes response messages with
> meaningful completion codes, and recovers gracefully when the
> hardware finishes the long busy. The subdriver now issues a "Get BT
> Capabilities" command and properly uses those results.
> More informative completion codes are returned on error from
> transaction starts; this logic was propogated to the KCS and
> SMIC subdrivers. Finally, indent and other style quirks were
> normalized.
>
> ...
>
> + BT_CONTROL(BT_CLR_WR_PTR); /* always reset */
argh.
#define BT_STATUS bt->io->inputb(bt->io, 0)
#define BT_CONTROL(x) bt->io->outputb(bt->io, 0, x)
#define BMC2HOST bt->io->inputb(bt->io, 1)
#define HOST2BMC(x) bt->io->outputb(bt->io, 1, x)
#define BT_INTMASK_R bt->io->inputb(bt->io, 2)
#define BT_INTMASK_W(x) bt->io->outputb(bt->io, 2, x)
Please don't write macros which require that the caller have a particular
local variable of a particular name.
In fact, please don't write macros.
All the above would be perfectly nice as
static inline void bt_control(struct si_sm_data *bt, int val)
{
bt->io->outputb(bt->io, val);
}
next prev parent reply other threads:[~2006-12-03 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 4:39 Corey Minyard
2006-12-03 21:26 ` Andrew Morton [this message]
2006-12-04 4:10 ` [Openipmi-developer] " Bela Lubkin
2006-12-08 13:03 ` Rocky Craig
2006-12-08 20:29 ` Andrew Morton
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=20061203132636.a7ac969d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rocky.craig@hp.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
all inboxes | Powered by JetHome®