From: "Gundlupet Raju, Sandeep" <sandeep.gundlupet-raju@amd.com>
To: Steve Sakoman <steve@sakoman.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org, "Hatle,
Mark" <mark.hatle@amd.com>
Subject: Re: [OE-core] [PATCH 1/2] wic: engine.py: use raw string for escape sequence
Date: Tue, 9 Jul 2024 09:21:54 -0600 [thread overview]
Message-ID: <400f91a5-e614-4970-a409-cf4e32f89429@amd.com> (raw)
In-Reply-To: <CAOSpxdbEBs7ZT1M-ainOu7CnEOh5T6+_db-SN+FUqX7_xpdRVQ@mail.gmail.com>
On 7/9/2024 7:12 AM, Steve Sakoman wrote:
> On Mon, Jul 8, 2024 at 2:32 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Mon, 2024-07-08 at 11:56 -0600, Gundlupet Raju, Sandeep wrote:
>>> Hi RP,
>>>
>>> We do see this issue in scarthgap, Can you get this patch backported
>>> to
>>> scarthgap branch?
>>>
>>> Thanks,
>>>
>>> Sandeep
>>>
>>> On 6/4/2024 2:06 AM, Enrico Jörns via lists.openembedded.org wrote:
>>>> Fixes:
>>>>
>>>>> poky/scripts/lib/wic/engine.py:362: SyntaxWarning: invalid escape
>>>>> sequence '\/'
>>>> Signed-off-by: Enrico Jörns <ejo@pengutronix.de>
>>>> ---
>>
>> You need to talk to the stable maintainer for scarthgap, Steve Sakoman
>> (copied on this reply) about that rather than me.
> I've got it, thanks!
Thanks RP and Steve. Steve when this will be available in scarthgap branch?
>
> Steve
next prev parent reply other threads:[~2024-07-09 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 8:06 [PATCH 1/2] wic: engine.py: use raw string for escape sequence Enrico Jörns
2024-06-04 8:06 ` [PATCH 2/2] wic: bootimg-efi: fix error handling Enrico Jörns
2024-07-08 17:56 ` [OE-core] [PATCH 1/2] wic: engine.py: use raw string for escape sequence Gundlupet Raju, Sandeep
2024-07-08 21:32 ` Richard Purdie
2024-07-09 13:12 ` Steve Sakoman
2024-07-09 15:21 ` Gundlupet Raju, Sandeep [this message]
2024-07-09 15:41 ` Steve Sakoman
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=400f91a5-e614-4970-a409-cf4e32f89429@amd.com \
--to=sandeep.gundlupet-raju@amd.com \
--cc=mark.hatle@amd.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