linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: move headers out of include/linux/raid/
Date: Fri, 6 Mar 2009 14:26:45 +1100	[thread overview]
Message-ID: <18864.38901.234155.887209@notabene.brown> (raw)
In-Reply-To: message from Christoph Hellwig on Thursday March 5

On Thursday March 5, hch@infradead.org wrote:
> On Thu, Mar 05, 2009 at 01:47:47PM +1100, Neil Brown wrote:
> > On Tuesday March 3, hch@lst.de wrote:
> > > Move the headers with the local structures for the disciplines and
> > > bitmap.h into drivers/md/ so that they are more easily grepable for
> > > hacking and not far away.  md.h is left where it is for now as there
> > > are some uses from the outside.
> > > 
> > 
> > I really like this, thanks.  I much prefer having the includes with
> > the C files where they are truly local.
> > 
> > I've added a few patches to move md_k.h into drivers/md as well.
> > I'll include them below for reference.
> 
> Btw, I think md_k.h should just be named md.h after that move, and the
> old md.h in include/linux/raid/ should just go away once all the
> function declarations & co are moved out.
> 

Yes, of course.
That makes it much tidier.

All done and pushed to git://neil.brown.name/md for-next
to be picked up by -next on Monday I guess.

Thanks!
NeilBrown

      reply	other threads:[~2009-03-06  3:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 18:30 [PATCH] md: move headers out of include/linux/raid/ Christoph Hellwig
2009-03-05  2:47 ` Neil Brown
2009-03-05 11:57   ` Christoph Hellwig
2009-03-06  3:26     ` Neil Brown [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=18864.38901.234155.887209@notabene.brown \
    --to=neilb@suse.de \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).