All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Siegumfeldt <mns@gomspace.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: URL of devmem2
Date: Wed, 31 May 2017 19:15:22 +0000	[thread overview]
Message-ID: <AM5PR0402MB2769B4C2EB8E2882A248DD34C4F10@AM5PR0402MB2769.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1496243833.26945.66.camel@linux.intel.com>

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Sent: Wednesday, May 31, 2017 17:17
To: Martin Siegumfeldt
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] URL of devmem2
    
On Tue, 2017-05-30 at 20:10 +0000, Martin Siegumfeldt wrote:
> Hi,
> 
> 
> Is there any chance that  http://git.openembedded.org/meta-openembedded/commit/?id=fc801961457fe2fbb24973bb43b302ad46044cb8 and  http://git.openembedded.org/meta-openembedded/commit/?id=6c584374a599f6f8d3607f20ecfc13a67ccf1da1 will be backported to release branches? lartmaker domain seems no longer available - AFAICS all branches older than pyro is affected.
> 

without much contexts on these two patches, send the backported patches
with proper stable releases names as prefixes to the mailing list.

Thanks Leonardo, assuming https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded still applies I will try it out - cheers...


> 
> Thanks,
> 
> Martin


    

  parent reply	other threads:[~2017-05-31 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 20:10 URL of devmem2 Martin Siegumfeldt
2017-05-31 15:17 ` Leonardo Sandoval
2017-05-31 16:15   ` Greg Hwang
2017-06-05 12:48     ` Martin Jansa
2017-05-31 19:15   ` Martin Siegumfeldt [this message]
2017-05-31 23:05     ` Andre McCurdy
2017-06-01  7:50     ` Martin Siegumfeldt
2017-06-01 10:59     ` Martin Siegumfeldt
2017-05-31 11:29 Martin Siegumfeldt

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=AM5PR0402MB2769B4C2EB8E2882A248DD34C4F10@AM5PR0402MB2769.eurprd04.prod.outlook.com \
    --to=mns@gomspace.com \
    --cc=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-devel@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 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.