ACPI bug tracking

ACPI bug tracking

[Grover, Andrew]

Hi all,

I don't know if it's been obvious or not, but I haven't had time for
keeping up with ACPI lately. Part of this is because the list volume is
picking up (a good thing) and part is because other projects are
demanding my time.

I just wanted to ask that people make greater use of
bugzilla.kernel.org, and work with the other Linux ACPI Intel people
(Luming Yu, Len Brown, and Bob Moore) so that bug reports or patches
don't get dropped. Issues reported in bugzilla are much less likely to
be overlooked.

Regards -- Andy

-----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

RE: ACPI bug tracking

[Yu, Luming]

My email account is:  luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org

Thanks,
Luming

-----Original Message-----
From: Grover, Andrew 
Sent: 2003?5?8? 0:29
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [ACPI] ACPI bug tracking


Hi all,

I don't know if it's been obvious or not, but I haven't had time for
keeping up with ACPI lately. Part of this is because the list volume is
picking up (a good thing) and part is because other projects are
demanding my time.

I just wanted to ask that people make greater use of
bugzilla.kernel.org, and work with the other Linux ACPI Intel people
(Luming Yu, Len Brown, and Bob Moore) so that bug reports or patches
don't get dropped. Issues reported in bugzilla are much less likely to
be overlooked.

Regards -- Andy

-----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
Acpi-devel mailing list
Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/acpi-devel


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: ACPI bug tracking

[Markus Gaugusch]

On May 7, Grover, Andrew <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> I just wanted to ask that people make greater use of
> bugzilla.kernel.org
This is only for 2.5 series now, what about 2.4? Most people here use 2.4,
I think and it's not good to report bugs for 2.4 into the 2.5 bugzilla, I
guess.
Also, which tree of 2.5 should we use? The Linus-tree?

I would particulary like to get my dsdt-initrd patch into acpi :)
Can I just submit my patch and hope that someone will pick it up?

thanks,
Markus
-- 
__________________    /"\
Markus Gaugusch       \ /    ASCII Ribbon Campaign
markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org     X     Against HTML Mail
                      / \


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: ACPI bug tracking

[Gunter Ohrner]

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

Am Donnerstag, 8. Mai 2003 13:36 schrieb Markus Gaugusch:
> I would particulary like to get my dsdt-initrd patch into acpi :)
> Can I just submit my patch and hope that someone will pick it up?

Doesn't the Kernel Bugzilla support wishlist entries? Add one and append the 
patch, this way at least it can't get lost in some mailing list archive. 
Andthis would be a pitty as your patch is really use- and helpful!

Greetings,

  Gunter

- -- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+                   PGP-verschlüsselte Mails bevorzugt!                 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
"Why's it called Ming?" said the Archchancellor, on cue. The Bursar 
tapped the pot. It went *ming*.        -- (Terry Pratchett, Moving 
Pictures)
+-+-+-+-+-+-+-+-+-+-+-+-+ http://www.lspace.org +-+-+-+-+-+-+-+-+-+-+-+-+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ulA80ORHvREo8l8RAm6zAKCL6S7qHM8ILnVHD7TI9IEfFMzQXgCePKxz
gbQa+WhUhN6yUpCUgZP+YQg=
=kNX9
-----END PGP SIGNATURE-----



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

RE: ACPI bug tracking

[Brown, Len]

Filing ACPI issues at http://bugzilla.kernel.org/ is preferred for either
the 2.4 or 2.5 tree.  Splitting the issue lists between what are very
similar versions of the ACPI code would just cause duplication and
confusion.  Be sure to select component=ACPI, and clearly mark the
kernel+patch version.

Sightings with un-adulterated distributor's pre-releases should still be
filed directly where the distributor says, e.g. http://bugzilla.redhat.com/
http://bugzilla.suse.de/ etc.  They don't generally seem to have a special
component for ACPI, but hopefully the description will direct the issue the
right way.

Please do not use the sourceforge bug tracker
(http://sourceforge.net/tracker/?group_id=36832&atid=425171) those will be
ignored.

> this way at least it can't get lost in some mailing list archive. 

Yep, that's the idea.

Cheers,
-Len


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: ACPI bug tracking

[Randy.Dunlap]

On Thu, 8 May 2003 07:15:07 -0700 "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

| Filing ACPI issues at http://bugzilla.kernel.org/ is preferred for either
| the 2.4 or 2.5 tree.  Splitting the issue lists between what are very
| similar versions of the ACPI code would just cause duplication and
| confusion.  Be sure to select component=ACPI, and clearly mark the
| kernel+patch version.

It may be preferred, but that bugzilla is specifically set up for 2.5
bug tracking.  Unless and until that is changed, 2.4 bugs should be
filed at sf.net/projects/acpi or with Linux distros.

| Sightings with un-adulterated distributor's pre-releases should still be
| filed directly where the distributor says, e.g. http://bugzilla.redhat.com/
| http://bugzilla.suse.de/ etc.  They don't generally seem to have a special
| component for ACPI, but hopefully the description will direct the issue the
| right way.
| 
| Please do not use the sourceforge bug tracker
| (http://sourceforge.net/tracker/?group_id=36832&atid=425171) those will be
| ignored.

Too bad.  Yes, I know that it's a pain to have to look in multiple places.

| > this way at least it can't get lost in some mailing list archive. 
| 
| Yep, that's the idea.

--
~Randy


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com