[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170826070407.GA1965@kroah.com>
Date: Sat, 26 Aug 2017 09:04:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Martyn Welch <martyn@...chs.me.uk>
Cc: SF Markus Elfring <elfring@...rs.sourceforge.net>,
devel@...verdev.osuosl.org, Arnd Bergmann <arnd@...db.de>,
Augusto Mecking Caringi <augustocaringi@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Alessio Igor Bogani <alessio.bogani@...ttra.eu>,
Baoyou Xie <baoyou.xie@...aro.org>,
Manohar Vanga <manohar.vanga@...il.com>
Subject: Re: [PATCH 00/14] VME: Adjustments for several function
implementations
On Fri, Aug 25, 2017 at 10:50:19PM +0100, Martyn Welch wrote:
> On Fri, Aug 25, 2017 at 05:41:13PM +0200, SF Markus Elfring wrote:
> > From: Markus Elfring <elfring@...rs.sourceforge.net>
> > Date: Fri, 25 Aug 2017 13:15:43 +0200
> >
> > Several update suggestions were taken into account
> > from static source code analysis.
> >
> > Markus Elfring (14):
> > Delete 11 error messages for a failed memory allocation
> > Improve 11 size determinations
> > Move an assignment in vme_new_dma_list()
> > Adjust 48 checks for null pointers
> > Return directly in two functions
> > fake: Delete an error message for a failed memory allocation in fake_init()
> > fake: Improve five size determinations in fake_init()
> > fake: Adjust 11 checks for null pointers
> > ca91cx42: Delete eight error messages for a failed memory allocation
> > ca91cx42: Improve 12 size determinations
> > ca91cx42: Adjust 14 checks for null pointers
> > tsi148: Delete nine error messages for a failed memory allocation
> > tsi148: Improve 17 size determinations
> > tsi148: Adjust 14 checks for null pointers
> >
>
> Hi Markus,
>
> Thanks for the patches. Other than the minor tweak needed to patch 13,
> these are looking good to me.
You do know this developer is in my kill-file and I refuse to take
patches from them, and strongly recommend that everyone else just ignore
them, right? Also many other maintainers/developers have done the same
to them over time due to their past history.
It's up to you what you want to do, but the only way I'll ever accept
patches from them is if they come through someone else (i.e. you resend
them to me...)
good luck!
greg k-h
Powered by blists - more mailing lists