From: David Miller <davem@davemloft.net>
To: aabdulla@nvidia.com
Cc: manfred@colorfullife.com, akpm@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] forcedeth: remove device id macros
Date: Thu, 04 Jun 2009 02:06:06 -0700 (PDT) [thread overview]
Message-ID: <20090604.020606.229964108.davem@davemloft.net> (raw)
In-Reply-To: <4A271DCD.3080903@nvidia.com>
From: Ayaz Abdulla <aabdulla@nvidia.com>
Date: Wed, 03 Jun 2009 21:05:17 -0400
> This patch removes the device id macros and instead uses the constants
> directly.
>
> The areas in which logic expressions where using the macros now
> instead use feature/workaround flags.
>
> No new functionality has been introduced in this patch, only clean up
> of flags and macros.
>
> Signed-off-by: Ayaz Abdulla <aabdulla@nvidia.com>
Applied to net-next-2.6
next prev parent reply other threads:[~2009-06-04 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 1:05 [PATCH 1/3] forcedeth: remove device id macros Ayaz Abdulla
2009-06-04 9:06 ` David Miller [this message]
2009-06-04 11:46 ` Michał Mirosław
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=20090604.020606.229964108.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=manfred@colorfullife.com \
--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).