From: Wolfram Sang <wsa@the-dreams.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
ulf.hansson@linaro.org, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, joro@8bytes.org,
wsa+renesas@sang-engineering.com, linux-mmc@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-block@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v9 3/5] block: sort headers on blk-setting.c
Date: Thu, 22 Aug 2019 11:35:56 +0200 [thread overview]
Message-ID: <20190822093556.ludte2vtp77fiaax@katana> (raw)
In-Reply-To: <6ed6c62d-d773-71ec-382b-acd850e3dff1@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 180 bytes --]
Hi Jens,
thanks for the feedback.
> Please just drop this patch.
OK, we will do. And patch 4/5? Is it OK or do you need some more time to
think about it?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-22 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 8:31 [PATCH v9 0/5] treewide: improve R-Car SDHI performance Yoshihiro Shimoda
2019-07-26 8:31 ` [PATCH v9 1/5] dma: Introduce dma_get_merge_boundary() Yoshihiro Shimoda
2019-07-26 8:31 ` [PATCH v9 2/5] iommu/dma: Add a new dma_map_ops of get_merge_boundary() Yoshihiro Shimoda
2019-08-16 19:48 ` Wolfram Sang
2019-08-19 12:45 ` Joerg Roedel
2019-08-19 12:54 ` Robin Murphy
2019-08-20 1:42 ` Yoshihiro Shimoda
2019-07-26 8:31 ` [PATCH v9 3/5] block: sort headers on blk-setting.c Yoshihiro Shimoda
2019-08-16 19:50 ` Wolfram Sang
2019-08-19 14:53 ` Jens Axboe
2019-08-20 1:50 ` Yoshihiro Shimoda
2019-08-22 9:35 ` Wolfram Sang [this message]
2019-07-26 8:31 ` [PATCH v9 4/5] block: add a helper function to merge the segments Yoshihiro Shimoda
2019-07-26 8:31 ` [PATCH v9 5/5] mmc: queue: Use bigger segments if DMA MAP layer can " Yoshihiro Shimoda
2019-08-15 7:30 ` [PATCH v9 0/5] treewide: improve R-Car SDHI performance Christoph Hellwig
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=20190822093556.ludte2vtp77fiaax@katana \
--to=wsa@the-dreams.de \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).