From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 1 Mar 2017 09:49:29 +0100 From: Boris Brezillon To: Hans-Christian Noren Egtvedt Cc: =?UTF-8?B?SMOldmFyZA==?= Skinnemoen , Alexandre Belloni , Andy Shevchenko , Richard Weinberger , "open list:MEMORY TECHNOLOGY..." , Nicolas Ferre , "linux-kernel@vger.kernel.org" , Wenyou Yang , Josh Wu , David Woodhouse , Brian Norris , Marek Vasut , Cyrille Pitchen , linux-arm Mailing List , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree Subject: Re: [PATCH v2 1/3] mtd: nand: Cleanup/rework the atmel_nand driver Message-ID: <20170301094929.5b0b831d@bbrezillon> In-Reply-To: <20170301083807.GA12981@samfundet.no> References: <20170221171438.e5hvruoixafpcdps@piout.net> <20170224081430.GB19663@samfundet.no> <20170224092742.3ce205e2@bbrezillon> <20170224085209.GA27812@samfundet.no> <20170224095509.777da771@bbrezillon> <20170224090435.GA11313@samfundet.no> <20170301092224.169dc7ae@bbrezillon> <20170301083807.GA12981@samfundet.no> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 1 Mar 2017 09:38:07 +0100 Hans-Christian Noren Egtvedt wrote: > Around Wed 01 Mar 2017 09:22:24 +0100 or thereabout, Boris Brezillon wrot= e: > > Hi Hans-Christian, > >=20 > > On Fri, 24 Feb 2017 10:04:35 +0100 > > Hans-Christian Noren Egtvedt wrote: > > =20 > >> Around Fri 24 Feb 2017 09:55:09 +0100 or thereabout, Boris Brezillon w= rote: =20 > >> > On Fri, 24 Feb 2017 09:52:09 +0100 > >> > Hans-Christian Noren Egtvedt wrote: =20 > >> >> Around Fri 24 Feb 2017 09:27:42 +0100 or thereabout, Boris Brezillo= n wrote: =20 > >> >> > On Fri, 24 Feb 2017 09:14:30 +0100 Hans-Christian Noren Egtvedt <= egtvedt@samfundet.no> wrote: =20 > >> >> >> Around Thu 23 Feb 2017 21:18:13 -0800 or thereabout, H=C3=A5vard= Skinnemoen wrote: =20 > >> >> >> > On Tue, Feb 21, 2017 at 9:14 AM, Alexandre Belloni > >> >> >> > wrote: =20 > >> >> >> >> On 21/02/2017 at 18:43:35 +0200, Andy Shevchenko wrote: = =20 > >> >>=20 > >> >> > >> >> =20 > >> >> >> >> If nobody complains about the 4.10 breakage, You'll have plen= ty of time > >> >> >> >> to remove it for 4.12 =20 > >> >> >> >=20 > >> >> >> > I'm fine with that, but I haven't put much effort into keeping= it > >> >> >> > alive lately. If Hans-Christian agrees, I'm willing to post a = patch to > >> >> >> > remove it, or ack someone else's patch. =20 > >> >> >>=20 > >> >> >> Then lets plan this for 4.12, either you H=C3=A5vard whip up a p= atch or I can > >> >> >> eventually do it. > >> >> >>=20 > >> >> >> I can push it through the linux-avr32 git tree on kernel.org. > >> >> >> =20 > >> >> >=20 > >> >> > Can you do that just after 4.11-rc1 is released and provide a top= ic > >> >> > branch I can pull in my nand/next branch, so that I can rework th= is > >> >> > patch and drop all the pdata-compat code (as suggested by Andy). = =20 > >> >>=20 > >> >> OK, I will try to prepare it during the weekend. > >> >>=20 > >> >> Any reason to wait for 4.11-rc1? AFAIK Linus prefers the larger cha= nges > >> >> before he starts tagging rc's. > >> >> =20 > >> >=20 > >> > Oh, so you want to queue it for 4.11, that's even better. =20 > >>=20 > >> Perhaps I misunderstood you, by after 4.11-rc1 you mean queue it for 4= .12? > >>=20 > >> I will see what I get around to do in the weekend, it should be pretty > >> straightforward, just want to make sure we remove all the bits. > >> =20 > >=20 > > Any progress on this? I plan to send a new version of this series soon > > and I'd like to know if I should drop pdata/avr32 support or not. Note > > that I'm targeting 4.12, so, as long as you drop avr32 support in 4.12 > > we should be good. =20 >=20 > I got around to make the patch series during the weekend, but I thought it > would be a good idea sending them to the kernel mailing list as a FYI. Definitely. >=20 > Also, I was unsure if I should send the driver removals through the > sub-maintainers trees, or if I can push them through linux-avr32 tree. I think it should go through the sub-maintainers trees, but I guess you can remove the arch code without breaking the build, so it shouldn't be a problem if drivers removal don't go through the avr32 tree. >=20 > I have a patch removing the pata driver for AVR32. >=20 Great! Just send everything to the MLs (and relevant maintainers). Thanks, Boris