linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Kacur <jkacur@redhat.com>,
	Anna-Maria Gleixner <anna-maria@glx-um.de>,
	linux-rt-users@vger.kernel.org,
	Clark Williams <williams@redhat.com>
Subject: Re: [patch 2/3] cyclictest: Convert the offset of the alignment option to microseconds
Date: Tue, 2 Jun 2015 23:17:53 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.10.1506022307210.13306@riemann> (raw)
In-Reply-To: <alpine.DEB.2.11.1506022247320.20347@nanos>



On Tue, 2 Jun 2015, Thomas Gleixner wrote:

> On Tue, 2 Jun 2015, John Kacur wrote:
> > > ===================================================================
> > > --- rt-tests.orig/src/cyclictest/cyclictest.c
> > > +++ rt-tests/src/cyclictest/cyclictest.c
> > > @@ -1289,9 +1289,9 @@ static void process_options (int argc, c
> > 
> > 
> > I fixed your patch manually, but you are doing something wrong generating 
> > it, see how the function header get's cut off above there?
> 
> No. This is entirely correct. diff cuts off the function declaration
> at some random column and it's completely irrelevant to the
> correctness of the patch. That line is merily an extra for navigation
> purpose and not at all relevant to the patch itself. 
>  
> @@ -1289,9 +1289,9 @@
> 
> would be a completly sufficient header for the hunk.
> 
> The reason why this patch did not apply is, that it is a complete
> replacement of the original patch and not a delta patch.
> 
> Anna-Maria should have sent a new series(PATCH V2) instead of patches
> which can be mistaken as delta fixes.
> 
> 
> Thanks,
> 
> 	tglx

Yeah, my guess as to why her patches are failing was wrong, but they are 
failing. Maybe it's a wordwrap problem. When I try with patch -p1 < 
annas-patch, I get this.

 patch -p1 < ~/patches/anna/align_measurement_threads.patch 
patching file src/cyclictest/cyclictest.c
Hunk #1 FAILED at 185.
patch: **** malformed patch at line 64: par->prio);

Thanks

John

  reply	other threads:[~2015-06-02 21:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 19:06 [patch 0/3] cyclictest: Various fixes and a new option anna-maria
2015-05-26 19:07 ` [patch 1/3] cyclictest: Ensure that next wakeup time is never in the past anna-maria
2015-06-02 13:06   ` John Kacur
2015-05-26 19:07 ` [patch 2/3] cyclictest: Convert the offset of the alignment option to microseconds anna-maria
2015-05-27 21:32   ` John Kacur
2015-05-30 11:01     ` Anna-Maria Gleixner
2015-06-02 13:00       ` John Kacur
2015-06-02 21:01         ` Thomas Gleixner
2015-06-02 21:17           ` John Kacur [this message]
2015-06-02 21:33             ` Thomas Gleixner
2015-06-08 13:18               ` Anna-Maria Gleixner
2015-06-08 17:31                 ` John Kacur
2015-05-26 19:07 ` [patch 3/3] cyclictest: Align measurement threads to the next full second anna-maria
2015-05-30 11:02   ` Anna-Maria Gleixner
2015-06-02 13:05     ` John Kacur
2015-06-08 13:21       ` Anna-Maria Gleixner
2015-06-08 17:32         ` John Kacur

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=alpine.LFD.2.10.1506022307210.13306@riemann \
    --to=jkacur@redhat.com \
    --cc=anna-maria@glx-um.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).