From: Samuel Ortiz <sameo@linux.intel.com>
To: inux-kernel <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartmann <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>, Samuel Ortiz <sameo@linux.intel.com>
Subject: [PATCH 7/7 v2] firmware: FIRMWARE_NAME_MAX removal
Date: Wed, 27 May 2009 00:49:37 +0200 [thread overview]
Message-ID: <20090526225202.824460684@linux.intel.com> (raw)
In-Reply-To: 20090526224930.145059254@linux.intel.com
[-- Attachment #1: firmware-no_max.patch --]
[-- Type: text/plain, Size: 843 bytes --]
From: Samuel Ortiz <sameo@linux.intel.com>
As we're allocating the firmware name dynamically, we no longer need this
definition.
This patch must be applied only after the 5 previous patches from this pacth
set have been applied.
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
---
include/linux/firmware.h | 1 -
1 file changed, 1 deletion(-)
Index: iwm-2.6/include/linux/firmware.h
===================================================================
--- iwm-2.6.orig/include/linux/firmware.h 2009-05-26 17:44:30.000000000 +0200
+++ iwm-2.6/include/linux/firmware.h 2009-05-26 17:44:34.000000000 +0200
@@ -5,7 +5,6 @@
#include <linux/types.h>
#include <linux/compiler.h>
-#define FIRMWARE_NAME_MAX 30
#define FW_ACTION_NOHOTPLUG 0
#define FW_ACTION_HOTPLUG 1
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2009-05-26 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 22:49 [PATCH 0/7 v2] firmware: dynamic firmware id allocation Samuel Ortiz
2009-05-26 22:49 ` [PATCH 1/7 v2] firmware: allocate firmware id dynamically Samuel Ortiz
2009-05-26 22:49 ` [PATCH 2/7 v2] atm/ueagle-atm: prepare for FIRMWARE_NAME_MAX removal Samuel Ortiz
2009-05-26 22:49 ` [PATCH 3/7 v2] tuners/xc2028: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 4/7 v2] dvb/dvb-usb: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 5/7 v2] pcmcia/ds: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 6/7 v2] wireless/libertas: " Samuel Ortiz
2009-05-26 22:49 ` Samuel Ortiz [this message]
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=20090526225202.824460684@linux.intel.com \
--to=sameo@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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