Linux backports project
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>, <backports@vger.kernel.org>
Subject: Re: [PATCH V2] backports: lib: remove raising ExecutionError exception
Date: Fri, 2 May 2014 10:08:40 +0200	[thread overview]
Message-ID: <53635288.1090701@broadcom.com> (raw)
In-Reply-To: <20140502010615.GC957@garbanzo.do-not-panic.com>

On 05/02/14 03:06, Luis R. Rodriguez wrote:
> On Tue, Apr 29, 2014 at 11:58:18AM +0200, Arend van Spriel wrote:
>> In spatch a ExecutionError was raised, but that causes the thread
>> to finish without closing the outfile and more importantly without
>> putting (ret, fn) tuple on the return queue. This results in the
>> threaded_spatch routine to get stuck on the ret_q.get() call. This
>> patch removes raising the ExecutionError and just return the tuple.
>> The non-zero return code will result in ExecutionErrorThread exception
>> anyway.
>>
>> Signed-off-by: Arend van Spriel<arend@broadcom.com>
>> ---
>> A bit late but here is the rebased version.
>
> Thanks! Perhaps you're on an outdated tree, the latest tree is:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git

Definitely barking up the wrong tree ;-)

$ git remote show origin
* remote origin
   Fetch URL: 
git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/backports.git

> I rebased your patch to fit on top of that though so no need to send
> another patch, thanks a lot!

Gr. AvS

      reply	other threads:[~2014-05-02  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 10:44 [PATCH] backports: lib: remove raising ExecutionError exception Arend van Spriel
2014-04-26 17:20 ` Luis R. Rodriguez
2014-04-29  9:58 ` [PATCH V2] " Arend van Spriel
2014-05-02  1:06   ` Luis R. Rodriguez
2014-05-02  8:08     ` Arend van Spriel [this message]

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=53635288.1090701@broadcom.com \
    --to=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@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