[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACna6rxNbPzSYbe9GjQCSAeB8FgVi6ZpgKo=AB=6nYc4QcqN1g@mail.gmail.com>
Date: Thu, 16 Oct 2014 10:12:47 +0200
From: Rafał Miłecki <zajec5@...il.com>
To: Bean Huo 霍斌斌 (beanhuo)
<beanhuo@...ron.com>
Cc: Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marex@...x.de>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"grmoore@...era.com" <grmoore@...era.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"shijie8@...il.com" <shijie8@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"geert+renesas@...der.be" <geert+renesas@...der.be>
Subject: Re: [PATCH 1/1 v2] driver:mtd:spi-nor:fix spi_nor_scan overwrite
platform ID point
On 16 October 2014 10:00, Bean Huo 霍斌斌 (beanhuo) <beanhuo@...ron.com> wrote:
>>There are a lot of changes happening/requested around this code. I also proposed some patch touching this code, see https://patchwork.ozlabs.org/patch/377917/
>
>>Right now there is a slow ongoing work on fixing some m25p80 regression, which also may touch the code you change. So I'll suggest postponing this patch until we get a regression fixed and then work on this hacky code again.
>
>
> Thanks for your concerns.But for the same deivce id with the different extended id and
> the same device name with the different device id issue, in your patch,this doesn't take
> into account. I have encountered this situation. for example:
I really wasn't looking into details yet and I'm aware my patch does
something else. I just say we should first fix the regression and then
base next patches on top of that regression fix. I'm not NACKing your
changes :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists