public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, linux-block@vger.kernel.org
Subject: Re: misc block cleanups
Date: Fri, 14 Dec 2018 14:00:22 +0100	[thread overview]
Message-ID: <20181214130022.GA11066@lst.de> (raw)
In-Reply-To: <5a57919d-7098-8b00-bc72-54538d384d09@kernel.dk>

On Thu, Dec 13, 2018 at 09:28:33PM -0700, Jens Axboe wrote:
> On 12/13/18 1:32 PM, Christoph Hellwig wrote:
> > Remove a few pointless helpers and unused exports.
> 
> We've got quite a bit of churn this round, do you mind if we
> push #1 to next round? I'm fine with killing the exports, if
> they are not used, they should go.

Sure, fine with me.  Are you going to drop the accidental hunk
yourself or should I resend?

  reply	other threads:[~2018-12-14 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 20:32 misc block cleanups Christoph Hellwig
2018-12-13 20:32 ` [PATCH 1/7] block: remove bio_set_prio and bio_prio Christoph Hellwig
2018-12-13 20:32 ` [PATCH 2/7] block: remove the bio_phys_segments export Christoph Hellwig
2018-12-14  4:27   ` Jens Axboe
2018-12-13 20:32 ` [PATCH 3/7] block: remove the blk_recount_segments export Christoph Hellwig
2018-12-13 20:32 ` [PATCH 4/7] block: remove the unused bio_iov_iter_get_pages export Christoph Hellwig
2018-12-13 20:32 ` [PATCH 5/7] block: remove the unused bio_set_pages_dirty and bio_check_pages_dirty exports Christoph Hellwig
2018-12-13 20:32 ` [PATCH 6/7] block: remove the bioset_integrity_free export Christoph Hellwig
2018-12-13 20:32 ` [PATCH 7/7] block: remove the bio_integrity_advance export Christoph Hellwig
2018-12-14  4:28 ` misc block cleanups Jens Axboe
2018-12-14 13:00   ` Christoph Hellwig [this message]
2018-12-14 13:02     ` Jens Axboe

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=20181214130022.GA11066@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox