From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations
Date: Tue, 03 Jan 2017 18:30:32 +0000 [thread overview]
Message-ID: <20170103183032.GA4426@kroah.com> (raw)
In-Reply-To: <87r34kniic.fsf@eliezer.anholt.net>
On Tue, Jan 03, 2017 at 09:46:51AM -0800, Eric Anholt wrote:
> SF Markus Elfring <elfring@users.sourceforge.net> writes:
>
> > From: Markus Elfring <elfring@users.sourceforge.net>
> > Date: Sat, 31 Dec 2016 22:42:34 +0100
> >
> > Some update suggestions were taken into account
> > from static source code analysis.
>
> This series is:
>
> Reviewed-by: Eric Anholt <eric@anholt.net>
Nice, but I have a blacklist from this patch author, and have told them
numerous times that I no longer accept patches from them. If you think
they are worthy, please resend them with your reviewed-by on them, but I
will warn you, I've blacklisted them for a reason...
good luck!
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations
Date: Tue, 3 Jan 2017 19:30:32 +0100 [thread overview]
Message-ID: <20170103183032.GA4426@kroah.com> (raw)
In-Reply-To: <87r34kniic.fsf@eliezer.anholt.net>
On Tue, Jan 03, 2017 at 09:46:51AM -0800, Eric Anholt wrote:
> SF Markus Elfring <elfring@users.sourceforge.net> writes:
>
> > From: Markus Elfring <elfring@users.sourceforge.net>
> > Date: Sat, 31 Dec 2016 22:42:34 +0100
> >
> > Some update suggestions were taken into account
> > from static source code analysis.
>
> This series is:
>
> Reviewed-by: Eric Anholt <eric@anholt.net>
Nice, but I have a blacklist from this patch author, and have told them
numerous times that I no longer accept patches from them. If you think
they are worthy, please resend them with your reviewed-by on them, but I
will warn you, I've blacklisted them for a reason...
good luck!
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Anholt <eric@anholt.net>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
devel@driverdev.osuosl.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
kbuild test robot <fengguang.wu@intel.com>,
popcornmix@gmail.com, Lee Jones <lee@kernel.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Wei Yongjun <weiyongjun1@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations
Date: Tue, 3 Jan 2017 19:30:32 +0100 [thread overview]
Message-ID: <20170103183032.GA4426@kroah.com> (raw)
In-Reply-To: <87r34kniic.fsf@eliezer.anholt.net>
On Tue, Jan 03, 2017 at 09:46:51AM -0800, Eric Anholt wrote:
> SF Markus Elfring <elfring@users.sourceforge.net> writes:
>
> > From: Markus Elfring <elfring@users.sourceforge.net>
> > Date: Sat, 31 Dec 2016 22:42:34 +0100
> >
> > Some update suggestions were taken into account
> > from static source code analysis.
>
> This series is:
>
> Reviewed-by: Eric Anholt <eric@anholt.net>
Nice, but I have a blacklist from this patch author, and have told them
numerous times that I no longer accept patches from them. If you think
they are worthy, please resend them with your reviewed-by on them, but I
will warn you, I've blacklisted them for a reason...
good luck!
greg k-h
next prev parent reply other threads:[~2017-01-03 18:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 21:54 [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations SF Markus Elfring
2016-12-31 21:54 ` SF Markus Elfring
2016-12-31 21:54 ` SF Markus Elfring
2016-12-31 21:58 ` [PATCH 1/6] staging: vchiq_arm: Use kmalloc_array() in dump_phys_mem() SF Markus Elfring
2016-12-31 21:58 ` SF Markus Elfring
2016-12-31 21:58 ` SF Markus Elfring
2016-12-31 22:00 ` [PATCH 2/6] staging: vchiq_arm: Adjust 13 checks for null pointers SF Markus Elfring
2016-12-31 22:00 ` SF Markus Elfring
2016-12-31 22:00 ` SF Markus Elfring
2016-12-31 22:01 ` [PATCH 3/6] staging: vchiq_arm: One check less in dump_phys_mem() after error detection SF Markus Elfring
2016-12-31 22:01 ` SF Markus Elfring
2016-12-31 22:01 ` SF Markus Elfring
2016-12-31 22:03 ` [PATCH 4/6] staging: vchiq_arm: Delete an error message for a failed memory allocation in dump_phys_ SF Markus Elfring
2016-12-31 22:03 ` [PATCH 4/6] staging: vchiq_arm: Delete an error message for a failed memory allocation in dump_phys_mem() SF Markus Elfring
2016-12-31 22:03 ` SF Markus Elfring
2016-12-31 22:04 ` [PATCH 5/6] staging: vchiq_arm: Combine substrings for 24 messages SF Markus Elfring
2016-12-31 22:04 ` SF Markus Elfring
2016-12-31 22:04 ` SF Markus Elfring
2016-12-31 22:06 ` [PATCH 6/6] staging: vchiq_arm: Delete an unnecessary return statement in two functions SF Markus Elfring
2016-12-31 22:06 ` SF Markus Elfring
2016-12-31 22:06 ` SF Markus Elfring
2017-01-03 17:46 ` [PATCH 0/6] staging: vchiq_arm: Fine-tuning for some function implementations Eric Anholt
2017-01-03 17:46 ` Eric Anholt
2017-01-03 17:46 ` Eric Anholt
2017-01-03 18:30 ` Greg Kroah-Hartman [this message]
2017-01-03 18:30 ` Greg Kroah-Hartman
2017-01-03 18:30 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170103183032.GA4426@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.