netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: ggrundstrom@neteffect.com
Cc: rdreier@cisco.com, ewg@lists.openfabrics.org, netdev@vger.kernel.org
Subject: Re: [PATCH 5/14] nes: context structures and defines
Date: Tue, 07 Aug 2007 21:50:33 -0400	[thread overview]
Message-ID: <46B92169.6020801@garzik.org> (raw)
In-Reply-To: <200708080103.l7813b7E004778@neteffect.com>

ggrundstrom@neteffect.com wrote:
> QP context structures and defines
> 
> Signed-off-by: Glenn Grundstrom <ggrundstrom@neteffect.com>
> ---
> diff -Nurp NULL ofa_kernel-1.2/drivers/infiniband/hw/nes/nes_context.h
> --- NULL	1969-12-31 18:00:00.000000000 -0600
> +++ ofa_kernel-1.2/drivers/infiniband/hw/nes/nes_context.h	2007-08-06 20:09:04.000000000 -0500
> @@ -0,0 +1,193 @@
> +/*
> + * Copyright (c) 2006 NetEffect, Inc. All rights reserved.
> + *
> + * This software is available to you under a choice of one of two
> + * licenses.  You may choose to be licensed under the terms of the GNU
> + * General Public License (GPL) Version 2, available from the file
> + * COPYING in the main directory of this source tree, or the
> + * OpenIB.org BSD license below:
> + *
> + *     Redistribution and use in source and binary forms, with or
> + *     without modification, are permitted provided that the following
> + *     conditions are met:
> + *
> + *      - Redistributions of source code must retain the above
> + *        copyright notice, this list of conditions and the following
> + *        disclaimer.
> + *
> + *      - Redistributions in binary form must reproduce the above
> + *        copyright notice, this list of conditions and the following
> + *        disclaimer in the documentation and/or other materials
> + *        provided with the distribution.
> + *
> + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> + * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> + * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
> + * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
> + * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
> + * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
> + * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> + * SOFTWARE.
> + */
> +
> +#ifndef NES_CONTEXT_H
> +#define NES_CONTEXT_H
> +
> +struct nes_qp_context {
> +	u32   misc;
> +	u32   cqs;
> +	u32   sq_addr_low;
> +	u32   sq_addr_high;
> +	u32   rq_addr_low;
> +	u32   rq_addr_high;
> +	u32   misc2;
> +	u32   tcpPorts;
> +	u32   ip0;
> +	u32   ip1;
> +	u32   ip2;
> +	u32   ip3;
> +	u32   mss;
> +	u32   arp_index_vlan;
> +	u32   tcp_state_flow_label;
> +	u32   pd_index_wscale;
> +	u32   keepalive;
> +	u32   ts_recent;
> +	u32   ts_age;
> +	u32   snd_nxt;
> +	u32   snd_wnd;
> +	u32   rcv_nxt;
> +	u32   rcv_wnd;
> +	u32   snd_max;
> +	u32   snd_una;
> +	u32   srtt;
> +	u32   rttvar;
> +	u32   ssthresh;
> +	u32   cwnd;
> +	u32   snd_wl1;
> +	u32   snd_wl2;
> +	u32   max_snd_wnd;
> +	u32   ts_val_delta;
> +	u32   retransmit;
> +	u32   probe_cnt;
> +	u32   hte_index;
> +	u32   q2_addr_low;
> +	u32   q2_addr_high;
> +	u32   ird_index;
> +	u32   Rsvd3;
> +	u32   ird_ord_sizes;
> +	u32   mrkr_offset;
> +	u32   aeq_token_low;
> +	u32   aeq_token_high;

I presume this needs the __le32, etc., types?

I presume you have not yet run this through sparse?  Please read and 
follow Documentation/sparse.txt

	Jeff




      reply	other threads:[~2007-08-08  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  1:03 [PATCH 5/14] nes: context structures and defines ggrundstrom
2007-08-08  1:50 ` Jeff Garzik [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=46B92169.6020801@garzik.org \
    --to=jeff@garzik.org \
    --cc=ewg@lists.openfabrics.org \
    --cc=ggrundstrom@neteffect.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdreier@cisco.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).