On Wed, Feb 14, 2018 at 02:58:41AM +, Michael Kelley (EOSG) wrote:
> > -Original Message-
> > From: Dan Carpenter
> > Sent: Monday, February 12, 2018 12:42 AM
> > To: KY Srinivasan ; Stephen Hemminger
> >
> >
> -Original Message-
> From: Dan Carpenter
> Sent: Monday, February 12, 2018 12:42 AM
> To: KY Srinivasan ; Stephen Hemminger
>
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
>
Hi Greg
On 2018/2/12 19:40, Yisheng Xie wrote:
> Hi Greg,
>
> JFYI, I have rebase this patchset to v4.15-rc1.[1]
Ah, sorry , I mean v4.16-rc1, and the same to other threads.
Thanks
Yisheng
>
> [1] https://lkml.org/lkml/2018/2/12/204
>
> Thanks
> Yisheng
>
> On 2018/2/1 9:54, Yisheng Xie
On 02/13/2018 08:40 PM, Laura Abbott wrote:
> On 02/12/2018 11:24 PM, Alexey Skidanov wrote:
>> Hello,
>>
>> Correct me if I'm wrong, but there is no user space interface, similar
>> to the dma_buf_start_cpu_access()/dma_buf_end_cpu_access() to handle IO
>> coherency. That is, on the platforms,
> if (rbi->ring_buffer->feature_bits.feat_pending_send_sz) {
> u32 pending_sz = READ_ONCE(rbi->ring_buffer->pending_send_sz);
>
> /*
> + * Ensure the read of write_index in hv_get_bytes_to_write()
> + * happens after the read of
On 12/02/18 21:03, Boris Brezillon wrote:
> MTD users are no longer checking erase_info->state to determine if the
> erase operation failed or succeeded. Moreover, mtd_erase_callback() is
> now a NOP.
>
> We can safely get rid of all mtd_erase_callback() calls and all
> erase_info->state
Hi Boris,
On Tue, 13 Feb 2018 09:17:14 +0100, Boris Brezillon
wrote:
> On Tue, 13 Feb 2018 08:42:46 +0100
> Miquel Raynal wrote:
>
> > Hi Boris,
> >
> > Just a few comments about the form.
> >
> > Otherwise:
> > Reviewed-by: Miquel
On Tue, 13 Feb 2018 08:42:46 +0100
Miquel Raynal wrote:
> Hi Boris,
>
> Just a few comments about the form.
>
> Otherwise:
> Reviewed-by: Miquel Raynal
>
>
> > diff --git a/drivers/mtd/devices/lart.c b/drivers/mtd/devices/lart.c
> >