All of lore.kernel.org
 help / color / mirror / Atom feed
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/mxc: add the missing UART_PADDR for i.mx53
Date: Wed, 20 Jul 2011 22:44:53 +0200	[thread overview]
Message-ID: <20110720204453.GA5007@pengutronix.de> (raw)
In-Reply-To: <20110720135921.GE6999@S2100-06.ap.freescale.net>

On Wed, Jul 20, 2011 at 09:59:22PM +0800, Shawn Guo wrote:
> On Wed, Jul 20, 2011 at 03:45:30PM +0200, Wolfram Sang wrote:
> > On Wed, Jul 20, 2011 at 09:44:27PM +0800, Shawn Guo wrote:
> > > On Wed, Jul 20, 2011 at 03:27:20PM +0200, Wolfram Sang wrote:
> > > > > > Then you should at least add his Signed-off. And maybe also mark him as
> > > > > > the author of the patch?
> > > > > > 
> > > > > I did exactly what you suggested here on a mx53 fec patch, but I was
> > > > > told by Troy to change his s-o-b to reported-by.  So let's see what
> > > > > he would say about this one.
> > > > 
> > > > Okay, not much of a deal for such a patch. Though, I have doubts if one
> > > > can request removing the SoB for a patch other people put work on top
> > > > of.
> > > > 
> > > So you are telling you are not following the list closely?
> > 
> > If "following closely" == "reading every single mail", then surely not.
> > Why?
> > 
> Well, not really.  But since you are co-maintaining i.mx, I *thought*
> you may have read the mail with "i.mx" in the subject.  It seems not
> the case, apparently.

? I don't get the relevance to the topic, sorry.

If the new patch is different enough to be considered new, Troy could indeed
request his SoB to be removed. If his patch is mainly improved, I do still
wonder if he could request his SoB to be removed. That is possibly a gray area,
but as I said before, it really doesn't matter for this patch and is not worth
the fuzz here. Let's just go back to hacking :)

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110720/063da325/attachment.sig>

  reply	other threads:[~2011-07-20 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 22:51 [PATCH 1/1] ARM: i.MX50/53: debug-macro: fix UART_PADDR Troy Kisky
2011-07-11  9:06 ` Amit Kucheria
2011-07-11  9:30   ` Uwe Kleine-König
2011-07-11 10:08     ` Amit Kucheria
2011-07-11 13:58       ` Uwe Kleine-König
2011-07-12 13:32 ` Sascha Hauer
2011-07-12 17:04   ` Troy Kisky
2011-07-15  7:56     ` Sascha Hauer
2011-07-20 13:13 ` [PATCH] arm/mxc: add the missing UART_PADDR for i.mx53 Shawn Guo
2011-07-20 13:08   ` Wolfram Sang
2011-07-20 13:24     ` Shawn Guo
2011-07-20 13:27       ` Wolfram Sang
2011-07-20 13:44         ` Shawn Guo
2011-07-20 13:45           ` Wolfram Sang
2011-07-20 13:59             ` Shawn Guo
2011-07-20 20:44               ` Wolfram Sang [this message]
2011-07-20 20:13             ` Troy Kisky
2011-07-20 23:13               ` Shawn Guo
2011-07-20 13:40     ` Shawn Guo
2011-07-20 21:10   ` Troy Kisky
2011-07-20 23:16     ` Shawn Guo
2011-07-21  0:31       ` Troy Kisky

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=20110720204453.GA5007@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --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.