[gentoo-kernel] Help needed with genpatches

[gentoo-kernel] Help needed with genpatches

[Daniel Drake]

I'm on holiday from 26th July to 11th August, the timing of which isn't 
great:

2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this 
will happen very soon (hint hint Greg, it's a day late! ;)).

There are bound to be a few bugs that need attention, the main concern 
is to fix things for the 2006.1 release and there isn't much time there. 
Apart from that we're OK, we need to make sure someone can do security 
fixes.

Any volunteers? :)

Daniel

-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] Help needed with genpatches

[Tim Yamin]

On Thu, Jul 20, 2006 at 07:19:49PM +0100, Daniel Drake wrote:
> I'm on holiday from 26th July to 11th August, the timing of which isn't 
> great:
> 
> 2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this 
> will happen very soon (hint hint Greg, it's a day late! ;)).
> 
> There are bound to be a few bugs that need attention, the main concern 
> is to fix things for the 2006.1 release and there isn't much time there. 
> Apart from that we're OK, we need to make sure someone can do security 
> fixes.
> 
> Any volunteers? :)

Sure, I can help out but you'll need to give me the magic tools and things
:)
-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] Help needed with genpatches

[Christian Heim]

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

On Thursday 20 July 2006 20:19, Daniel Drake wrote:
>I'm on holiday from 26th July to 11th August, the timing of which isn't
>great:
>
>2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this
>will happen very soon (hint hint Greg, it's a day late! ;)).
>
>There are bound to be a few bugs that need attention, the main concern
>is to fix things for the 2006.1 release and there isn't much time there.
>Apart from that we're OK, we need to make sure someone can do security
>fixes.
>
>Any volunteers? :)

I would, just as Tim, be glad to help you out for the time being.

Christian

-- 
Christian Heim <phreak@gentoo.org>
Gentoo Linux Developer
Your friendly kernel/vserver/openvz monkey

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-kernel] Help needed with genpatches

[Christian Heim]

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

On Thursday 20 July 2006 20:48, Tim Yamin wrote:
>On Thu, Jul 20, 2006 at 07:19:49PM +0100, Daniel Drake wrote:
>> I'm on holiday from 26th July to 11th August, the timing of which isn't
>> great:
>>
>> 2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this
>> will happen very soon (hint hint Greg, it's a day late! ;)).
>>
>> There are bound to be a few bugs that need attention, the main concern
>> is to fix things for the 2006.1 release and there isn't much time there.
>> Apart from that we're OK, we need to make sure someone can do security
>> fixes.
>>
>> Any volunteers? :)
>
>Sure, I can help out but you'll need to give me the magic tools and things
>
>:)

*hint* take a look at the linux-patches/genpatches-2.6-misc/scripts [1] dir ;)

[1]http://sources.gentoo.org/viewcvs.py/linux-patches/genpatches-2.6-misc/scripts/

-- 
Christian Heim <phreak@gentoo.org>
Gentoo Linux Developer
Your friendly kernel/vserver/openvz monkey

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-kernel] Help needed with genpatches

[Mike Doty]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Yamin wrote:
> On Thu, Jul 20, 2006 at 07:19:49PM +0100, Daniel Drake wrote:
>> I'm on holiday from 26th July to 11th August, the timing of which isn't 
>> great:
>>
>> 2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this 
>> will happen very soon (hint hint Greg, it's a day late! ;)).
>>
>> There are bound to be a few bugs that need attention, the main concern 
>> is to fix things for the 2006.1 release and there isn't much time there. 
>> Apart from that we're OK, we need to make sure someone can do security 
>> fixes.
>>
>> Any volunteers? :)
> 
> Sure, I can help out but you'll need to give me the magic tools and things
> :)
I'll certainly give Tim and co a hand

- --
=======================================================
Mike Doty                      kingtaco -at- gentoo.org
Gentoo/AMD64 Strategic Lead
Gentoo Developer Relations
Gentoo Recruitment Lead
Gentoo Infrastructure
GPG: 0094 7F06 913E 78D6 F1BB  06BA D0AD D125 A797 C7A7
=======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iQCVAwUBRL/TeoBrouQZ9K4FAQKk4QQAr62TwB3KRiBfdk3AZxXdvwIdsdYLaW3m
D0gir+hWxlnwAbqUTnTEPRAj5qPSVB9MdrCM9ZuHPmJdAPwa6nh8q+oxbOlCYCtg
xEJWHzdfaDjmBzAEB+e9pny7XlO65x+9ABAto/pUMXp2lEoyiDrtWn46s6zKGAdX
DjXhXeo4LSA=
=1Tu5
-----END PGP SIGNATURE-----
-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] Help needed with genpatches

[Greg KH]

On Thu, Jul 20, 2006 at 07:19:49PM +0100, Daniel Drake wrote:
> I'm on holiday from 26th July to 11th August, the timing of which isn't 
> great:
> 
> 2.6.17 will go stable as soon as we do a 2.6.17.7-based release - this 
> will happen very soon (hint hint Greg, it's a day late! ;)).

It's going to be a few more days late.  I'm at OLS, have yet to finish
writing my keynote I'm giving in a day or so, and rumor has it, the .7
patches I sent out have some "issues"...

So I don't know when 2.6.17 is going "stable" for us yet, but you might
want to hold off till .7 comes out.  Sometime early next week probably.

> There are bound to be a few bugs that need attention, the main concern 
> is to fix things for the 2006.1 release and there isn't much time there. 
> Apart from that we're OK, we need to make sure someone can do security 
> fixes.
> 
> Any volunteers? :)

I can poke at it after OSCON and help out.  SLES 10 work is pretty much
finished for me now (that sucked me away from Gentoo work, sorry).

Oh, also, some stuff that affected us came up at the kernel summit with
regards to how we should track our kernel bugs.  I'll write it up in a
bit...

thanks,

greg k-h
-- 
gentoo-kernel@gentoo.org mailing list

[gentoo-kernel] push kernel bugs upstream sooner and bootsplash/vesa-ng stuff

[Greg KH]

On Thu, Jul 20, 2006 at 07:37:32PM -0700, Greg KH wrote:
> Oh, also, some stuff that affected us came up at the kernel summit with
> regards to how we should track our kernel bugs.  I'll write it up in a
> bit...

So the main bit that happened, was an agreement to allow the
bugzilla.kernel.org database, hold distro kernel bugs.  The upstream
developers want to see the bugs earlier, and faster.  So I'd really
recommend throwing them there almost immediately if we can, unless it's
obvious the problem is in our stuff (bootsplash, vesa-ng, etc.).

The big issue is that the reporter would have to create their own
account there to get notified of changes, and mirroring the stuff back
into our bugzilla would get to be a big chore.  So I'd recommend just
starting out with a few of them, and see how it goes.

There should be a new field in the kernel.org bugzilla there soon that
shows that this is a gentoo specific bug (along with the other distros.)
If it doesn't happen in a week, poke me and I'll go poke the responsible
people for it.


Another off-hand remark that happened was a conversation about the
bootsplash and vesa-ng code.  People were wondering why the hell it
wasn't in mainline already!  The bootsplash stuff was remarked by the
whole group involved that it looked great, and was way better than the
old implementation.  Yeah, I know some RH people still don't like the
whole idea, as they use X for their splash stuff, but it shouldn't be
hard to keep that under control, as I think the code is pretty
self-contained with no real issues if you turn it off.

And the same for vesa-ng, although most present were not even aware of
it.

So, what's the hold up?  Why not get them upstream?  Would save us a bit
of merge issues for new kernel releases :)

thanks,

greg k-h
-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] Help needed with genpatches

[Daniel Drake]

Greg KH wrote:
> So I don't know when 2.6.17 is going "stable" for us yet, but you might
> want to hold off till .7 comes out.  Sometime early next week probably.

OK. We need 2.6.17 stable before then really, so I am just going to 
steal a few of the more important fixes for now.

Thanks for all the offers to help. I am going to get Christian to 
produce the next release so that he is all set up. The rest of you
really just need to help out in bugzilla, thats where the real work gets 
done.

Daniel
-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] push kernel bugs upstream sooner and bootsplash/vesa-ng stuff

[Daniel Drake]

Greg KH wrote:
> So the main bit that happened, was an agreement to allow the 
> bugzilla.kernel.org database, hold distro kernel bugs.  The upstream 
> developers want to see the bugs earlier, and faster.  So I'd really 
> recommend throwing them there almost immediately if we can, unless
> it's obvious the problem is in our stuff (bootsplash, vesa-ng, etc.).
> 
I really like this idea. I'm slightly worried that you'll end up with a
pile of other bugs that just waste time though (not from Gentoo, but
from other distros). About a month ago I tried to get a patch from
Mandrivas's kernel. It was 2.6.12 with loaaaads of patches, so many that 
they revealed a very obscure bug in diffstat when trying to create these 
statistics:

2257 files changed, 363439 insertions(+), 22957 deletions(-)

As well as those ~700 patches, they also include 38 tarballs of
out-of-tree modules (mostly drivers), which they then build into the
kernel RPM. So you might even get some bugs on things that aren't even
in the kernel tree in those cases...

But for Gentoo at least, I think both the Gentoo maintainers and the
upstream developers would find it really useful.

> The big issue is that the reporter would have to create their own 
> account there to get notified of changes, and mirroring the stuff
> back into our bugzilla would get to be a big chore.  So I'd recommend
> just starting out with a few of them, and see how it goes.

I agree that there is an issue with getting the reporter to sign up for
yet another bugzilla, but I don't think there would be any problem with
mirroring: I don't see why we'd need to mirror anything back, except
maybe the resolution of the bug. I need to give this more thought.

> Another off-hand remark that happened was a conversation about the 
> bootsplash and vesa-ng code.  People were wondering why the hell it 
> wasn't in mainline already!  The bootsplash stuff was remarked by the
>  whole group involved that it looked great, and was way better than
> the old implementation.  Yeah, I know some RH people still don't like
> the whole idea, as they use X for their splash stuff, but it
> shouldn't be hard to keep that under control, as I think the code is
> pretty self-contained with no real issues if you turn it off.
> 
> And the same for vesa-ng, although most present were not even aware
> of it.

I'd love to see these merged.

Michal can provide you with clearer answers but here is what I know:

fbsplash was submitted about a year ago. Some developers commented "do
it in userspace, you can do almost all of that there", and others gave
feedback on things which must be changed or fixed before it is to be
considered. I don't think Michal has had time to finish addressing those 
points -- when are you going to get SuSE to hire him? :)

I don't think fbsplash is too far away from possible kernel inclusion,
but vesafb-tng is. It is x86-only and is a big hack by design. Here's a
recent comment from Michal:

> Wrt the future of vesafb-tng -- it's unlikely any code can be moved
> to vesafb. The way to go (and this seems to be both my own opinion
> and the opinion of the fb developers) is to have the vm86 code
> separated into an userspace application (which will also make it
> possible for the driver to work on non-x86, since x86emu can be used
> in place of vm86). I'm going to work on this during the summer, but I
> wouldn't want to set any deadlines or promise completion dates just
> yet :)


So, did you show them the speakup patch? :)
*runs for the hills*

Daniel
-- 
gentoo-kernel@gentoo.org mailing list

Re: [gentoo-kernel] push kernel bugs upstream sooner and bootsplash/vesa-ng stuff

[Michal Januszewski]

[-- Attachment #1: Type: text/plain, Size: 2412 bytes --]

On Fri, Jul 21, 2006 at 08:46:58AM +0100, Daniel Drake wrote:

> Michal can provide you with clearer answers but here is what I know:
> 
> fbsplash was submitted about a year ago. Some developers commented "do
> it in userspace, you can do almost all of that there", and others gave
> feedback on things which must be changed or fixed before it is to be
> considered. I don't think Michal has had time to finish addressing those 
> points -- when are you going to get SuSE to hire him? :)

I'm sorry this reply is so terribly delayed, but I have been away at the
time this message was sent. What Daniel said above is true. I didn't
really have time to address or dispute all these issues (I'm not sure
all of them were fixable).

What's more, I don't think it is possible to get fbsplash merged at this
point. Currently, the predominant vision for a themed console, with
bell'n'whistles and stuff, is to do it completely in userspace (see
the rather lengthy 'OpenGL-based framebuffer concepts' discussion [lkml,
June 2006]). The idea is to do fbcon in userspace and keep only a very
simple console driver in the kernel (for things such as printing
oopses). Obviously, having the console completely in userspace makes
it possible to do virtually anything with it -- the possibilities are
by no means limited by just setting background images.

I have to say I like this idea of a userspace console and plan to work
on it after I'm finished with all the old stuff I'm stuck with right
now.
 
> I don't think fbsplash is too far away from possible kernel inclusion,
> but vesafb-tng is. It is x86-only and is a big hack by design. Here's a
> recent comment from Michal:
> 
> >Wrt the future of vesafb-tng -- it's unlikely any code can be moved
> >to vesafb. The way to go (and this seems to be both my own opinion
> >and the opinion of the fb developers) is to have the vm86 code
> >separated into an userspace application (which will also make it
> >possible for the driver to work on non-x86, since x86emu can be used
> >in place of vm86). I'm going to work on this during the summer, but I
> >wouldn't want to set any deadlines or promise completion dates just
> >yet :)

The quote says it all :)

Best regards.
-- 
Michal Januszewski                              JID: spock@im.gentoo.org
Gentoo Linux Developer                    http://people.gentoo.org/spock


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]