All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Jennejohn <garyj@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] IOMUX: Add console multiplexing support.
Date: Mon, 15 Sep 2008 10:46:47 +0200	[thread overview]
Message-ID: <20080915104647.79c73006@peedub.jennejohn.org> (raw)
In-Reply-To: <20080914183427.3502C24885@gemini.denx.de>

On Sun, 14 Sep 2008 20:34:27 +0200
Wolfgang Denk <wd@denx.de> wrote:

> In message <20080914191918.7de10c5c@peedub.jennejohn.org> you wrote:
> > 
> > > 2) You only add new points where the GD_FLG_DEVINIT bit gets set in
> > > gd->flags. That means there are two possibilities when your newly
> > > added code is run: either, this bit is already set by other parts of
> > > the codem than the operation was redundant and couldbe omitted; or,
> > > the flasg was not set yet, then you set it now, which means you set it
> > > EARLIE than it would have been set before.
> > > 
> > > But your comment suggests that that would be done LATER now.
> > > 
> > > 
> > > So what exactly is the purpose of this patch?
> > 
> > This bit is normally ser in console_init_r, which is called very early.
> > 
> > You have to look at this patch in conjunction with the first patch and
> > not as a separate entity, which it most definitely is not.
> 
> Sorry, but this doesn't work. If you split patches, you have to do it
> in an orthogoanl way, such that each patch on it's own  makes  sense.
> This  patch  doesn't  make  any  sense  as is. Maybe theree are parts
> missing that may be buried somewhere in some other patch, but  please
> do not expect that we will try to find them.
> 
> Please re-split patches such that they are independent of each  other
> (except  maybe  that one has to be applied first), and make sure that
> each patch is complete in itself.
> 

I did it this way because I didn't want to send the net custodian
an unnecessary patch.  I though that was the way patches were supposed
to be handled.  I know I've had complaints from custodians in the
past about this.

A consistent policy certainly would be nice.

---
Gary Jennejohn
*********************************************************************
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
*********************************************************************

  reply	other threads:[~2008-09-15  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 14:45 [U-Boot] [PATCH 2/2] IOMUX: Add console multiplexing support Gary Jennejohn
2008-09-14 16:07 ` Wolfgang Denk
2008-09-14 17:19   ` Gary Jennejohn
2008-09-14 18:34     ` Wolfgang Denk
2008-09-15  8:46       ` Gary Jennejohn [this message]
2008-09-15 11:08         ` Wolfgang Denk
2008-10-20 11:58 ` [U-Boot] [PATCH 2/2 V2] " Gary Jennejohn
2008-10-20 13:24   ` Wolfgang Denk
2008-10-20 13:57     ` Gary Jennejohn
2008-10-20 16:26       ` Gary Jennejohn
2008-10-20 19:43         ` Wolfgang Denk
2008-10-20 20:13           ` Ben Warren
2008-10-21  9:45             ` Gary Jennejohn
2008-10-21 10:34               ` Wolfgang Denk
2008-10-21 11:32                 ` Gary Jennejohn
2008-10-20 19:32       ` Wolfgang Denk

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=20080915104647.79c73006@peedub.jennejohn.org \
    --to=garyj@denx.de \
    --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.