public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, support@moxa.com.tw,
	"Michael H. Warfield" <mhw@wittsend.com>
Subject: Re: [PATCH] Char: remove unneded termbits redefinitions
Date: Sat, 07 Oct 2006 14:22:37 +0159	[thread overview]
Message-ID: <45279C24.1080004@gmail.com> (raw)
In-Reply-To: <20061006181641.e437548e.akpm@osdl.org>

Andrew Morton wrote:
> On Wed,  4 Oct 2006 18:49:01 +0200 (CEST)
> Jiri Slaby <jirislaby@gmail.com> wrote:
> 
>> Char, remove unneded termbits redefinitions
>>
>> No need to redefine termbits in char tree.
> 
> drivers/char/ip2/ip2main.c:2498: error: 'B153600' undeclared (first use in this function)
> drivers/char/ip2/ip2main.c:2498: error: (Each undeclared identifier is reported only once
> drivers/char/ip2/ip2main.c:2498: error: for each function it appears in.)
> drivers/char/ip2/ip2main.c:2500: error: 'B307200' undeclared (first use in this function)
> 
> Unless you're a sparc user, methinks you didn't compile this one.
> 
> I suppose an appropriate fix would be to move the B153600 and B307200
> definitions into include/asm-*/termbits.h (those which don't already have it).
> But that's just a guess.

Hum, I thought I had at least compiled it :/. Next time I'll double-check!

The problem is, that sparc defines it in a little bit different way.
ip2 does this: <<EOF
#ifndef B153600
#       define B153600   0010005
#endif
#ifndef B307200
#       define B307200   0010006
#endif
#ifndef B921600
#       define B921600   0010007
#endif
EOF

and sparc termbits looks like this: <<EOF
/* This is what we can do with the Zilogs. */
#define  B76800   0x00001005
/* This is what we can do with the SAB82532. */
#define  B153600  0x00001006
#define  B307200  0x00001007
#define  B614400  0x00001008
#define  B921600  0x00001009
EOF

This diversity should be eliminated, I guess. What do char-folks think about 
this? Should we move this bits into asm-specific directories?

sorry,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

      reply	other threads:[~2006-10-07 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1236876321987@karneval.cz>
2006-10-04 20:09 ` [PATCH] Char: remove unneded termbits redefinitions Michael H. Warfield
2006-10-07  1:16 ` Andrew Morton
2006-10-07 12:23   ` Jiri Slaby [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=45279C24.1080004@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhw@wittsend.com \
    --cc=support@moxa.com.tw \
    /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