linux-kernel - Re: [3/3] mfd/omap-usb-tll: Return an error code only as a constant in usbtll_omap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180123150408.tljqon24yhbartkw@dell>
Date:   Tue, 23 Jan 2018 15:04:08 +0000
From:   Lee Jones <lee.jones@...aro.org>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc:     linux-omap@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org, Tony Lindgren <tony@...mide.com>,
        Ladislav Michl <ladis@...ux-mips.org>
Subject: Re: [3/3] mfd/omap-usb-tll: Return an error code only as a constant
 in usbtll_omap_probe()

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.

> https://lkml.org/lkml/2018/1/23/277
> https://patchwork.kernel.org/patch/10165339/
> https://lkml.kernel.org/r/<20180115202505.GA2628@...och>

-- 
Lee Jones
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog