From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
jgarzik@pobox.com
Subject: Re: [PATCH 5/8] New driver "sfc" for Solarstorm SFC4000 controller (try #8)
Date: Sun, 23 Mar 2008 22:38:41 -0700 (PDT) [thread overview]
Message-ID: <20080323.223841.235095904.davem@davemloft.net> (raw)
In-Reply-To: <20080312012513.GG24160@solarflare.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 12 Mar 2008 01:25:14 +0000
> +/* Writes to a normal 16-byte Falcon register, locking as appropriate. */
> +static inline void falcon_write(struct efx_nic *efx, efx_oword_t *value,
> + unsigned int reg)
> +{
> + unsigned long flags __attribute__ ((unused));
Delete.
> +/* Writes to an 8-byte Falcon SRAM register, locking as appropriate. */
> +static inline void falcon_write_sram(struct efx_nic *efx, efx_qword_t *value,
> + unsigned int index)
> +{
> + unsigned int reg = efx->type->buf_tbl_base + (index * sizeof(*value));
> + unsigned long flags __attribute__ ((unused));
Delete.
> +/* Read from a Falcon register
> + *
> + * This reads an entire 16-byte Falcon register in one go, locking as
> + * appropriate. It is essential to read the first dword first, as this
> + * prompts Falcon to load the current value into the shadow register.
> + */
> +static inline void falcon_read(struct efx_nic *efx, efx_oword_t *value,
> + unsigned int reg)
> +{
> + unsigned long flags __attribute__ ((unused));
Delete.
> +static inline void falcon_read_sram(struct efx_nic *efx, efx_qword_t *value,
> + unsigned int index)
> +{
> + unsigned int reg = efx->type->buf_tbl_base + (index * sizeof(*value));
> + unsigned long flags __attribute__ ((unused));
Delete.
> +/* Write dword to Falcon page-mapped register with an extra lock.
> + *
> + * As for falcon_writel_page(), but for a register that suffers from
> + * SFC bug 3181. Take out a lock so the BIU collector cannot be
> + * confused. */
> +static inline void falcon_writel_page_locked(struct efx_nic *efx,
> + efx_dword_t *value,
> + unsigned int reg,
> + unsigned int page)
> +{
> + unsigned long flags __attribute__ ((unused));
Remove the unused tag, it's wrong.
next prev parent reply other threads:[~2008-03-24 5:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 1:21 [PATCH 0/8] New driver "sfc" for Solarstorm SFC4000 controller (try #8) Ben Hutchings
2008-03-12 1:22 ` [PATCH 1/8] " Ben Hutchings
2008-03-24 5:32 ` David Miller
2008-03-24 10:29 ` Ben Hutchings
2008-03-24 20:22 ` David Miller
2008-03-25 12:54 ` Ben Hutchings
2008-03-25 23:37 ` David Miller
2008-03-26 11:58 ` Ben Hutchings
2008-03-25 15:40 ` Ben Hutchings
2008-03-12 1:23 ` [PATCH 2/8] " Ben Hutchings
2008-03-24 5:35 ` David Miller
2008-03-12 1:24 ` [PATCH 3/8] " Ben Hutchings
2008-03-24 5:36 ` David Miller
2008-03-12 1:24 ` [PATCH 4/8] " Ben Hutchings
2008-03-24 5:37 ` David Miller
2008-03-12 1:25 ` [PATCH 5/8] " Ben Hutchings
2008-03-24 5:38 ` David Miller [this message]
2008-03-12 1:25 ` [PATCH 6/8] " Ben Hutchings
2008-03-24 5:39 ` David Miller
2008-03-12 1:26 ` [PATCH 7/8] " Ben Hutchings
2008-03-24 5:40 ` David Miller
2008-03-12 1:26 ` [PATCH 8/8] " Ben Hutchings
2008-03-12 1:45 ` Ben Hutchings
2008-03-12 2:01 ` David Miller
2008-03-12 2:29 ` David Miller
2008-03-24 5:40 ` David Miller
2008-03-24 8:52 ` Christoph Hellwig
2008-03-24 10:34 ` Ben Hutchings
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=20080323.223841.235095904.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=jgarzik@pobox.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@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 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).