On 05/22/2014 06:55 AM, Jingoo Han wrote:
On Monday, May 19, 2014 7:48 PM, Daniel Lezcano wrote:
On 04/29/2014 10:26 AM, Jingoo Han wrote:
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Are you sure the MM subsys display a message
On Thu, May 22, 2014 at 01:55:20PM +0900, Jingoo Han wrote:
> On Monday, May 19, 2014 7:48 PM, Daniel Lezcano wrote:
> > On 04/29/2014 10:26 AM, Jingoo Han wrote:
> > > The site-specific OOM messages are unnecessary, because they
> > > duplicate the MM subsystem generic OOM message.
> >
> > Are yo
On Monday, May 19, 2014 7:48 PM, Daniel Lezcano wrote:
> On 04/29/2014 10:26 AM, Jingoo Han wrote:
> > The site-specific OOM messages are unnecessary, because they
> > duplicate the MM subsystem generic OOM message.
>
> Are you sure the MM subsys display a message when an allocation fails ?
>
> T
On 04/29/2014 10:26 AM, Jingoo Han wrote:
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Are you sure the MM subsys display a message when an allocation fails ?
There are multiple reasons an allocation can fail.
Signed-off-by: Jin
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/clocksource/em_sti.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/em_sti.c b/drivers/clocksource/em_
5 matches
Mail list logo