public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brandon Hale <tseng@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Patches and the 2.4->2.6 move
Date: Mon, 20 Oct 2003 03:20:34 +0000	[thread overview]
Message-ID: <20031020032034.GA29403@emu.gentoo.org> (raw)
In-Reply-To: <1066617251.991.5.camel@sfa237013.richmond.edu>

> I have a patch that fixes SSE problems on 2.4 kernels. However, on 2.6
> kernels it breaks OpenGL (applications segfault).
>
> Currently I'm applying this patch if /usr/src/linux is linked to a 2.4
> kernel at compile-time.
>
> This means that if a user emerges xfree when linked to a 2.4 kernel,
> that user will need to remerge xfree after moving to 2.6 kernels. This
> takes about 40 minutes on a ~2GHz x86. However, if this patch is not
> applied, the bug will continue to exist for all Gentoo users on 2.4
> kernels.

It appears that the larger part of our user base is running a 2.4 series kernel,
and will be for quite some time. Considering this, and our position that
testing kernels are not offically supported, I think we should give priority to
fixing bugs that affect the most users.

> My request to you is:
> 1) Is this acceptable?

I find this acceptable under the condition that it is properly documented in
both postinst and ChangeLog.

> 2) If not, what is a better solution? Dropping the patch entirely? Note
> that I don't know Mesa/programming well enough to write a patch
> compatible for both 2.4 and 2.6 kernels.

The one caveat I can think of is GRP. Will we distribute a package for both
kernels? How does portage choose the right one?

> Thanks,
> Donnie

--tseng

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-10-20  3:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20  2:34 [gentoo-dev] Patches and the 2.4->2.6 move Donnie Berkholz
2003-10-20  3:05 ` Luke-Jr
2003-10-20  3:18   ` Donnie Berkholz
2003-10-20  3:22   ` Donnie Berkholz
2003-10-20  4:04     ` Luke-Jr
2003-10-20  4:30       ` Donnie Berkholz
2003-10-20  3:20 ` Brandon Hale [this message]
2003-10-20  3:25   ` Donnie Berkholz
2003-10-20  4:32     ` Luke-Jr
2003-10-20  4:16   ` Luke-Jr
2003-10-20  3:38     ` Jason Stubbs
2003-10-20  4:25     ` Jon Portnoy
2003-10-20  4:33 ` Kumba
2003-10-20  4:59   ` Donnie Berkholz
2003-10-19 23:48     ` C. Brewer
2003-10-20  7:13       ` Luke-Jr
2003-10-20  0:30         ` C. Brewer
2003-10-20  5:15     ` Luke-Jr
2003-10-20  5:23       ` Donnie Berkholz
2003-10-20 13:47 ` Alexander Gretencord

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=20031020032034.GA29403@emu.gentoo.org \
    --to=tseng@gentoo.org \
    --cc=gentoo-dev@gentoo.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