Let me send both patches.
On 4/30/19, 11:45 PM, "Greg Kroah-Hartman" wrote:
On Wed, May 01, 2019 at 05:55:07AM +, Joel Stanley wrote:
> On Fri, 18 Jan 2019 at 20:12, Vijay Khemka wrote:
> >
> > Hi Andrew,
> > Thanks for this review, I will have a follow up patch for thi
On Wed, May 01, 2019 at 05:55:07AM +, Joel Stanley wrote:
> On Fri, 18 Jan 2019 at 20:12, Vijay Khemka wrote:
> >
> > Hi Andrew,
> > Thanks for this review, I will have a follow up patch for this return
> > values.
>
> Did you send a follow up patch to fix the return values?
>
> Greg, is th
On Fri, 18 Jan 2019 at 20:12, Vijay Khemka wrote:
>
> Hi Andrew,
> Thanks for this review, I will have a follow up patch for this return values.
Did you send a follow up patch to fix the return values?
Greg, is there any reason why you did not merge this one? 5.2 will
have device trees that depe
Hi Joel,
Can you please apply this below patch to kernel 5.0.
Regards
-Vijay
On 3/18/19, 12:46 PM, "openbmc on behalf of Vijay Khemka"
wrote:
Hi Joel,
Can you please apply this patch as "
Documentation/devicetree/bindings/mfd/aspeed-lpc.txt" has already been applied
Regards
Hi Joel,
Can you please apply this patch as "
Documentation/devicetree/bindings/mfd/aspeed-lpc.txt" has already been applied
Regards
-Vijay
On 3/5/19, 4:15 PM, "Linux-aspeed on behalf of Vijay Khemka"
wrote:
Joel,
Did this patch apply upstream. Somehow I can't find this patch in linu
Joel,
Did this patch apply upstream. Somehow I can't find this patch in linux or
linux-next or our obmc dev4.19.
Regards
-Vijay
On 1/17/19, 10:53 AM, "Linux-aspeed on behalf of Vijay Khemka"
wrote:
On 1/16/19, 10:17 PM, "Joel Stanley" wrote:
On Thu, 17 Jan 2019 at
Hi Andrew,
Thanks for this review, I will have a follow up patch for this return values.
Regards
-Vijay
On 1/17/19, 8:58 PM, "Andrew Jeffery" wrote:
Hi Vijay,
Thanks for doing the work to fix the driver. Some minor queries/points
below.
On Thu, 17 Jan 2019, at 08:31,
Hi Vijay,
Thanks for doing the work to fix the driver. Some minor queries/points
below.
On Thu, 17 Jan 2019, at 08:31, Vijay Khemka wrote:
> Makiing memory-region and flash as optional parameter in device
> tree if user needs to use these parameter through ioctl then
> need to define in devicetre
On 1/16/19, 10:17 PM, "Joel Stanley" wrote:
On Thu, 17 Jan 2019 at 09:02, Vijay Khemka wrote:
>
> Makiing memory-region and flash as optional parameter in device
> tree if user needs to use these parameter through ioctl then
> need to define in devicetree.
>
> Sign
On Thu, 17 Jan 2019 at 09:02, Vijay Khemka wrote:
>
> Makiing memory-region and flash as optional parameter in device
> tree if user needs to use these parameter through ioctl then
> need to define in devicetree.
>
> Signed-off-by: Vijay Khemka
Thanks! This looks okay to me. I tested it on one o
Makiing memory-region and flash as optional parameter in device
tree if user needs to use these parameter through ioctl then
need to define in devicetree.
Signed-off-by: Vijay Khemka
---
drivers/misc/aspeed-lpc-ctrl.c | 58 +-
1 file changed, 36 insertions(+), 22
11 matches
Mail list logo
