From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Jones Subject: Re: [3/3] mfd/omap-usb-tll: Return an error code only as a constant in usbtll_omap_probe() Date: Wed, 24 Jan 2018 15:16:40 +0000 Message-ID: <20180124151640.t4dayoyh7iv4wvmm@dell> References: <367e77d8-3a65-2c12-5e79-75a626b65f41@users.sourceforge.net> <20180122155057.7eiu53l6xjls6uga@dell> <20180123130440.lgfoeq4rzsa2e4gk@dell> <20180123150408.tljqon24yhbartkw@dell> <20180123171346.GA5296@lenoch> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20180123171346.GA5296@lenoch> Sender: kernel-janitors-owner@vger.kernel.org To: Ladislav Michl Cc: SF Markus Elfring , linux-omap@vger.kernel.org, LKML , kernel-janitors@vger.kernel.org, Tony Lindgren List-Id: linux-omap@vger.kernel.org On Tue, 23 Jan 2018, Ladislav Michl wrote: > Lee, > > On Tue, Jan 23, 2018 at 03:04:08PM +0000, Lee Jones wrote: > > On Tue, 23 Jan 2018, SF Markus Elfring wrote: > > > > > >> Applied, thanks. > > > > > > > > This patch does not apply. > > > > > > > > Please rebase and resend. > > > > > > Did you notice that this update suggestion could eventually be superseded > > > by the software change “[PATCH v2] mfd: omap-usb-tll: Allocate driver data at once”? > > > > How would I? It looks like a completely different patch. > > > > In future, please either reply to the original patch with the > > follow-up patch OR reply to the original patch to say it's been > > superseded, and provide an indication of which patch superseded it. > > this is my fault. I should point out that v2 superseded also other > patches in the serie (see previous discussion, how that happened). > > I'm sorry for this. Not a problem. -- Lee Jones Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog