From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] ibm_newemac: Introduce mal_has_feature
Date: Fri, 05 Sep 2008 13:19:23 +1000 [thread overview]
Message-ID: <1220584763.4879.97.camel@pasglop> (raw)
In-Reply-To: <20080904150205.GC2479@yoda.jdub.homelinux.org>
On Thu, 2008-09-04 at 11:02 -0400, Josh Boyer wrote:
> There are some PowerPC SoCs that do odd things with the MAL handling. In
> order to accommodate them, we need to introduce a feature mechanism that is
> similar to the existing emac_has_feature function.
>
> This adds a feature variable to the mal_instance structure, and adds a
> mal_has_feature function with some feature definitions. These are guarded
> by Kconfig options that are selected by the affected platforms.
>
> Signed-of-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
You also add an actual feature (CLR_ICINSTAT). You should document that
or move it to a separate patch.
> +/* Features of various MAL implementations */
> +
> +/* Dummy feature bit so the enum works properly */
> +#define MAL_FTR_DUMMY 0x00000001
Nah. Just stick an | 0 in the enum to make it happy.
Cheers,
Ben.
next prev parent reply other threads:[~2008-09-05 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1220540078.git.jwboyer@linux.vnet.ibm.com>
2008-09-04 15:01 ` [PATCH 1/3] ibm_newemac: Allow the "no flow control" EMAC feature to work Josh Boyer
2008-09-04 15:02 ` [PATCH 2/3] ibm_newemac: Introduce mal_has_feature Josh Boyer
2008-09-05 3:19 ` Benjamin Herrenschmidt [this message]
2008-09-05 3:37 ` Josh Boyer
2008-09-04 15:02 ` [PATCH 3/3] ibm_newemac: MAL support for PowerPC 405EZ Josh Boyer
2008-09-05 2:10 ` Simon Horman
2008-09-05 3:41 ` Josh Boyer
2008-09-05 9:34 ` Benjamin Herrenschmidt
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=1220584763.4879.97.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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 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).