From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 0/3] qede: Bug fixes
Date: Tue, 19 Apr 2016 20:21:26 -0400 (EDT)
Message-ID: <20160419.202126.734822407546551092.davem@davemloft.net>
References: <1460999167-3746-1-git-send-email-manish.chopra@qlogic.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org, Ariel.Elior@qlogic.com,
	Yuval.Mintz@qlogic.com
To: manish.chopra@qlogic.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([149.20.54.216]:38759 "EHLO
	shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752806AbcDTAV2 (ORCPT
	<rfc822;netdev@vger.kernel.org>); Tue, 19 Apr 2016 20:21:28 -0400
In-Reply-To: <1460999167-3746-1-git-send-email-manish.chopra@qlogic.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Manish Chopra <manish.chopra@qlogic.com>
Date: Mon, 18 Apr 2016 13:06:04 -0400

> Please note that I have intentionally targeted this for "net-next"
> to avoid merge conflicts when net-next changes gets merged to net
> 
> Please consider applying this series to "net-next"

I do not understand what you are saying here.

If these bugs exist in 'net' you must target these bug fixes
there.

If there will be merge conflicts after this when I merge net
into net-next, that's exactly what is supposed to happen and
is what I'm supposed to work on to resolve.  That's my job.