All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek <marek.bykowski@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe] [PATCHv3] lmbench: Fix/clean-up the build for lmbench
Date: Thu, 19 Dec 2019 13:34:16 +0100	[thread overview]
Message-ID: <CAHw2UgAUh82RGjtbCk05xDpeETD8m74mvMQCeMdcMJHGTUcAGg@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1srcG7HP18wyYMK8Sn4uLbzyr+ePTGCLUZXvyecVj6nBoQ@mail.gmail.com>

I don't think Intel is interested in the pull request (
https://github.com/intel/lmbench/pull/9). With that are you still planning
on taking the change in?

Thanks,
Marek

On Fri, 8 Nov 2019 at 18:13, Khem Raj <raj.khem@gmail.com> wrote:

> Hi Marek
>
> I thought there are some feedbacks to be addressed, so I was hoping to get
> a v3
>
> On Fri, Nov 8, 2019 at 5:24 AM Marek <marek.bykowski@gmail.com> wrote:
> >
> > Any thoughts if this is going to be included in the upstream?
> > Thanks,
> > Marek
> >
> > On Tue, 22 Oct 2019 at 12:03, marek.bykowski@gmail.com
> > <marek.bykowski@gmail.com> wrote:
> > >
> > > On Tue, 22 Oct 2019 09:15:23 +0200
> > > "marek.bykowski@gmail.com" <marek.bykowski@gmail.com> wrote:
> > >
> > > > On Mon, 21 Oct 2019 19:42:45 -0400
> > > > Randy MacLeod <randy.macleod@windriver.com> wrote:
> > > >
> > > > > We have had Intel employees working on oe-core / meta-openembedded
> > > > > for years so I hope that you will send the commit to that repo on
> > > > > github and indicate the
> > > > > upstream-status in the patch what we integrate into meta-oe.
> > > >
> > > > Hi Randy,
> > > >
> > > > I'm Intel (actually a subcontractor to them) working on occasion with
> > > > Daniel Drogomir, Charlie Paul, and Chantale Ouimet from Windriver. I
> > > > have put the names as chances they may be your colleagues. Even
> > > > though I'm Intel I didn't know of lmbench Intel repo on github - this
> > > > must a totally different team. Sure I'll send the patch onto that
> > > > repo indicating these are the changes integration planned into
> > > > meta-oe.
> > > >
> > > > Regards,
> > > > Marek
> > >
> > > Done https://github.com/intel/lmbench/pull/9
> >
> >
> >
> > --
> > Slán,
> > Marek
>


-- 
Slán,
Marek


  reply	other threads:[~2019-12-19 12:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 12:13 [meta-oe] [PATCH] lmbench: fix/clean-up the build for lmbench marek.bykowski
2019-10-16 10:45 ` Adrian Bunk
2019-10-16 12:21   ` [meta-oe] [PATCHv2] lmbench: Fix/clean-up " Marek Bykowski
2019-10-17 12:53     ` Khem Raj
2019-10-17 14:10       ` marek.bykowski
2019-10-18 11:42       ` [meta-oe] [PATCHv3] " marek.bykowski
2019-10-18 19:49         ` Randy MacLeod
2019-10-21  9:30           ` marek.bykowski
2019-10-21 23:42             ` Randy MacLeod
2019-10-22  7:15               ` marek.bykowski
2019-10-22 10:03                 ` marek.bykowski
2019-11-08 13:24                   ` Marek
2019-11-08 17:13                     ` Khem Raj
2019-12-19 12:34                       ` Marek [this message]
2020-02-11 14:41                         ` Marek
2020-02-11 16:31                           ` Khem Raj

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=CAHw2UgAUh82RGjtbCk05xDpeETD8m74mvMQCeMdcMJHGTUcAGg@mail.gmail.com \
    --to=marek.bykowski@gmail.com \
    --cc=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.