From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <oss@buserror.net>
Date: Tue, 23 Aug 2016 19:04:45 -0500
Subject: [U-Boot] [PATCH] nand: Fix set_dev checks for no device
In-Reply-To: <20160823222125.ihfaeqwezo3s3qz4@atomide.com>
References: <20160823212621.r6absphhojmfulr4@atomide.com>
 <1471987839.25630.277.camel@buserror.net>
 <20160823220442.zv3guwtetvua5lf3@atomide.com>
 <1471990037.25630.279.camel@buserror.net>
 <20160823222125.ihfaeqwezo3s3qz4@atomide.com>
Message-ID: <1471997085.25630.283.camel@buserror.net>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Tue, 2016-08-23 at 15:21 -0700, Tony Lindgren wrote:
> OK seems to work. Updated patch below.
> 
> Regards,
> 
> Tony
> 8< -----------------
> From: Tony Lindgren <tony@atomide.com>
> Date: Tue, 23 Aug 2016 15:14:26 -0700
> Subject: [PATCHv2] nand: Fix set_dev checks for no device

Could you please send a standalone patch (no 8< ------) generated by git, or
at least that has the "diff" line? ?These aren't even showing up in patchwork
as is.


> If we do nand device 0 command in u-boot on a device that has NAND support
> enabled but no NAND chip, we can get data abort at least on omaps.
> 
> Fix the issue by replaceing the check with nand_info[dev] as
> suggested by Scott Wood.

"replacing the name check with..."

-Scott