* Re: Question about mv_print_info in sata_mv.c in sata_mv.c [not found] <5498E9E4.4040308@gmail.com> @ 2014-12-26 20:55 ` Rob Herring [not found] ` <549DCDC3.3040207@gmail.com> 0 siblings, 1 reply; 2+ messages in thread From: Rob Herring @ 2014-12-26 20:55 UTC (permalink / raw) To: nick Cc: tj@kernel.org >> Tejun Heo, Grant Likely, Rob Herring, linux-ide, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org On Mon, Dec 22, 2014 at 10:04 PM, nick <xerofoify@gmail.com> wrote: > Greetings Tejuin,Grant and Rob, > Hope you are having a good holidays. I am wondering if there is > anything we need to add to this function as stated in a fix me above it.I am pretty certain > there isn't but as the maintainers, I am double checking first with you:). Please let me > known if you think of something. Grant and I are not actually maintainers of this driver. get_maintainer.pl is somewhat wrong here because it matches on regex that is present in about every driver that is DT enabled. I've sent a patch now to change that. It would help also if you paste in the actually code you are referring to. Rob > Regards and Have a Great Holidays :), > Nick ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <549DCDC3.3040207@gmail.com>]
* Re: Question about mv_print_info in sata_mv.c in sata_mv.c [not found] ` <549DCDC3.3040207@gmail.com> @ 2014-12-26 21:11 ` tj@kernel.org >> Tejun Heo 0 siblings, 0 replies; 2+ messages in thread From: tj@kernel.org >> Tejun Heo @ 2014-12-26 21:11 UTC (permalink / raw) To: nick Cc: Rob Herring, Grant Likely, Rob Herring, linux-ide, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Hello, Nick. On Fri, Dec 26, 2014 at 04:06:11PM -0500, nick wrote: > I am assuming after reading this function's code, that this function is completed and no longer > needs a fix me comment above it to be completed. I do appreciate that you're studying the FIXME comments but at this point I'm not sure whether blindly chasing them and asking people whether they're still necessary is a productive thing to do. If they're actively misleading, sure, let's remove them, but FIXME in a sata_mv function which prints some controller identification information just doesn't matter. If you can assert that the comment is no longer necessary and misleading, please submit a patch with backing rationale; otherwise, obsessing with each instance of FIXME comment doesn't seem to be a particularly productive way of participating in kernel development. Thanks. -- tejun ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-12-26 21:11 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <5498E9E4.4040308@gmail.com> 2014-12-26 20:55 ` Question about mv_print_info in sata_mv.c in sata_mv.c Rob Herring [not found] ` <549DCDC3.3040207@gmail.com> 2014-12-26 21:11 ` tj@kernel.org >> Tejun Heo
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).