public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Jason Gunthorpe <jgg@ziepe.ca>, linux-rdma@vger.kernel.org
Cc: Max Gurtovoy <maxg@mellanox.com>,
	Doug Ledford <dledford@redhat.com>,
	Or Gerlitz <ogerlitz@mellanox.com>, Roi Dayan <roid@mellanox.com>,
	Sagi Grimberg <sagi@grimberg.me>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [0/3] IB-iSER: Adjustments for three function implementations
Date: Mon, 29 Jan 2018 11:28:37 +0100	[thread overview]
Message-ID: <66bbf52f-c043-e027-277c-8f0195794a4c@users.sourceforge.net> (raw)
In-Reply-To: <20180128211050.GM23869@ziepe.ca>

> Okay, applied to for-next, thanks both

Thanks for your acceptance.

How are the chances for integration of further software updates
from my selection of change possibilities?

Example:
IB/iser: Add spaces for better code readability
https://lkml.org/lkml/2017/4/7/667
https://patchwork.kernel.org/patch/9670439/
https://lkml.kernel.org/r/<7e406ba5-f7c8-16a7-9c3e-464e48120088@users.sourceforge.net>

Regards,
Markus

      reply	other threads:[~2018-01-29 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 18:17 [PATCH 0/3] IB-iSER: Adjustments for three function implementations SF Markus Elfring
2018-01-27 18:18 ` [PATCH 1/3] IB/iser: Delete an error message for a failed memory allocation in iser_send_data_out() SF Markus Elfring
2018-01-27 18:20 ` [PATCH 2/3] IB/iser: Delete an unnecessary variable initialisation " SF Markus Elfring
2018-01-27 18:21 ` [PATCH 3/3] IB/iser: Combine substrings for three messages SF Markus Elfring
2018-01-28 14:41 ` [PATCH 0/3] IB-iSER: Adjustments for three function implementations Max Gurtovoy
2018-01-28 21:10   ` Jason Gunthorpe
2018-01-29 10:28     ` SF Markus Elfring [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=66bbf52f-c043-e027-277c-8f0195794a4c@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maxg@mellanox.com \
    --cc=ogerlitz@mellanox.com \
    --cc=roid@mellanox.com \
    --cc=sagi@grimberg.me \
    /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