public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] ATMEL/PIO: Enable new feature of PIO on Atmel device
Date: Mon, 21 May 2012 13:59:44 +0800	[thread overview]
Message-ID: <4FB9D9D0.3010406@atmel.com> (raw)
In-Reply-To: <4FB62BEC.6000007@gmail.com>

Hi Andreas,

On 5/18/2012 19:01, Andreas Bie?mann wrote:
> Dear Bo Shen,
>
> On 17.05.2012 03:19, Bo Shen wrote:
>> On 5/16/2012 18:42, Andreas Bie?mann wrote:
>>> Dear Bo Shen,
>>>
>>> On 16.05.2012 04:16, Bo Shen wrote:
>
> <snip>
>
>>>> -#ifdef CONFIG_AT91_LEGACY
>>>> -
>
> <snip remove of legacy interface>
>
>>>> -
>>> I think this should be done in a separate patch (series). There are a
>>> lot of CONFIG_AT91_LEGACY left somewhere in the code. Please read
>>> doc/README.at91-soc; I think step 4 is reached so step 5 should follow.
>>
>> Would this be dealt one by one, while not a series?
>
> Well it must not be a series of patches send at once. This can also be
> done step by step e.g. by first cleaning up atmel_pio and doing other
> parts later (I think this should/could be documented in the
> doc/README.at91-soc). This should be carefully considered because you
> may break some boards.
> Beware! I do not really know if my statement 'step 4 of
> doc/README.at91-soc is reached' is correct, so this needs to be proven.
> If you have proven that removing legacy interface of atmel_pio is ok,  I
> would like to see another patch for that task (this patch is 'Enable new
> feature ..' not 'remove legacy interface ..').

I will take this suggestion. Just add the new feature and do not touch 
with the legacy interface. The version 3 has been sent out.

>
> Some additional words on this part of the patch. I think (and this is my
> personal view) we should not expand legacy interfaces at all, instead we
> should try to remove them sooner rather than later. Additionally I think
> (again my personal view) it is not your responsibility to clean this up
> _now_ because you touch this file. In my opinion it is ok to just add
> the new interface and leave the old one as is.
>
> Maybe someone else (Albert?) can comment on this?
>
> best regards
>
> Andreas Bie?mann

      reply	other threads:[~2012-05-21  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  2:16 [U-Boot] [PATCH v2] ATMEL/PIO: Enable new feature of PIO on Atmel device Bo Shen
2012-05-16 10:42 ` Andreas Bießmann
2012-05-17  1:19   ` Bo Shen
2012-05-18 11:01     ` Andreas Bießmann
2012-05-21  5:59       ` Bo Shen [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=4FB9D9D0.3010406@atmel.com \
    --to=voice.shen@atmel.com \
    --cc=u-boot@lists.denx.de \
    /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