[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140623092650.GE8847@lee--X1>
Date: Mon, 23 Jun 2014 10:26:50 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Doug Anderson <dianders@...omium.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: cros_ec_spi: set wakeup capability
> Lee (-others),
Re-CC'ing the list.
> On Wed, Jun 18, 2014 at 2:20 AM, Lee Jones <lee.jones@...aro.org> wrote:
> >> From: Prathyush K <prathyush.k@...sung.com>
> >>
> >> Set the device as wakeup capable and register the wakeup source.
> >>
> >> Note: Though it makes more sense to have the SPI framework do this,
> >> (either via device tree or by board_info)
> >> this change is as per an existing mail chain:
> >> https://lkml.org/lkml/2009/8/27/291
> >>
> >> Signed-off-by: Prathyush K <prathyush.k@...sung.com>
> >> Signed-off-by: Doug Anderson <dianders@...omium.org>
> >> ---
> >> Note that I don't have suspend/resume actually working upstream, but I
> >> see that /sys/bus/spi/drivers/cros-ec-spi/spi2.0/power/wakeup exists
> >> with this patch and doesn't exist without it.
> >
> > Very well. Applied, thanks.
>
> Thanks for applying! ...did this go in some non-standard branch? I
> see another of my patches got committed to your "for-mfd-next" tree on
> the 19th but I don't see this one...
Patience Grasshopper. When I say that it's applied, it means that I
have done so locally only. After I've collected a few local patches
I'll usually then fix them all with with my SoB and push them out to
the public MFD tree.
BTW, it's always best to leave the ML in as CC, so others can see the
answer to these types of questions. It may save a few emails a year,
but every little helps. :)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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