From: Andrew Morton <akpm@linux-foundation.org>
To: Jing Huang <huangj@brocade.com>
Cc: James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
rvadivel@brocade.com, vravindr@brocade.com
Subject: Re: [PATCH 1/14] bfa: Brocade BFA FC SCSI driver (bfad)
Date: Wed, 2 Sep 2009 12:41:35 -0700 [thread overview]
Message-ID: <20090902124135.aa55f0be.akpm@linux-foundation.org> (raw)
In-Reply-To: <200908280754.n7S7sUMB030191@blc-10-6.brocade.com>
On Fri, 28 Aug 2009 00:54:30 -0700
Jing Huang <huangj@brocade.com> wrote:
> From: Jing Huang <huangj@brocade.com>
>
> This patch contains code that interfaces to upper layer linux kernel, such as
> PCI, SCSI mid-layer and sysfs etc.
>
These patches seem to have been posted a lot of times. Is anyone
paying attention?
> +BFA_TRC_FILE(LDRV, BFAD);
> +
> +static DEFINE_MUTEX(bfad_mutex);
> +int bfad_scan_done;
> +
> +LIST_HEAD(bfad_list);
> +
> +static int bfad_inst;
> +int supported_fc4s;
> +
> +char *host_name;
> +char *os_name;
> +char *os_patch;
> +int num_rports;
> +int num_ios;
> +int num_tms;
> +int num_fcxps;
> +int num_ufbufs;
> +int reqq_size;
> +int rspq_size;
> +int num_sgpgs;
> +int rport_del_timeout = BFA_FCS_RPORT_DEF_DEL_TIMEOUT;
> +int bfa_lun_queue_depth = BFAD_LUN_QUEUE_DEPTH;
> +int bfa_io_max_sge = BFAD_IO_MAX_SGE;
> +int log_level = BFA_LOG_WARNING;
> +int ioc_auto_recover = BFA_TRUE;
> +int ipfc_enable = BFA_FALSE;
> +int ipfc_mtu = -1;
> +int linkup_delay = -1;
eek. These are all kernel-wide global symbols and many of them are
very inappropriately named. They should either be made static or given
a subsystem-specific prefix such as "bfad_".
next prev parent reply other threads:[~2009-09-02 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 7:54 [PATCH 1/14] bfa: Brocade BFA FC SCSI driver (bfad) Jing Huang
2009-08-28 7:54 ` Jing Huang
2009-09-02 19:41 ` Andrew Morton [this message]
2009-09-02 20:02 ` Jing Huang
-- strict thread matches above, loose matches on Subject: below --
2009-09-24 0:46 Jing Huang
2009-09-24 0:46 ` Jing Huang
2009-08-20 6:58 Jing Huang
2009-09-03 14:44 ` Brian King
2009-09-24 2:40 ` Jing Huang
2009-07-25 5:24 Jing Huang
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=20090902124135.aa55f0be.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=huangj@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rvadivel@brocade.com \
--cc=vravindr@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.