lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150320073140.GC10068@pengutronix.de>
Date:	Fri, 20 Mar 2015 08:31:40 +0100
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mark Brown <broonie@...nel.org>, kernel@...gutronix.de,
	Pankaj Dubey <pankaj.dubey@...sung.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Philipp Zabel <p.zabel@...gutronix.de>
Subject: Re: [PATCH] regmap: Move tracing header into drivers/base/regmap

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@...nel.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/  |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ