From: Christoph Hellwig <hch@infradead.org>
To: Anil Veerabhadrappa <anilgv@broadcom.com>
Cc: Mike Christie <mchristi@redhat.com>,
Michael Chan <mchan@broadcom.com>,
davem@davemloft.net, netdev@vger.kernel.org,
open-iscsi@googlegroups.com, talm@broadcom.com,
lusinsky@broadcom.com, uri@broadcom.com,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v3 2/2][BNX2]: Add iSCSI support to BNX2 devices.
Date: Sat, 8 Sep 2007 12:59:07 +0100 [thread overview]
Message-ID: <20070908115907.GA8478@infradead.org> (raw)
In-Reply-To: <1189027622.19638.42.camel@dhcp-10-13-106-205.broadcom.com>
On Wed, Sep 05, 2007 at 02:27:02PM -0700, Anil Veerabhadrappa wrote:
> This is a very tricky proposal as this header file is automatically
> generated by a well defined process and is shared between various driver
> supporting multiple platform/OS and the firmware. If it is not of a big
> issue I would like to keep it the way it is.
Most of it should just go away, and the other bits shouldn't change over
the lifetime of the driver except for additions. So there really isn't
any point in auto-generating it.
next prev parent reply other threads:[~2007-09-08 11:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1188599815.5176.12.camel@dell>
2007-09-05 18:34 ` [PATCH v3 2/2][BNX2]: Add iSCSI support to BNX2 devices Mike Christie
2007-09-05 21:27 ` Anil Veerabhadrappa
2007-09-07 22:23 ` Mike Christie
2007-11-21 18:38 ` Anil Veerabhadrappa
2007-11-21 19:17 ` James Smart
[not found] ` <1195670296.8767.9.camel-opBMJL+S1+mb6IhXEaeG+wpgy58w7zIFpWgKQ6/u3Fg@public.gmane.org>
2007-11-27 4:15 ` Mike Christie
2007-11-28 0:44 ` Anil Veerabhadrappa
[not found] ` <1196210691.5980.20.camel-opBMJL+S1+mb6IhXEaeG+20Cxg0+/0ngpWgKQ6/u3Fg@public.gmane.org>
2007-11-28 20:06 ` Mike Christie
2007-11-29 0:36 ` Anil Veerabhadrappa
2007-09-08 11:59 ` Christoph Hellwig [this message]
2007-09-08 14:49 ` Michael Chan
2007-09-08 17:57 ` Anil Veerabhadrappa
2007-09-07 22:36 ` Mike Christie
2007-09-08 7:41 ` FUJITA Tomonori
2007-09-08 11:32 ` Jeff Garzik
2007-09-08 12:00 ` Christoph Hellwig
2007-09-09 15:05 ` FUJITA Tomonori
2007-09-25 8:39 ` Hannes Reinecke
2007-09-26 8:57 ` FUJITA Tomonori
2007-09-27 7:31 ` Jeff Garzik
2007-09-27 7:38 ` Benjamin Herrenschmidt
2007-09-27 7:49 ` Jeff Garzik
2007-09-27 8:12 ` Benjamin Herrenschmidt
2007-09-27 8:22 ` Jeff Garzik
2007-09-27 8:46 ` FUJITA Tomonori
2007-09-27 8:06 ` FUJITA Tomonori
2007-09-27 8:23 ` Jeff Garzik
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=20070908115907.GA8478@infradead.org \
--to=hch@infradead.org \
--cc=anilgv@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-scsi@vger.kernel.org \
--cc=lusinsky@broadcom.com \
--cc=mchan@broadcom.com \
--cc=mchristi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=talm@broadcom.com \
--cc=uri@broadcom.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).