public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] push down inclusion of buffer_head.h into users
Date: Mon, 20 May 2002 18:17:31 -0700	[thread overview]
Message-ID: <20020520181731.K2996@work.bitmover.com> (raw)
In-Reply-To: <20020520190033.A414@infradead.org> <20020521011108.A22488@infradead.org>

Hi Christoph,

while it is true that BK will do the right thing if Linus applies this patch
and then you pull it, it's a lot nicer if you let him pull your tree.  

The problem is that you're going to have this in your tree as one delta and
Linus will have it in his tree as another delta.  When you pull, the data
will be in the tree twice.  That's not critical in this case, the amount of
data is relatively small, but it's still sort of messy.  While we can work
out that it is duplicate and make it so you don't have to merge it, it
increases the size of the revision history.  No big deal just this once,
but if everyone does this then we'll eventually get to a revision history
which is a lot less useful because of all the duplicates you have to wade
through to see why something was added.


On Tue, May 21, 2002 at 01:11:08AM +0100, Christoph Hellwig wrote:
> On Mon, May 20, 2002 at 07:00:33PM +0100, Christoph Hellwig wrote:
> > Now that fs.h grow due to the lock.h removal let's reduce it's overhead
> > again:  Instead of penalizing ever user of fs.h with the overhead of the
> > buffer head interface let it's users include it directly.
> > 
> > This also shows nicely which parts of the core kernel still depend on the
> > buffer head interface, and allows that to be cleaned up properly.
> > 
> > Please drop me a note if you have a reason to not include it as it is
> > painfull to update due to the number of files touched.
> 
> Updated to the latest BK tree, UP compilation failures fixed.
> Please include.
> 
> ===== drivers/block/blkpg.c 1.31 vs edited =====
> --- 1.31/drivers/block/blkpg.c	Sun May 19 13:49:48 2002
> +++ edited/drivers/block/blkpg.c	Tue May 21 01:46:38 2002
> @@ -36,6 +36,7 @@
>  #include <linux/genhd.h>
>  #include <linux/module.h>               /* for EXPORT_SYMBOL */
>  #include <linux/backing-dev.h>
> +#include <linux/buffer_head.h>
>  
>  #include <asm/uaccess.h>
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-05-21  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 18:00 [PATCH] push down inclusion of buffer_head.h into users Christoph Hellwig
2002-05-21  0:11 ` Christoph Hellwig
2002-05-21  1:17   ` Larry McVoy [this message]
2002-05-21  8:12     ` 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=20020520181731.K2996@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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