From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Robertson <gary.robertson@linaro.org>
Cc: Mike Holmes <mike.holmes@linaro.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rt-tests: bump version 0.87 => 0.89
Date: Thu, 08 May 2014 23:09:40 +0100 [thread overview]
Message-ID: <1399586980.31891.79.camel@ted> (raw)
In-Reply-To: <CAF7YWnzBffap=rUnEAVhJ1B6x4-v7rvv9LR+mxK6i_tw=Gqbyg@mail.gmail.com>
On Thu, 2014-05-08 at 16:24 -0500, Gary Robertson wrote:
> I am regrettably new at patch submissions within the Linux / Open
> Source community, so please forgive my breach of etiquette if I abuse
> the balance between persistence and peskiness.
>
> I submitted the first version of this recipe patch on 18 APR and
> received prompt suggestions for improvement.
> However since amending the patch to incorporate those improvements and
> re-submitting the patch on 24 APR, I have heard no further comments or
> responses.
>
> So I am pinging the list once more to check the status of the patch.
> Please let me know if additional work must be done to make the patch
> acceptable.
>
> (BTW, I authored the patch to cyclictest and Anders Roxell authored
> the patch to update the recipe with the new version of the rt-tests.
> I subsequently submitted the recipe patch on his behalf... that is why
> his name appears as author of the patch itself.)
We have tried this in some of the test builds. My memory says something
failed and we hence didn't merge it but I'm not remembering which
version of the series that was, or what the failure was. Saul may
remember.
We do try and reply to the patches where we identify failures with
pointers to the logs but this one has probably fallen through the
cracks, sorry.
If we can't remember we'll try it in master-next or mut and see if we
can remember what the issue was...
Cheers,
Richard
next prev parent reply other threads:[~2014-05-08 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 20:12 [PATCH] rt-tests: bump version 0.87 => 0.89 gary.robertson
2014-04-18 20:12 ` gary.robertson
2014-04-18 20:15 ` Khem Raj
2014-04-18 20:17 ` Saul Wold
2014-04-23 16:59 ` [PATCH V2 1/1] " gary.robertson
2014-04-23 16:59 ` [PATCH] " gary.robertson
2014-05-08 21:24 ` Gary Robertson
2014-05-08 22:09 ` Richard Purdie [this message]
2014-05-11 17:05 ` Richard Purdie
2014-04-24 22:09 ` [PATCH V3 0/1] " gary.robertson
2014-04-24 22:09 ` [PATCH V3 1/1] " gary.robertson
2014-05-09 21:59 ` Saul Wold
2014-05-14 4:08 ` Saul Wold
2014-05-14 13:04 ` Gary Robertson
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=1399586980.31891.79.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary.robertson@linaro.org \
--cc=mike.holmes@linaro.org \
--cc=openembedded-core@lists.openembedded.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