[request-sponsor] Request for sponsor for 6884004

Boris Ostrovsky wrote: Hello, I am going to be working on the following CR: 6884004 ahci driver calls ddi_dma_addr_bind_handle() without specifying permissions My SCA# is OS0248. Thanks. Boris Ostrovsky I'll be sponsoring this for Boris.

[request-sponsor] Request for sponsor for 6884004

Dan Mick wrote: Boris Ostrovsky wrote: Hello, I am going to be working on the following CR: 6884004 ahci driver calls ddi_dma_addr_bind_handle() without specifying permissions My SCA# is OS0248. Thanks. Boris Ostrovsky I'll be sponsoring this for Boris. sorry; I was expecting

[request-sponsor] Bug 6341292 cleanup of hsfs warning messages required

Joerg Schilling wrote: Bonnie Corwin Bonnie.Corwin at Sun.COM wrote: Thanks for your interest in this code. I've added this request to the table in the 'awaiting sponsor' category. While waiting for a sponsor, you can get started by reading the instructions about contributing code and

[request-sponsor] Remove 6566789

I've taken over 6566789 myself; please remove it from any sponsor lists.

[request-sponsor] contribution

ashish kataria wrote: Want to work on bug (number 10),*CrNumber =*6291460 http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6291460** *Synopsis=too much pseudo-spelling in solaris (oss-bite-size) for 1 month (approx.)* -- Ashish Kataria Student Apeejay College of Engineering

[request-sponsor] sponsor request for bug 6363303

John, if you've done the contributor agreement, I can certainly help you with this putback. Bonnie Corwin wrote: Hi John, I assume you mean 6363303. I'll add this to the table. You might want to go ahead and submit a contributor agreement. Then you'll be all set when someone picks

[request-sponsor] Sponsor Request for 4970570 fsdb_ufs :log_head prints extent list twice

I'll take this one, Shawn...and the next one as well Shawn Walker wrote: Greetings, I would like to request a sponsor to help me integrate my fix for bug 4970570, fsdb_ufs :log_head prints extent list twice. I have a text file giving a short summary here:

[request-sponsor] Sponsor Request for 5031435 fsdb dumps a core with :log_otodb command

I'll take this one too, Shawn, along with 4970570 fsdb_ufs :log_head prints extent list twice Shawn Walker wrote: Greetings, I would like to request a sponsor to help me integrate my fix for bug 5031435, fsdb dumps a core with :log_otodb command. I have a text file giving a short

[request-sponsor] 6424003 pkginfo -l can't handle long package names properly

Peter Tribble wrote: I would like a sponsor for 6424003. Suggested fix is in the bug report. (Note that the bug report is slightly inaccurate. It's broken on all platforms, but the output sometimes looks plausible.) I'll take this one.

[request-sponsor] 6312400 Ps/2 floppy is not enumerated when acpi is disabled for not supported

Dan Mick wrote: I don't have this saved in my mailbox, for some reason, but I'll sponsor it for Juergen. sorry, I see now that Dana has already taken it.

[request-sponsor] request sponsor for 6311025: build_reserved_irqlist ignores irq15 ...

J?rgen Keil wrote: Fix for this issue is included in the bug's workaround section: in usr/src/uts/i86pc/io/psm/psm_common.c, line 308, the condition for running the code in the loop must be changed from i MAX_ISA_IRQ to i = MAX_ISA_IRQ. This message posted from opensolaris.org

[request-sponsor] Re: 6183481 - pfiles could easily print file offset for files

That is, indeed, the fix that's already in the bug... Edward Wilson wrote: Off the top of my head I can't think of anything that changes state on a 0 offset relative seek, so, how about (in context diff format), *** pfiles.c.prev Sun Dec 11 23:02:37 2005 --- pfiles.cSun Dec 11

[request-sponsor] Round2: Sponsor Proposal

David Robinson wrote: Being a sponsor is not just about typing putback, but it is actually moderately heavyweight in that the sponsor is expected to build, test (maybe DIY test?), and validate the changes. Frankly, in many cases that may take more time than the actual code change. This is

[request-sponsor] updated request table

Question: Dan Mick had noted last month that 6323481 (Pci device enumeration for multifunction pci devices is incomplete) may be subsumed by an existing bug. This bug is still in the dispatched state in the database. How do I find out whether this bug really is being addressed by something

[request-sponsor] Requesting sponsor for 4997138 - pn_free() should free pn_bufsize bytes

Just to be clear, I'm working on this one. Jeremy Teo wrote: Hello, as mentioned in the subject above. Trivial patch to fix this is attached. Regards, Jeremy Suggested Fix: --- usr/src/uts/common/fs/pathname.c Tue Jun 14 15:45:20 2005 +++ usr/src/uts/common/fs/pathname.c Wed Jun

[request-sponsor] How to know whether a bug is being fixed by others?

How to know whether a bug is being fixed by others? As always, if there's a responsible engineer assigned, you can assume that person is working on the bug. Di-Li Victor Hu wrote: And I am Sun employee, do I need to request a sponsor to play with some oss-bit-size tagged bugs? No, but

[request-sponsor] [PATCH] 4763952 fstyp_ufs misreports cylinder group offsets

Shawn Walker wrote: [PATCH] for bug 4763952 fstyp_ufs misreports cylinder group offsets http://icculus.org/~eviltypeguy/4763952.patch contributor agreement # OS0004 I've got this one

[request-sponsor] request to add Intel D865PERL onboard LAN support

well, it's sorta a minor sponsor request. someone has to add the new ID and test it. I can take this one. Karyn Ritter wrote: I'm still working on the initial email about what processes you all should follow in responding to these messages. Expect to see something by tomorrow at the