linux-kernel - Re: [PATCH] Removes FIXME message in usb.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPDOMVgZGWm=A89DdXiTmt+1qKNKxc+UpbupqCW52_+abfWAYw@mail.gmail.com>
Date:	Wed, 9 Jul 2014 13:28:32 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	balbi@...com, Tony Lindgren <tony@...mide.com>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-usb@...r.kernel.org, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Removes FIXME message in usb.c

Greg KH wrote on July 9th at 1:19 P.M.
Ok, this has been fun to watch on lkml for a while now, but really,
please, just stop doing this.  Randomly searching the kernel source for
FIXME lines and just commenting them out, isn't ok.  Almost always,
those lines are there because the original developer really doesn't know
how else to resolve the issue.

So, if the domain-specific-author doesn't have an idea of what to do,
how does someone who is brand-new to the code know better?

If you are looking for a task to do in the kernel, try
drivers/staging/*/TODO for a list.  Or look at the kernel janitor's list
on kernelnewbies.org.  Or try running the kernel and finding something
that is broken for you and fixing that.  Any of those would be better
than randomly deleting FIXME lines.  By doing that, you are just wasting
maintainer's time.  Which is the resource we have the least of at the
moment.

thanks,

greg k-h

Greg ,

I sent in another patch which enables omap_cfg_reg(USB2_SPEED) as
stated in the fix me.
The maintainers of this file stated to me this was dangerous due to
the wires perhaps being
shared with other parts of the board and we should depend on the boot
loader to set this.
The maintainers decided to remove this fix me not me based on their
better understanding
of this file.

Cheers Nick

On Wed, Jul 9, 2014 at 1:19 PM, Greg KH <greg@...ah.com> wrote:
> Ok, this has been fun to watch on lkml for a while now, but really,
> please, just stop doing this.  Randomly searching the kernel source for
> FIXME lines and just commenting them out, isn't ok.  Almost always,
> those lines are there because the original developer really doesn't know
> how else to resolve the issue.
>
> So, if the domain-specific-author doesn't have an idea of what to do,
> how does someone who is brand-new to the code know better?
>
> If you are looking for a task to do in the kernel, try
> drivers/staging/*/TODO for a list.  Or look at the kernel janitor's list
> on kernelnewbies.org.  Or try running the kernel and finding something
> that is broken for you and fixing that.  Any of those would be better
> than randomly deleting FIXME lines.  By doing that, you are just wasting
> maintainer's time.  Which is the resource we have the least of at the
> moment.
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/