[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cdc8383433a1f67f4d5f5d9c528e116ee10c7466.camel@perches.com>
Date: Sun, 01 Jul 2018 13:54:32 -0700
From: Joe Perches <joe@...ches.com>
To: Boris Brezillon <boris.brezillon@...tlin.com>,
Richard Weinberger <richard@....at>
Cc: Quentin Schulz <quentin.schulz@...tlin.com>, dedekind1@...il.com,
dwmw2@...radead.org, computersforpeace@...il.com,
marek.vasut@...il.com, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com
Subject: Re: [PATCH v3 2/2] ubi: expose the volume CRC check skip flag
On Sun, 2018-07-01 at 22:33 +0200, Boris Brezillon wrote:
> On Sun, 01 Jul 2018 21:35:57 +0200 Richard Weinberger <richard@....at> wrote:
> > Am Donnerstag, 28. Juni 2018, 09:40:53 CEST schrieb Quentin Schulz:
> > > Now that we have the logic for skipping CRC check for static UBI volumes
> > > in the core, let's expose it to users.
[]
> > > diff --git a/drivers/mtd/ubi/cdev.c b/drivers/mtd/ubi/cdev.c
[]
> > > @@ -622,6 +622,10 @@ static int verify_mkvol_req(const struct ubi_device *ubi,
> > > req->vol_type != UBI_STATIC_VOLUME)
> > > goto bad;
> > >
> > > + if (req->flags & UBI_VOL_SKIP_CRC_CHECK_FLG &&
>
> Oops, missed that req->flags & UBI_VOL_SKIP_CRC_CHECK_FLG check was
> missing parens (checkpatch --strict should complain about that).
Why should checkpatch complain?
& has higher precedence than &&.
Powered by blists - more mailing lists