public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: "amatus@ocgnet.org" <amatus@ocgnet.org>
Cc: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IPMI: Support registering for a command per-channel
Date: Mon, 26 Jun 2006 09:37:36 -0500	[thread overview]
Message-ID: <449FF130.3010601@acm.org> (raw)
In-Reply-To: <20060623150705.GA14245@login.ocgnet.org>

amatus@ocgnet.org wrote:
> From: David Barksdale <amatus@ocgnet.org>
>
> This patch adds the ability to register for a command per-channel.
>
> If your BMC supports multiple channels, incoming messages can be
> differentiated by the channel on which they arrived. In this case it's
> useful to have the ability to register to receive commands on a
> specific channel instead the current behaviour of all channels.
>
>   
Sorry for the long delay on this.  I like the patch in general, there
are a few things I'd like to fix in it, though:

* Instead of naming the IOCTLs xxx_CMD2, could you name
  them xxx_CMD_CHANNEL, or something that conveys a
  little more meaning?

* The command unregister function needs to use a different
  matching function now that you have to allow non-exact
  matches for the channels.  You still need an exact match
  for unregistering.

* Someone mentioned using a bitmask for the channels
  you are registering.  I think that's a good idea.  IPMI
  only allows 16 channels max, so an unsigned int should
  be plenty.  Add a define for all channels and for setting
  a specific channel.

Thanks,

-Corey

  reply	other threads:[~2006-06-26 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 15:07 [PATCH] IPMI: Support registering for a command per-channel amatus
2006-06-26 14:37 ` Corey Minyard [this message]
2006-06-28 19:28   ` amatus
2006-06-29  1:06     ` Corey Minyard
2006-06-29 14:20       ` amatus

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=449FF130.3010601@acm.org \
    --to=minyard@acm.org \
    --cc=amatus@ocgnet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    /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