From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [dylan][PATCH 00/41] Stable branch cherry-picks (cover letter only)
Date: Wed, 22 May 2013 12:11:58 +0100 [thread overview]
Message-ID: <2443317.KenNugOWqv@helios> (raw)
In-Reply-To: <CADkTA4MMVZR7hQbr5rdATrYmQtDPAVxLK29cq2SDTECYRWkD_Q@mail.gmail.com>
On Monday 20 May 2013 16:05:15 Bruce Ashfield wrote:
> On Mon, May 20, 2013 at 1:02 PM, Paul Eggleton
>
> <paul.eggleton@linux.intel.com> wrote:
> > On Monday 20 May 2013 17:54:21 Paul Eggleton wrote:
> >> On Monday 20 May 2013 13:21:29 Otavio Salvador wrote:
> >> > On Mon, May 20, 2013 at 12:58 PM, Paul Eggleton <
> >> >
> >> > paul.eggleton@linux.intel.com> wrote:
> >> > > ...
> >> > >
> >> > > Bruce Ashfield (4):
> >> > > linux-yocto/3.4: iwlwifi, ext4, brtfs warning and -rt fixes
> >> > > kern-tools: anchor and delimit regexs
> >> > > linux-yocto/3.4: update to v3.4.43, ltsi-65311d8 and v3.4.42-rt56
> >> > > linux-yocto/3.8: udpate to v3.8.11
> >> >
> >> > Does this includes the dash kernel-tools fix?
> >>
> >> I don't think it does. Bruce is that suitable to be pulled into dylan?
> >
> > Scratch that - it is, I just missed including it.
>
> Holiday here, so a slow response. But looks like you've sorted it out now.
Right, I've added that patch onto my paule/dylan-next branch and pushed it,
and have alerted Richard as well. Thanks Otavio for pointing out this
omission.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-05-22 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 15:58 [dylan][PATCH 00/41] Stable branch cherry-picks (cover letter only) Paul Eggleton
2013-05-20 16:21 ` Otavio Salvador
2013-05-20 16:54 ` Paul Eggleton
2013-05-20 17:02 ` Paul Eggleton
2013-05-20 20:05 ` Bruce Ashfield
2013-05-22 11:11 ` Paul Eggleton [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=2443317.KenNugOWqv@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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