All of lore.kernel.org
 help / color / mirror / Atom feed
From: manabian@gmail.com (Joachim Eastwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: at91: remove at91_register_uart_fns and headers
Date: Wed, 11 Apr 2012 18:35:17 +0200	[thread overview]
Message-ID: <CAGhQ9VxxS7fZ1X4rKiTaWoS7TK0goaJ1nCw3UDC4CCzsSJVudw@mail.gmail.com> (raw)
In-Reply-To: <4F856D0E.5040802@atmel.com>

On Wed, Apr 11, 2012 at 1:37 PM, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> On 04/08/2012 11:55 PM, Andrew Victor :
>> hi,
>>
>>> Yeah, as far as I know, nobody ever used this functionality on AVR32.
>>> In fact, I can't even think of a reason to use it.
>>>
>>> But I seem to recall submitting a patch to remove this functionality a
>>> long time ago, and it was struck down. I don't remember the reason,
>>> but there's a chance it might still be valid.
>>
>> Some of the SAN People / Multenet AT91RM9200 boards needed it....
>> We needed to use GPIO pins for some of the modem-control signals -
>> couldn't use the standard pins since the alternate pin function was
>> being used.
>>
>> Regards,
>> ?Andrew Victor
>
> Hi Andrew,
>
> Well if it is of some interest on your side, I am in favor of keeping
> this feature. It is not a so big amount of code and seems quite easy to
> maintain...

It's not a big deal for me whether the code stays or not. The only reason I
bumped into it was while trying to get atmel_serial to compile as a module
and the serial_at91.h header generated some build error.

But still, why keep a feature with no mainline users. A new kernel feature
is never accepted without any users.

I also think it's hard to maintain the code without any users. I may be easy
to preserve the code but you can never change/improve the code since
you can't change the users of the code.

regards
Joachim Eastwood

      reply	other threads:[~2012-04-11 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 16:02 [PATCH RFC] ARM: at91: remove at91_register_uart_fns and headers Joachim Eastwood
2012-04-06 16:19 ` Joachim Eastwood
2012-04-08 18:09 ` Hans-Christian Egtvedt
2012-04-08 21:21   ` Håvard Skinnemoen
2012-04-08 21:55     ` Andrew Victor
2012-04-11 11:37       ` Nicolas Ferre
2012-04-11 16:35         ` Joachim Eastwood [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=CAGhQ9VxxS7fZ1X4rKiTaWoS7TK0goaJ1nCw3UDC4CCzsSJVudw@mail.gmail.com \
    --to=manabian@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.