mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Brown <broonie@kernel.org>,
	kernel@pengutronix.de, Pankaj Dubey <pankaj.dubey@samsung.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] regmap: Move tracing header into drivers/base/regmap
Date: Fri, 20 Mar 2015 08:31:40 +0100	[thread overview]
Message-ID: <20150320073140.GC10068@pengutronix.de> (raw)
In-Reply-To: <20150319183203.584f940a@grimm.local.home>

Hey Steven,

On Thu, Mar 19, 2015 at 06:32:03PM -0400, Steven Rostedt wrote:
> On Thu, 19 Mar 2015 22:23:23 +0000
> Mark Brown <broonie@kernel.org> wrote:
> 
> > On Thu, Mar 19, 2015 at 05:50:47PM -0400, Steven Rostedt wrote:
> > > The tracing events for regmap are confined to the regmap subsystem. It
> > > also requires accessing an internal header. Instead of including the
> > > internal header from a generic file location, move the tracing file
> > > into the regmap directory.
> > 
> > Applied, thanks.  Please use git format-patch -m for files that are
> > being moved.
I thought it's -M not -m?!

> OK, will do next time. This time, as it was only a single patch, I just
> added everything to git with "git add" and then did a:
> 
> git diff HEAD > t.patch
git diff knows about -M, too :-)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-03-20  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 21:50 Steven Rostedt
2015-03-19 22:23 ` Mark Brown
2015-03-19 22:32   ` Steven Rostedt
2015-03-20  7:31     ` Uwe Kleine-König [this message]
2015-03-20 13:43       ` Mark Brown

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=20150320073140.GC10068@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pankaj.dubey@samsung.com \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®