All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: kernel@pengutronix.de, linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line
Date: Tue, 30 Jul 2013 07:51:09 -0700	[thread overview]
Message-ID: <20130730145109.GA29971@kroah.com> (raw)
In-Reply-To: <20130730143739.GV1754@pengutronix.de>

On Tue, Jul 30, 2013 at 04:37:39PM +0200, Uwe Kleine-König wrote:
> Hi Greg,
> 
> On Tue, Jul 30, 2013 at 07:02:50AM -0700, Greg Kroah-Hartman wrote:
> > On Tue, Jul 30, 2013 at 10:34:41AM +0200, Uwe Kleine-König wrote:
> > > On Tue, Jul 30, 2013 at 10:23:12AM +0200, Uwe Kleine-König wrote:
> > > > pdev->id is not a valid choice for device-tree probed devices. So use
> > > > the (properly determined) line from efm32_uart_probe consistenly
> > > > 
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > Forwarded: id:1374043721-30677-1-git-send-email-u.kleine-koenig@pengutronix.de
> > > I forgot to drop these lines that I use for tracking which patches were
> > > sent for inclusion into mainline. I don't care much, but you might want
> > > to drop them.
> > 
> > Please resend so I don't have to hand-edit the messages.  I handle
> > thousands of patches a month, hand-editing is a pain and slows me
> > down...
> ok, just resent to you only after doing
> 
> 	git filter-branch -f --msg-filter 'grep -v "^Forwarded:"' next/master..
> 
> (Maybe this is even easier than replying about your pain? No offense
> intended, just wondering.)

Easier for you, yes :)

But I don't see how that would help me out when applying patches in a
mbox format to a git tree, do you?  What am I missing?

Having to craft a custom grep -v pattern for every message would be a
pain, as people do lots of silly things in patches that need to be
edited out at times...

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-07-30 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 19:55 [PATCH] serial/efm32-uart: don't slur over failure in probe_dt Uwe Kleine-König
2013-07-26 23:06 ` Greg Kroah-Hartman
2013-07-30  8:21   ` Uwe Kleine-König
2013-07-30  8:23     ` [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line Uwe Kleine-König
2013-07-30  8:34       ` Uwe Kleine-König
2013-07-30 14:02         ` Greg Kroah-Hartman
2013-07-30 14:37           ` Uwe Kleine-König
2013-07-30 14:51             ` Greg Kroah-Hartman [this message]
2013-07-30  8:23     ` [PATCH 2/2] serial/efm32-uart: don't slur over failure in probe_dt Uwe Kleine-König
  -- strict thread matches above, loose matches on Subject: below --
2013-07-17  6:48 [PATCH 1/2] serial/efm32-uart: don't use pdev->id to determine the port's line Uwe Kleine-König
2013-07-26 23:05 ` Greg Kroah-Hartman

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=20130730145109.GA29971@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-serial@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.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.