From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Kerr Date: Sat, 25 May 2019 07:37:06 +0800 Subject: [U-Boot] [PATCH v2 0/2] Add 'bcb' command to read/modify/write Android BCB In-Reply-To: <20190524193633.GB11798@vmlxhi-102.adit-jv.com> References: <20190517144503.3275-1-erosca@de.adit-jv.com> <20190517152457.GA5239@vmlxhi-102.adit-jv.com> <2dce29c3676523aef32efc2eaf4fe911d4e82654.camel@that.guru> <20190517152825.GA6378@vmlxhi-102.adit-jv.com> <20190524193633.GB11798@vmlxhi-102.adit-jv.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Eugeniu, > jFYI/FWIW, a recent patch series no longer suffers from this problem: > https://patchwork.ozlabs.org/cover/1104242/ > ("[U-Boot,v3,0/3] Add 'bcb' command to read/modify/write Android BCB") OK, super. I'd applied the fix for that issue on patchwork.ozlabs.org last week. > However, the old series still exhibits the issue, as if the old series > is rendered by the old patchwork version: > https://patchwork.ozlabs.org/cover/1101106/ > ("[U-Boot,v2,0/2] Add 'bcb' command to read/modify/write Android BCB") The issue was with the parser. Since the patch was parsed before the fix was applied, it'll remain like that. Cheers, Jeremy