From: Daniel Drake <dsd@gentoo.org>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH-remove experimental depends from forcedeth
Date: Sun, 24 Apr 2005 21:30:04 +0100 [thread overview]
Message-ID: <426C01CC.7050602@gentoo.org> (raw)
In-Reply-To: <200503051106.11678.gene.heskett@verizon.net>
Gene Heskett wrote:
> I've not seen a forcedeth mention go by on this list for quite some
> time unless I made it. It has been quite bulletproof here so I don't
> feel the need for it to remain dependent on the experimental status in
> the main .config.
>
> Hence this patch to remove that requirement from the appropriate
> Kconfig.
I know of one issue that remains, which seems to have hit a few Gentoo users.
See
http://www.ussg.iu.edu/hypermail/linux/kernel/0502.0/0219.html
and
http://bugs.gentoo.org/90069
It's been reported to this mailing list, but I've also asked the affected
Gentoo users to file a bug at the kernel bugzilla.
Daniel
prev parent reply other threads:[~2005-04-24 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 16:06 PATCH-remove experimental depends from forcedeth Gene Heskett
2005-04-24 20:30 ` Daniel Drake [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=426C01CC.7050602@gentoo.org \
--to=dsd@gentoo.org \
--cc=gene.heskett@verizon.net \
--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