public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Dan Murphy" <dmurphy@ti.com>
To: Steve Sakoman <steve@sakoman.com>
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [RFC]Backport of a patch from master to dunfell
Date: Fri, 4 Dec 2020 16:19:05 -0600	[thread overview]
Message-ID: <e75ef924-e626-1f7c-790a-a02a8179e432@ti.com> (raw)
In-Reply-To: <CAOSpxdZFBi_3aOMUkzGR3juc_xfNb1EeMV6-oXmvEV2LEkw1JQ@mail.gmail.com>

Steve

Awesome thanks!

The 3 patches will fix our issues

Dan

On 12/4/20 4:18 PM, Steve Sakoman wrote:
> I sent a pull request yesterday for a series that includes this patch.
>
> Richard will probably merge it to dunfell in the next day or two.
>
> Steve
>
> On Fri, Dec 4, 2020 at 11:30 AM Dan Murphy via lists.openembedded.org
> <dmurphy=ti.com@lists.openembedded.org> wrote:
>> Hello
>>
>> How do we get this patch below backported to dunfell?
>>
>> https://git.openembedded.org/openembedded-core/commit/meta/classes/kernel.bbclass?h=gatesgarth&id=d9e327063f63193186822d958706081d64ec8139
>>
>> We at TI are seeing similar issues with Dunfell and cryptodev modules on
>> 5.10 builds.
>>
>> Dan
>>
>>
>>
>> 
>>

      reply	other threads:[~2020-12-04 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 21:29 [RFC]Backport of a patch from master to dunfell Dan Murphy
2020-12-04 21:35 ` [OE-core] " Konrad Weihmann
2020-12-04 21:58   ` Dan Murphy
2020-12-04 22:18 ` Steve Sakoman
2020-12-04 22:19   ` Dan Murphy [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=e75ef924-e626-1f7c-790a-a02a8179e432@ti.com \
    --to=dmurphy@ti.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=steve@sakoman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox