linux-kernel - RE: [PATCH v2 0/2] cxgb3/cxgb3i: added support of private MAC address and provisioning packet handler for iSCSI

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] [day] [month] [year] [list]

Message-ID: <8A71B368A89016469F72CD08050AD334066E713E@maui.asicdesigners.com>
Date:	Sat, 26 Sep 2009 11:55:36 -0700
From:	"Karen Xie" <kxie@...lsio.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<michaelc@...wisc.edu>, <James.Bottomley@...senPartnership.com>,
	"Steve Wise" <swise@...ngridcomputing.com>,
	"Divy Le Ray" <divy@...lsio.com>,
	"Rakesh Ranjan" <rakesh@...lsio.com>, <linux-scsi@...r.kernel.org>,
	<open-iscsi@...glegroups.com>, <linux-kernel@...r.kernel.org>,
	<netdev@...r.kernel.org>
Subject: RE: [PATCH v2 0/2] cxgb3/cxgb3i: added support of private MAC address and provisioning packet handler for iSCSI

Thanks, understood.

We are submitting a new version that would be isolated to changes to the
net driver only and would not affect scsi driver.

Thanks a lot.
Karen

-----Original Message-----
From: David Miller [mailto:davem@...emloft.net] 
Sent: Saturday, September 26, 2009 12:17 AM
To: Karen Xie
Cc: michaelc@...wisc.edu; James.Bottomley@...senPartnership.com; Steve
Wise; Divy Le Ray; Rakesh Ranjan; linux-scsi@...r.kernel.org;
open-iscsi@...glegroups.com; linux-kernel@...r.kernel.org;
netdev@...r.kernel.org
Subject: Re: [PATCH v2 0/2] cxgb3/cxgb3i: added support of private MAC
address and provisioning packet handler for iSCSI

From: "Karen Xie" <kxie@...lsio.com>
Date: Fri, 25 Sep 2009 15:34:22 -0700

> Hmm, I am wondering how could this merge activity to be coordinated?
If
> only the driver/scsi change is merged, then it won't compile either,
> since it requires the driver/net change.

That's rediculious, frankly.

Since they are two seperate changes you are knowingly creating
a bisection point that will not work.  That's wrong.

You need to split up the changes so that each and every one of them
are independant and the tree can be checked out at either of them and
everything can be expected to work.
--
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/