All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC Patches <openbmc-patches@stwcx.xyz>
Cc: openbmc@lists.ozlabs.org
Subject: Re: [PATCH phosphor-host-ipmid 1/3] ipmid: Use updated dbus HostIpmi interface
Date: Mon, 30 Nov 2015 09:17:32 -0600	[thread overview]
Message-ID: <20151130151732.GI19499@asimov.austin.ibm.com> (raw)
In-Reply-To: <1448436024-9396-2-git-send-email-openbmc-patches@stwcx.xyz>

[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]

Chris,

Why does this patch exist with whitespace only changes?  Did something
go wrong in a rebase you did?

On Wed, Nov 25, 2015 at 02:20:22AM -0500, OpenBMC Patches wrote:
> From: Jeremy Kerr <jk@ozlabs.org>
> 
> With the updated HostIpmi dbus interface, netfns are not packed with
> LUNs, and the CC is separate from the data.  This means we no longer
> have to define NETFN_* as arbitrarily shifted, and we have the added
> bonus of replying to messages where lun != 0.
> 
> We may want to separate the CC returned from the handlers in future too.
> 
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
> ---
>  ipmid-api.h | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/ipmid-api.h b/ipmid-api.h
> index 2d58961..f9c03dd 100644
> --- a/ipmid-api.h
> +++ b/ipmid-api.h
> @@ -63,16 +63,16 @@ extern "C" void ipmi_register_callback(ipmi_netfn_t, ipmi_cmd_t,
>  // Note: these are also shifted left to make room for the LUN.
>  enum ipmi_net_fns
>  {
> -    NETFUN_CHASSIS   =   0x00,
> -    NETFUN_BRIDGE    =   0x02,
> -    NETFUN_SENSOR    =   0x04,
> -    NETFUN_APP       =   0x06,
> -    NETFUN_FIRMWARE  =   0x08,
> -    NETFUN_STORAGE   =   0x0a,
> -    NETFUN_TRANSPORT =   0x0c,
> -    NETFUN_GRPEXT    =   0x2c,
> -    NETFUN_NONE      =   0x30,
> -    NETFUN_OEM       =   0x32
> +    NETFUN_CHASSIS  =   0x00,
> +    NETFUN_BRIDGE   =   0x02,
> +    NETFUN_SENSOR   =   0x04,
> +    NETFUN_APP      =   0x06,
> +    NETFUN_FIRMWARE =   0x08,
> +    NETFUN_STORAGE  =   0x0a,
> +    NETFUN_TRANPORT =   0x0c,
> +    NETFUN_GRPEXT   =   0x2c,
> +    NETFUN_NONE     =   0x30,
> +    NETFUN_OEM      =   0x32
>  };
>  
>  // IPMI commands for net functions. Since this is to be used both by the ipmi
> -- 
> 2.6.3
> 
> 
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-30 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  7:20 [PATCH phosphor-host-ipmid 0/3] simple cleanups OpenBMC Patches
2015-11-25  7:20 ` [PATCH phosphor-host-ipmid 1/3] ipmid: Use updated dbus HostIpmi interface OpenBMC Patches
2015-11-30 15:17   ` Patrick Williams [this message]
2015-11-25  7:20 ` [PATCH phosphor-host-ipmid 2/3] ipmid: Remove assumptions about host IPMI sender objects OpenBMC Patches
2015-11-25  7:20 ` [PATCH phosphor-host-ipmid 3/3] fixing build break in my master OpenBMC Patches

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=20151130151732.GI19499@asimov.austin.ibm.com \
    --to=patrick@stwcx.xyz \
    --cc=openbmc-patches@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.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.