From: Timur Tabi <timur@freescale.com>
To: Greg KH <gregkh@suse.de>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>,
Markus Rechberger <markus.rechberger@amd.com>
Subject: Re: Fix Firmware class name collision
Date: Fri, 14 Dec 2007 16:46:21 -0600 [thread overview]
Message-ID: <476307BD.5010809@freescale.com> (raw)
In-Reply-To: <20071214224051.GA29580@suse.de>
Greg KH wrote:
> In the near future (2.6.26) there will not be a limit on the size of the
> file name, so we should not have this problem anymore.
In that case, I won't worry about it. I would have preferred 2.6.25, since I
have code going into 2.6.25 that is affected by the current limit.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2007-12-14 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 23:45 Fix Firmware class name collision Timur Tabi
2007-12-04 23:52 ` Scott Wood
2007-12-05 1:28 ` Timur Tabi
2007-12-14 22:40 ` Greg KH
2007-12-14 22:46 ` Timur Tabi [this message]
2007-12-15 6:14 ` Benjamin Herrenschmidt
2007-12-15 6:39 ` Greg KH
2007-12-15 15:46 ` Kay Sievers
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=476307BD.5010809@freescale.com \
--to=timur@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=gregkh@suse.de \
--cc=markus.rechberger@amd.com \
/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).