linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>
Cc: linux-block@vger.kernel.org, linux-s390@vger.kernel.org,
	hoeppner@linux.ibm.com, heiko.carstens@de.ibm.com,
	borntraeger@de.ibm.com, gor@linux.ibm.com
Subject: Re: [PATCH 0/1] sending DASD patches through linux-block
Date: Thu, 1 Aug 2019 20:47:27 -0600	[thread overview]
Message-ID: <c66977ae-7a17-5a54-0519-a69d8f825070@kernel.dk> (raw)
In-Reply-To: <20190801110630.82432-1-sth@linux.ibm.com>

On 8/1/19 5:06 AM, Stefan Haberland wrote:
> Hi Jens,
> 
> we would like to get our DASD related patches upstream through your
> linux-block git tree in the future.
> We hope to get a better integration and that we are able to identify
> potential conflicts with generic blocklayer changes earlier.
> 
> I hope this is OK for you. I have attached a first patch that fixes a
> bug in the DASD driver. This patch is based on the master branch of your
> linux-block git tree.

Certainly. No extra hassle for me, and if it makes it easier for you,
then by all means.

> Please let me know if I should change something in my workflow.

Looks fine to me, I generally prefer patches (individual or series)
to git trees, unless it's a huge series.

-- 
Jens Axboe


      parent reply	other threads:[~2019-08-02  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 11:06 [PATCH 0/1] sending DASD patches through linux-block Stefan Haberland
2019-08-01 11:06 ` [PATCH 1/1] s390/dasd: fix endless loop after read unit address configuration Stefan Haberland
2019-08-02  2:47   ` Jens Axboe
2019-08-02  2:47 ` Jens Axboe [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=c66977ae-7a17-5a54-0519-a69d8f825070@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sth@linux.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).