All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Rename reset to sysreset
Date: Thu, 12 May 2016 16:15:56 -0600	[thread overview]
Message-ID: <5735009C.8010104@wwwdotorg.org> (raw)
In-Reply-To: <20160512204718.2107A100879@atlas.denx.de>

On 05/12/2016 02:47 PM, Wolfgang Denk wrote:
> Dear Stephen,
>
> In message <1463076215-27228-1-git-send-email-swarren@wwwdotorg.org> you wrote:
>>
>> The current reset API implements a method to reset the entire system.
>> In the near future, I'd like to introduce code that implements the device
>> tree reset bindings; i.e. the equivalent of the Linux kernel's reset API.
>> This controls resets to individual HW blocks or external chips with reset
>> signals. It doesn't make sense to merge the two APIs into one since they
>> have different semantic purposes. Resolve the naming conflict by renaming
>> the existing reset API to sysreset instead, so the new reset API can be
>> called just reset.
>
> What about the "reset" command?  This cannot be easily renamed (not
> without breaking backward compatibility).  Do you feel this is an
> issue, or can we just ignore that here?

As you say, it's best not to change the cmdline syntax to avoid 
compatibility issues. I think we can ignore this; in the context of a 
bootloader command-line, I'd expect "reset" to do a system reset, and 
any debug commands related to any new reset subsystem (if there end up 
being any) to get some other name that's a bit less of a "land grab" for 
a common name.

  reply	other threads:[~2016-05-12 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 18:03 [U-Boot] [PATCH] Rename reset to sysreset Stephen Warren
2016-05-12 20:47 ` Wolfgang Denk
2016-05-12 22:15   ` Stephen Warren [this message]
2016-05-14 21:23 ` Simon Glass
2016-05-23 15:39   ` Simon Glass

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=5735009C.8010104@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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 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.