LKML Archive on
help / color / mirror / Atom feed
From: Konstantin Kletschke <>
Subject: Re: ARM i.MX serial: fix tx buffer overflows
Date: Mon, 29 Jan 2007 17:43:30 +0100	[thread overview]
Message-ID: <20070129164330.GA4006@synertronixx3> (raw)
In-Reply-To: <>

Am 2007-01-29 15:37 +0000 schrieb Russell King:

> Is it really worth adding additional code to shut up this (imho) silly
> warning?  It's just adding needless complexity to drivers.

As I pointed out in
the console gets flooded with this "warning" to unusable state sometimes.

> What happens if a driver is used on multiple platforms, some of which
> support trigger setting and others which don't?  Are we going to end
> up with a large #ifdef in every driver?

I don't know exactly. But in addition to the fact, that this warning
floods my console to unusable state I am used to sell software without
warnings. If there are warnings my boss some things are broken.


Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

      reply	other threads:[~2007-01-29 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 15:51 Sascha Hauer
2007-01-05 18:01 ` Pavel Pisa
2007-01-29 14:47   ` Konstantin Kletschke
2007-01-29 15:37     ` Russell King
2007-01-29 16:43       ` Konstantin Kletschke [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070129164330.GA4006@synertronixx3 \ \ \ \ \
    --subject='Re: ARM i.MX serial: fix tx buffer overflows' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).