From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-s390@vger.kernel.org,
"Jan Höppner" <hoeppner@linux.vnet.ibm.com>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Stefan Haberland" <sth@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/3] S390-DASD: Fine-tuning for some function implementations
Date: Thu, 14 Dec 2017 12:07:34 +0100 [thread overview]
Message-ID: <20171214110734.GD4238@osiris> (raw)
In-Reply-To: <d7e6649b-cdb4-e686-df0e-472958c94202@users.sourceforge.net>
On Thu, Dec 14, 2017 at 11:34:01AM +0100, SF Markus Elfring wrote:
> > Date: Wed, 10 May 2017 19:43:21 +0200
> >
> > A few update suggestions were taken into account
> > from static source code analysis.
> >
> > Markus Elfring (3):
> > Adjust buffer output in dasd_hosts_print()
> > Fix typos in two comment lines
> > Adjust six checks for null pointers
> >
> > drivers/s390/block/dasd_eckd.c | 24 +++++++++++-------------
> > 1 file changed, 11 insertions(+), 13 deletions(-)
>
>
> Are there any chances that such change possibilities (and further adjustments)
> will be integrated in this software area?
No.
prev parent reply other threads:[~2017-12-14 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 18:00 [PATCH 0/3] S390-DASD: Fine-tuning for some function implementations SF Markus Elfring
2017-05-10 18:01 ` [PATCH 1/3] s390/dasd: Adjust buffer output in dasd_hosts_print() SF Markus Elfring
2017-05-10 19:28 ` Dan Carpenter
2017-05-10 22:30 ` kbuild test robot
2017-05-10 18:02 ` [PATCH 2/3] s390/dasd: Fix typos in two comment lines SF Markus Elfring
2017-05-10 18:03 ` [PATCH 3/3] s390/dasd: Adjust six checks for null pointers SF Markus Elfring
2017-12-14 10:34 ` [PATCH 0/3] S390-DASD: Fine-tuning for some function implementations SF Markus Elfring
2017-12-14 11:07 ` Heiko Carstens [this message]
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=20171214110734.GD4238@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=elfring@users.sourceforge.net \
--cc=hoeppner@linux.vnet.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sth@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).