linux-kernel - RE: [PATCH 2/5] bfa: Brocade BFA FC SCSI driver submission

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C94DE2070B172459E4F1EE14BD2364E02753674@HQ-EXCH-5.corp.brocade.com>
Date:	Wed, 28 Jan 2009 10:02:43 -0800
From:	"Jing Huang" <huangj@...cade.COM>
To:	"James Bottomley" <James.Bottomley@...senPartnership.com>
Cc:	"Christoph Hellwig" <hch@...radead.org>,
	"Krishna Gudipati" <kgudipat@...cade.com>,
	<linux-kernel@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
	"Ramkumar Vadivelu" <rvadivel@...cade.COM>,
	"Vinodh Ravindran" <vravindr@...cade.COM>
Subject: RE: [PATCH 2/5] bfa: Brocade BFA FC SCSI driver submission

James Bottomley Wrote:
> > > > + * Generic HAL callback element.
> > > > + */
> > > > +struct bfa_cb_qe_s {
> > > > +	struct bfa_q_s         qe;
> > > > +	bfa_cb_cbfn_t  cbfn;
> > > > +	bfa_boolean_t   once;
> > > > +	u32		rsvd;
> > > > +	void           *cbarg;
> > > > +};
> > > > +
> > > > +#define bfa_cb_queue(__bfa, __hcb_qe, __cbfn, __cbarg) do {
> > \
> > > > +	(__hcb_qe)->cbfn  = (__cbfn);
> > \
> > > > +	(__hcb_qe)->cbarg = (__cbarg);
> > \
> > > > +	bfa_q_enq(&(__bfa)->comp_q, (__hcb_qe));
> > \
> > > > +} while (0)
> > >
> > > Please stop here, weird HALs and own list management routines are
not
> > > things we put into the tree.  (except for gregs junk
subdirectory..)
> > >
> > > Please rewrite this into a proper Linux driver.
> >
> >
> > Thanks Christoph for the code review,
> >
> > I will clean up all the HAL references and also replace our own list
> > management code with standard linux implementation.
> 
> This might take a while.  I can offer to put this driver in the
staging
> tree while you work on it if that would be helpful?
> 
> The way the staging tree works is that drivers are held in a separate
> area (drivers/staging) in the linux kernel while they're being worked
> on.  The driver can be installed by users while it's in the staging
tree
> (so made use of) but it will taint the kernel with a warning that it's
> not of linux kernel quality yet.  Once we get an acceptable driver in
> drivers/staging, I'll move it across to drivers/scsi and remove the
> taint.
> 
> James
> 
> 

This is definitely helpful, thanks James!

Jing

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/