Hi Richard,
Richard Weinberger wrote on Tue, 11 Jun
2019 22:16:36 +0200:
> On Tue, Jun 11, 2019 at 10:03 PM Kamal Dasu wrote:
> >
> > Richard,
> >
> > You have any other review comments/concerns with this patch, if not
> > can you please sign off on it.
>
> I'm fine with that approach.
> I
On Tue, Jun 11, 2019 at 10:03 PM Kamal Dasu wrote:
>
> Richard,
>
> You have any other review comments/concerns with this patch, if not
> can you please sign off on it.
I'm fine with that approach.
I hoped to get some input from other MTD folks too :-(
--
Thanks,
//richard
Richard,
You have any other review comments/concerns with this patch, if not
can you please sign off on it.
Thanks
Kamal
On Fri, May 17, 2019 at 7:56 AM Kamal Dasu wrote:
>
> On Fri, May 17, 2019 at 4:12 AM Richard Weinberger
> wrote:
> >
> > On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
On Fri, May 17, 2019 at 4:12 AM Richard Weinberger
wrote:
>
> On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
> >
> > If mtd_oops is in progress, switch to polling during NAND command
> > completion instead of relying on DMA/interrupts so that the mtd_oops
> > buffer can be completely written
On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
>
> If mtd_oops is in progress, switch to polling during NAND command
> completion instead of relying on DMA/interrupts so that the mtd_oops
> buffer can be completely written in the assigned NAND partition.
With the new flag the semantics
If mtd_oops is in progress, switch to polling during NAND command
completion instead of relying on DMA/interrupts so that the mtd_oops
buffer can be completely written in the assigned NAND partition.
Signed-off-by: Kamal Dasu
---
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 48
6 matches
Mail list logo