All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] mtd: remove compatmac.h
Date: Fri, 19 Aug 2005 23:58:18 +0000	[thread overview]
Message-ID: <20050819235818.GH3615@stusta.de> (raw)
In-Reply-To: <20050819205632.GA5211@mipter.zuzino.mipt.ru>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On Sat, Aug 20, 2005 at 03:46:45AM +0400, Alexey Dobriyan wrote:
> On Fri, Aug 19, 2005 at 11:15:17PM +0200, Adrian Bunk wrote:
> > On Sat, Aug 20, 2005 at 12:56:32AM +0400, Alexey Dobriyan wrote:
> > 
> > > File is effectively empty.
> > >...
> > 
> > That's expected.
> > 
> > The trick is that it's non-empty in 2.4
> 
> Take assorted snippets from version.h, compiler.h, wait.h, uaccess.h,
> module.h, byteorder.h, types.h, spinlock.h, kernel.h, blkdev.h and
> others, mix them, multiply by LINUX_VERSION_CODE [1] ifdeffery [2], add
> some bugs(?) going to happen [3], mix once again and you'll get
> compatmac.h from 2.4. :-\ Just like any other compat header this one is
> mess.
> 
> > and provides some code for letting 2.6 code running on 2.4 .
> > 
> > As long as the MTD maintainer wants to share the code between 2.4 and 
> > 2.6 your patch makes his life much harder.
> 
> As long as patches don't include pretty localized headers in context it
> shouldn't.

Compat headers are a mess, but OTOH it often makes maintaining the code 
for the maintainers much easier if they can use the same file in both 
2.4 and 2.6.

The 2.4 compatmac.h might be a mess, and if you find bugs affecting 2.4 
in it please send patches to fix them.

From a 2.6 point of view, the compatmac.h approach is the best I've ever 
seen because #include'ing an empty file doesn't do much harm (I've 
already seen and removed some pretty ugly #ifdef's and wrapper functions 
doing similar things).

It't up to the MTD maintainer (Cc'ed) whether he wants to continue to 
use this file or whether he'll accept your patch.

> 	Alexey
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-08-19 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 20:56 [KJ] [PATCH] mtd: remove compatmac.h Alexey Dobriyan
2005-08-19 21:15 ` Adrian Bunk
2005-08-19 23:46 ` Alexey Dobriyan
2005-08-19 23:58 ` Adrian Bunk [this message]
2005-08-20  9:09 ` 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=20050819235818.GH3615@stusta.de \
    --to=bunk@stusta.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.