mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] misc improvements
Date: Sun,  7 Oct 2012 13:39:46 +0200	[thread overview]
Message-ID: <1349609991-26567-1-git-send-email-s.hauer@pengutronix.de> (raw)

Some things that should have been changed earlier: Print error messages
when a driver probe or a initcall fails. Also some cleanups in the console
activation area.

Sascha

----------------------------------------------------------------
Sascha Hauer (5):
      driver: print error message when probe fails
      resource: statically initialize iomem resource
      console: Cleanup console activation
      console: cleanup Kconfig
      startup: Print error message when initcall fails

 common/Kconfig        |   35 ++++++++++++++++++++++++---------
 common/console.c      |   51 +++++++++++++++++++++++++------------------------
 common/resource.c     |   10 ++--------
 common/startup.c      |    4 +++-
 drivers/base/driver.c |    7 ++++++-
 5 files changed, 63 insertions(+), 44 deletions(-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-10-07 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 11:39 Sascha Hauer [this message]
2012-10-07 11:39 ` [PATCH 1/5] driver: print error message when probe fails Sascha Hauer
2012-10-07 11:39 ` [PATCH 2/5] resource: statically initialize iomem resource Sascha Hauer
2012-10-07 11:39 ` [PATCH 3/5] console: Cleanup console activation Sascha Hauer
2012-10-07 11:39 ` [PATCH 4/5] console: cleanup Kconfig Sascha Hauer
2012-10-07 11:39 ` [PATCH 5/5] startup: Print error message when initcall fails Sascha Hauer

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=1349609991-26567-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox