All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Justin.Lee1@Dell.com>
To: <joel@jms.id.au>
Cc: <amithash@fb.com>, <vijaykhemka@fb.com>, <sam@mendozajonas.com>,
	<linux-aspeed@lists.ozlabs.org>, <openbmc@lists.ozlabs.org>,
	<sdasari@fb.com>, <netdev@vger.kernel.org>, <christian@cmd.nu>
Subject: RE: [PATCH] net/ncsi: Add NCSI OEM command for FB Tiogapass
Date: Thu, 27 Sep 2018 17:46:32 +0000	[thread overview]
Message-ID: <9553a4168a7e4134a3d6d7e2572bace0@AUSX13MPS306.AMER.DELL.COM> (raw)
In-Reply-To: <CACPK8XfuXa19dGRqL+Ycdgh1LKmoQNuqGvtrrOgeNyvTZR01kQ@mail.gmail.com>


> Thanks for the overview. We look forward to your patches; please
> include the same cc list as this series.

> I think it makes sense to have some OEM NCSI handing purely in the
> kenrel. This would allow eg. the MAC address of an interface to be
> correct at boot, without requiring userspace to come up first.

> I have also heard stories of temperature sensors over NCSI. Those
> would make sense to be hwmon drivers, which again would mean handling
> them in the kernel.

> Justin, Vijay, can you please list the known NCSI OEM
> commands/extensions that we plan on implementing?

In our implementation, All OEM commands are transparent to Kernel.
We don't plan to add any specific handler in the Kernel. 

Thanks,
Justin

  reply	other threads:[~2018-09-28  0:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  0:08 [PATCH] net/ncsi: Add NCSI OEM command for FB Tiogapass Vijay Khemka
2018-09-25  0:15 ` Vijay Khemka
2018-09-25  0:30 ` Joel Stanley
2018-09-25 18:16   ` Vijay Khemka
2018-09-26  4:33     ` Samuel Mendoza-Jonas
2018-09-26  4:33       ` Samuel Mendoza-Jonas
2018-09-26 17:07       ` Vijay Khemka
2018-09-26 18:07         ` Amithash Prasad
2018-09-26 20:39           ` Justin.Lee1
2018-09-27  3:20             ` Joel Stanley
2018-09-27  3:20               ` Joel Stanley
2018-09-27 17:46               ` Justin.Lee1 [this message]
2018-09-27  3:43 ` Samuel Mendoza-Jonas
2018-09-27  3:54   ` Samuel Mendoza-Jonas
2018-09-28 22:26   ` Vijay Khemka

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=9553a4168a7e4134a3d6d7e2572bace0@AUSX13MPS306.AMER.DELL.COM \
    --to=justin.lee1@dell.com \
    --cc=amithash@fb.com \
    --cc=christian@cmd.nu \
    --cc=joel@jms.id.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sam@mendozajonas.com \
    --cc=sdasari@fb.com \
    --cc=vijaykhemka@fb.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 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.