linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Andrew Victor <avictor.za@gmail.com>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>,
	linux-ide@vger.kernel.org, Andrew Victor <linux@maxim.org.za>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 2/3] ide: add at91_ide driver
Date: Thu, 05 Feb 2009 23:03:23 +0300	[thread overview]
Message-ID: <498B460B.20205@ru.mvista.com> (raw)
In-Reply-To: <cd73a99e0902051200ob1787e2v73e750344ca44ec9@mail.gmail.com>

Andrew Victor wrote:

>>>>>>AT91SAM9.

>>>>>Ok, currently only SAM9 can be used with driver. However I think adding
>>>>>support to AT91RM9200 to this driver will be not much effort.

>>>>  Can you answer the simple question: why we should try to support two
>>>>incompatible chips with a single driver? Because the driver name will be
>>>>shorter? :-)

>>>Very funny. I think patch adding RM9200 support to this driver will have
>>>less
>>>than 50 lines changeset,  whereas writing new driver would be about 500
>>>lines.

>>  This approach is so broken-minded that I'm just out words to argue any
>>more.

> This driver should also work on the Atmel AT91CAP9 and AT572D940HF processors.
> So I see no valid reason why the driver cannot be called at91_ide.

    I've already said: call it whatever you want. Just don't try to add 
support for an incompatible AT91 SMC.

> Regards,
>   Andrew Victor

MBR, Sergei

  reply	other threads:[~2009-02-05 20:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 10:47 [PATCH 2/3] ide: add at91_ide driver Stanislaw Gruszka
2009-02-04 12:19 ` Sergei Shtylyov
2009-02-04 14:47   ` Stanislaw Gruszka
2009-02-04 16:04     ` Sergei Shtylyov
2009-02-04 16:08       ` Sergei Shtylyov
2009-02-05 15:01       ` Stanislaw Gruszka
2009-02-05 16:09         ` Sergei Shtylyov
2009-02-05 20:00           ` Andrew Victor
2009-02-05 20:03             ` Sergei Shtylyov [this message]
2009-02-06  9:35           ` Stanislaw Gruszka
2009-02-06 10:55           ` Sergei Shtylyov
2009-02-06 16:50             ` Bartlomiej Zolnierkiewicz
2009-02-06 17:20               ` Sergei Shtylyov
2009-02-05 21:23   ` Bartlomiej Zolnierkiewicz
2009-02-05 23:31     ` Sergei Shtylyov
2009-02-06 16:36       ` Bartlomiej Zolnierkiewicz
2009-02-08  0:10         ` Sergei Shtylyov
2009-02-08 11:39           ` Sergei Shtylyov
2009-02-08 22:58             ` Sergei Shtylyov
2009-02-09 19:48               ` Bartlomiej Zolnierkiewicz
2009-02-06  9:30   ` Stanislaw Gruszka
2009-02-06 10:36     ` Sergei Shtylyov
2009-02-06 10:47       ` Stanislaw Gruszka

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=498B460B.20205@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=avictor.za@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=stf_xl@wp.pl \
    /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;
as well as URLs for NNTP newsgroup(s).