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] KERNEL_VERSION #ifs
Date: Sun, 18 Dec 2005 23:18:35 +0000	[thread overview]
Message-ID: <20051218231835.GO23349@stusta.de> (raw)
In-Reply-To: <1134943209.7082.2.camel@alice>

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

On Sun, Dec 18, 2005 at 03:16:29PM -0700, Matthew Wilcox wrote:
> On Sun, Dec 18, 2005 at 11:00:08PM +0100, Eric Sesterhenn / snakebyte wrote:
> > #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,2,0)
> > 
> > in arch/cris/arch-v32/kernel/fasttimer.c should also be
> > removed (Of course just the if, not the code inside it)
> 
> Yes, but beware that the architecture hasn't been updated in any
> meaningful way since July 27th.  I think cris is pretty much a
> patch-and-run architecture.

The cris maintainers respond to emails, and they should at least get 
copies of patches touching their architecture code.

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-12-18 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 22:00 [KJ] KERNEL_VERSION #ifs Eric Sesterhenn / snakebyte
2005-12-18 22:16 ` Matthew Wilcox
2005-12-18 22:41 ` Eric Sesterhenn / snakebyte
2005-12-18 23:18 ` Adrian Bunk [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=20051218231835.GO23349@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.