mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: agk@sourceware.org, jens.axboe@oracle.com,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH] dm: Add support for data integrity to DM
Date: Tue, 23 Sep 2008 14:41:10 -0400	[thread overview]
Message-ID: <1222195272-18674-1-git-send-email-martin.petersen@oracle.com> (raw)
In-Reply-To: <20080920211433.9e1a6872.akpm@linux-foundation.org>


>>>>> "Andrew" == Andrew Morton <akpm@linux-foundation.org> writes:

Sorry about the delayed response.  I'm still on the road after LPC.

Andrew> For better or for worse, the developers of dm.c have chosen to
Andrew> keep the whole file presentable in an 80-col display.  This
Andrew> patch breaks that, and they might not like this.

I've broken the lines.


[Excessive BUG_ONs]

Andrew> This will provide no more information than the oops which will
Andrew> happen two lines later.

Debugging debris.  Gone.


>> +struct request_queue *dm_queue(struct mapped_device *md)
>> +{
>> +    return md->queue;
>> +}

Andrew> This (unused, undocumented) function should be inlined.

 - It's not unused.

 - return md->queue is more descriptive than anything I could possibly
   put in a comment.

 - None of the other accessor functions in DM are inlined.  I'll let
   Alasdair decide.

Updated patches follow.

-- 
Martin K. Petersen      Oracle Linux Engineering

  reply	other threads:[~2008-09-23 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  0:16 Martin K. Petersen
2008-09-21  4:14 ` Andrew Morton
2008-09-23 18:41   ` Martin K. Petersen [this message]
2008-09-23 18:41   ` [PATCH 1/2] block: Find bio sector offset given idx and offset Martin K. Petersen
2008-09-23 18:41   ` [PATCH 2/2] dm: Add support for data integrity to DM Martin K. Petersen
2008-09-23 19:29     ` [dm-devel] " Kiyoshi Ueda
2008-09-24 16:23       ` Kiyoshi Ueda
2008-09-29 15:05       ` Martin K. Petersen

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=1222195272-18674-1-git-send-email-martin.petersen@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=agk@sourceware.org \
    --cc=dm-devel@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®