[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131024191557.GD3512@pengutronix.de>
Date: Thu, 24 Oct 2013 21:15:57 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Joe Perches <joe@...ches.com>
Cc: Kukjin Kim <kgene.kim@...sung.com>,
Ferruh Yigit <fery@...ress.com>,
Wan ZongShun <mcuos.com@...il.com>,
Andrey Moiseev <o2g.org.ru@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-kernel@...r.kernel.org, Josh Wu <josh.wu@...el.com>,
linux-samsung-soc@...r.kernel.org,
Henrik Rydberg <rydberg@...omail.se>,
Ben Dooks <ben-linux@...ff.org>, linux-input@...r.kernel.org,
Pau Oliva Fora <pof@...ack.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 4/8] input: Remove OOM message after input_allocate_device
On Thu, Oct 24, 2013 at 11:48:48AM -0700, Joe Perches wrote:
> On Thu, 2013-10-24 at 20:46 +0200, Uwe Kleine-König wrote:
> > On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
> []
> > > Any k.alloc without __GFP_NOWARN does a generic OOM message
> > > and a dump_stack() so there could already be 2 messages anyway.
> > Then mention that in the commit log if you still want this patch?!
>
> How do you think this commit message should be changed:
>
> Emitting an OOM message isn't necessary after input_allocate_device
> as there's a generic OOM and a dump_stack already done.
after input_allocate_device and/or k.alloc ...
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
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