From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Cc: "netdev\@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v6] net: sched: Introduce act_ctinfo action
Date: Tue, 28 May 2019 21:38:46 +0200 [thread overview]
Message-ID: <87blzmtlmh.fsf@toke.dk> (raw)
In-Reply-To: <70B35849-D2D4-4B4E-8D3E-8AF089B0947F@darbyshire-bryant.me.uk>
Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> writes:
>> On 28 May 2019, at 19:08, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>>
> <stuff snipped>
>>
>> Thank you for doing another iteration!
>>
>> No further comments on the actual code, but I still get the whitespace
>> issue with the patch... And now it results in stray ^M characters in the
>> Kconfig file, which makes the build blow up :/
>
> This is very odd. I produced the last patch (v6) from within a debian VM
> and sent it from there also. No weird line endings in the locally produced
> patch text and it applied cleanly to a local tree. I’ve sent test patches
> into the openwrt tree and applied those cleanly direct from patchwork.
>
> Similarly I’ve downloaded the v5 patch from netdev patchwork
> http://patchwork.ozlabs.org/patch/1105755/mbox/ and applied that with
> git am without problem.
>
> Am totally confused!
Hmm, yeah, that is odd. Guess it may be mangled somewhere in transit on
the way to my system? I'll try to investigate that...
Anyway, if I download the patch from patchwork and apply it manually
things seems to work, so I guess you can ignore this for now. I'm sure
Davem will let you know if he has problems applying the patch :)
-Toke
next prev parent reply other threads:[~2019-05-28 19:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 17:03 [PATCH net-next v6] net: sched: Introduce act_ctinfo action Kevin 'ldir' Darbyshire-Bryant
2019-05-28 18:08 ` Toke Høiland-Jørgensen
2019-05-28 18:52 ` Kevin 'ldir' Darbyshire-Bryant
2019-05-28 19:38 ` Toke Høiland-Jørgensen [this message]
2019-05-28 22:06 ` Cong Wang
2019-05-30 4:44 ` David Miller
2019-05-30 12:01 ` Kevin 'ldir' Darbyshire-Bryant
2019-06-12 18:02 ` Marcelo Ricardo Leitner
2019-06-12 18:46 ` Jakub Kicinski
2019-06-12 18:52 ` Marcelo Ricardo Leitner
2019-06-12 18:56 ` Johannes Berg
2019-06-12 19:18 ` Michal Kubecek
2019-06-12 21:34 ` Jakub Kicinski
2019-06-13 20:12 ` Marcelo Ricardo Leitner
2019-06-13 11:18 ` [RFC PATCH net-next] sched: act_ctinfo: use extack error reporting Kevin Darbyshire-Bryant
2019-06-13 12:55 ` Marcelo Ricardo Leitner
2019-06-13 8:33 ` [PATCH net-next v6] net: sched: Introduce act_ctinfo action Simon Horman
2019-06-13 9:09 ` Kevin 'ldir' Darbyshire-Bryant
2019-06-13 10:47 ` Kevin 'ldir' Darbyshire-Bryant
2019-06-13 10:53 ` Toke Høiland-Jørgensen
2019-06-13 20:08 ` Marcelo Ricardo Leitner
2019-06-14 9:09 ` [PATCH net-next] sched: act_ctinfo: use extack error reporting Kevin Darbyshire-Bryant
2019-06-14 15:57 ` David Miller
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=87blzmtlmh.fsf@toke.dk \
--to=toke@redhat.com \
--cc=ldir@darbyshire-bryant.me.uk \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).