From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, dick.kennedy@broadcom.com,
james.smart@broadcom.com
Subject: Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64
Date: Wed, 22 Jun 2016 09:51:56 -0300 [thread overview]
Message-ID: <576A89EC.2010003@linux.vnet.ibm.com> (raw)
In-Reply-To: <yq1fus62cji.fsf@sermon.lab.mkp.net>
Hi Martin,
On 06/21/2016 11:16 PM, Martin K. Petersen wrote:
> Distros are free to carry a patch such as yours. That puts the burden on
> them and not on upstream which is going in a different direction as
> outlined by Christoph.
> This is ultimately Broadcom's decision. It is their driver.
Right, I understand. I submitted the patch in case they see value in
having it upstream, as some distros discuss/ask about what's the status
(or differences to) upstream.
In some cases, a rationale like this one being documented on a mailing
list is sufficient, provided the patch hasn't received other technical
problems, for example.
Thanks for the review/comments (Christoph too),
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2016-06-22 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464813809-22066-1-git-send-email-mauricfo@linux.vnet.ibm.com>
2016-06-01 20:43 ` [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64 Mauricio Faria de Oliveira
2016-06-21 14:29 ` Christoph Hellwig
2016-06-21 17:42 ` Mauricio Faria de Oliveira
2016-06-22 2:16 ` Martin K. Petersen
2016-06-22 12:51 ` Mauricio Faria de Oliveira [this message]
2016-06-01 20:43 ` [PATCH 2/2] lpfc: add option for lpfc_fcp_io_sched (LPFC_FCP_SCHED_BY_CPU_CORE) Mauricio Faria de Oliveira
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=576A89EC.2010003@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=dick.kennedy@broadcom.com \
--cc=hch@infradead.org \
--cc=james.smart@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).