[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120912.014746.636228439025755624.davem@davemloft.net>
Date: Wed, 12 Sep 2012 01:47:46 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: naresh@...lsio.com
Cc: JBottomley@...allels.com, linux-scsi@...r.kernel.org,
dm@...lsio.com, leedom@...lsio.com, netdev@...r.kernel.org,
chethan@...lsio.com
Subject: Re: [V3 PATCH 9/9] cxgb4vf: Chelsio FCoE offload driver submission
(header compatibility fixes).
From: Naresh Kumar Inna <naresh@...lsio.com>
Date: Wed, 12 Sep 2012 11:05:22 +0530
> On 9/11/2012 11:03 PM, David Miller wrote:
>> From: Naresh Kumar Inna <naresh@...lsio.com>
>> Date: Tue, 11 Sep 2012 20:09:07 +0530
>>
>>> This patch contains minor fixes to make cxgb4vf driver work with the updates to
>>> shared firmware/hardware header files.
>>>
>>> Signed-off-by: Naresh Kumar Inna <naresh@...lsio.com>
>>
>> You cannot submit a patch set that isn't bisectable, and in particular
>> create a situation that mid-way through your patch set things do not
>> build or operate correctly.
>>
>
> Sorry, I am new to this process. The reason I did that was because I was
> not sure if I could create a single patch with both cxgb4 and cxgb4vf
> files in it, since they are two different subsystems. If I could do
> that, the single patch then would build on its own, and not be dependent
> on the other patches in the series. Is that something I can do?
I don't know how else to say this, every step along the way the tree
has to build. You arrange the patches however necessary to achieve
that goal.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists