From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arun Easi <arun.easi@cavium.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
David Miller <davem@davemloft.net>,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: qed, qedi patchset submission
Date: Mon, 14 Nov 2016 18:47:27 -0500 [thread overview]
Message-ID: <yq11sydfwts.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1611141256340.28058@mvluser05.qlc.com> (Arun Easi's message of "Mon, 14 Nov 2016 13:53:50 -0800")
>>>>> "Arun" == Arun Easi <arun.easi@cavium.com> writes:
Arun,
Arun> Do you have any preference or thoughts on how the "qed" patches be
Arun> approached? Just as a reference, our rdma driver "qedr" went
Arun> through something similar[1], and eventually "qed" patches were
Arun> taken by David in the net tree and "qedr", in the rdma tree
Arun> (obviously) by Doug L.
DaveM can queue the whole series or I can hold the SCSI pieces for
rc1. Either way works for me.
However, I would like to do a review of the driver first. I will try to
get it done this week.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arun Easi <arun.easi@cavium.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
David Miller <davem@davemloft.net>, <linux-scsi@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: qed, qedi patchset submission
Date: Mon, 14 Nov 2016 18:47:27 -0500 [thread overview]
Message-ID: <yq11sydfwts.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1611141256340.28058@mvluser05.qlc.com> (Arun Easi's message of "Mon, 14 Nov 2016 13:53:50 -0800")
>>>>> "Arun" == Arun Easi <arun.easi@cavium.com> writes:
Arun,
Arun> Do you have any preference or thoughts on how the "qed" patches be
Arun> approached? Just as a reference, our rdma driver "qedr" went
Arun> through something similar[1], and eventually "qed" patches were
Arun> taken by David in the net tree and "qedr", in the rdma tree
Arun> (obviously) by Doug L.
DaveM can queue the whole series or I can hold the SCSI pieces for
rc1. Either way works for me.
However, I would like to do a review of the driver first. I will try to
get it done this week.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-11-14 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 21:53 qed, qedi patchset submission Arun Easi
2016-11-14 21:53 ` Arun Easi
2016-11-14 23:47 ` Martin K. Petersen [this message]
2016-11-14 23:47 ` Martin K. Petersen
2016-11-29 23:11 ` Arun Easi
2016-11-29 23:11 ` Arun Easi
2016-11-30 16:45 ` Martin K. Petersen
2016-11-30 16:45 ` Martin K. Petersen
2016-11-30 17:15 ` Arun Easi
2016-11-30 17:15 ` Arun Easi
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=yq11sydfwts.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=arun.easi@cavium.com \
--cc=davem@davemloft.net \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.