All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
	Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>,
	RT-users <linux-rt-users@vger.kernel.org>
Subject: [PATCH 0/1] Re: [PATCH RT] latency-hist: mostly checkpatch cleanup
Date: Fri, 14 Feb 2014 18:16:41 +0100	[thread overview]
Message-ID: <20140214171641.048899133@osadl.org> (raw)

Hi Sebastian,

you submitted a patch of a patch - it's not funny and very difficult to read.
I allowed myself to transform it to a normal separate patch on top of the one
that you patched. It can be merged lateron.

Isn't this better? (We always did it this way.)

	-Carsten.


             reply	other threads:[~2014-02-14 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 17:16 Carsten Emde [this message]
2014-02-14 17:16 ` [PATCH 1/1] From: Nicholas Mc Guire <der.herr@hofr.at> Carsten Emde
2014-02-14 19:46 ` [PATCH 0/1] Re: [PATCH RT] latency-hist: mostly checkpatch cleanup Sebastian Andrzej Siewior
2014-02-14 20:33   ` Carsten Emde

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=20140214171641.048899133@osadl.org \
    --to=c.emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=der.herr@hofr.at \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.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.