mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Adrian Bunk <bunk@kernel.org>,
	zippel@linux-m68k.org, linux-m68k@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: [2.6 patch] remove the dead ATARI_SCC{,_DMA} options
Date: Thu, 26 Jun 2008 09:11:06 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806260909490.30924@anakin> (raw)
In-Reply-To: <alpine.DEB.1.00.0806260644080.30738@zirkon.biophys.uni-duesseldorf.de>

On Thu, 26 Jun 2008, Michael Schmitz wrote:
> > It seems the driver was removed back in kernel 2.3 but the options were
> > forgotten.
> > 
> > Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> A revived Atari SCC serial driver should be in Geert's patch queue, or in the

... which needs some rework before it can be submitted, I'm afraid (I can
take care of the checkpatch warnings, though ;-)

> m68k kernel tree. The SCC_DMA option, however, is dead and can be removed.

So I think it's safe to apply the whole patch, and readd
CONFIG_ATARI_SCC together with the new driver.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-06-26  7:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 16:25 Adrian Bunk
2008-06-26  4:45 ` Michael Schmitz
2008-06-26  7:11   ` Geert Uytterhoeven [this message]
2008-06-26 20:57     ` Michael Schmitz
2008-06-26  7:19 ` Geert Uytterhoeven
2008-06-29  4:57 ` Brad Boyer

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=Pine.LNX.4.64.0806260909490.30924@anakin \
    --to=geert@linux-m68k.org \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®