[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1369921028.26799.4.camel@gandalf.local.home>
Date: Thu, 30 May 2013 09:37:08 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Borislav Petkov <bp@...en8.de>
Cc: "Ortiz, Lance E" <lance.oritz@...com>,
"Luck, Tony" <tony.luck@...el.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"lance_ortiz@...mail.com" <lance_ortiz@...mail.com>,
"jiang.liu@...wei.com" <jiang.liu@...wei.com>,
"mchehab@...hat.com" <mchehab@...hat.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] aerdrv: Move cper_print_aer() call out of interrupt
context
On Thu, 2013-05-30 at 09:28 +0200, Borislav Petkov wrote:
> On Thu, May 30, 2013 at 04:55:20AM +0000, Ortiz, Lance E wrote:
> > This TODO is a note for future clean-up and is not directly related to
> >the bug being fixed with this patch. Which lends to the argument of why
> >put the TODO in this patch? Opportunistic. I don’t think we want to
> >create a separate patch just for a TODO note.
>
> Sounds to me, this TODO item should be on your TODO list - not in kernel
> sources :-)
>
Also, that TODO sounds like there's output to userspace that can be
parsed by a userspace tool. If a tool expects the current format, it may
not be acceptable to change it later.
If the contents of this patch has nothing to do with the TODO, then
leave it out. It just confuses things.
-- Steve
--
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/
Powered by blists - more mailing lists