From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/9] minicom: upgrade 2.8 -> 2.9
Date: Mon, 19 Feb 2024 08:11:10 +0000 [thread overview]
Message-ID: <ad432017ab18b6716473771869036aaa3d34a026.camel@intel.com> (raw)
In-Reply-To: <778a5a81ba0d8a3a8fc725b69f96c5d2762a0bf9.camel@linuxfoundation.org>
On Sat, 2024-02-17 at 12:38 +0000, Richard Purdie wrote:
> On Fri, 2024-02-16 at 19:40 +0800, Anuj Mittal wrote:
> > Drop patches that have been merged upstream and available in this
> > version.
> >
> > Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
> > ---
> > ...ix-minicom-h-v-return-value-is-not-0.patch | 33 ---------------
> > ----
> > .../minicom/allow.to.disable.lockdev.patch | 30 ---------------
> > --
> > .../{minicom_2.8.bb => minicom_2.9.bb} | 7 ++--
> > 3 files changed, 2 insertions(+), 68 deletions(-)
> > delete mode 100644 meta/recipes-extended/minicom/minicom/0001-fix-
> > minicom-h-v-return-value-is-not-0.patch
> > delete mode 100644 meta/recipes-
> > extended/minicom/minicom/allow.to.disable.lockdev.patch
> > rename meta/recipes-extended/minicom/{minicom_2.8.bb =>
> > minicom_2.9.bb} (80%)
>
> I think devtool testing is using something here in oe-selftest:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/6422/steps/14/logs/stdio
>
> but haven't 100% confirmed that yet as there are multiple patches in
> master-next.
The upgrade removed "minicom" directory that had the patches so
untracked files output from git status in the test changed. I will send
a patch.
Thanks,
Anuj
next prev parent reply other threads:[~2024-02-19 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 11:40 [PATCH 1/9] enchant2: upgrade 2.6.5 -> 2.6.7 Anuj Mittal
2024-02-16 11:40 ` [PATCH 2/9] minicom: upgrade 2.8 -> 2.9 Anuj Mittal
2024-02-17 12:38 ` [OE-core] " Richard Purdie
2024-02-19 8:11 ` Mittal, Anuj [this message]
2024-02-16 11:40 ` [PATCH 3/9] libproxy: upgrade 0.5.3 -> 0.5.4 Anuj Mittal
2024-02-16 11:40 ` [PATCH 4/9] sqlite3: upgrade 3.44.2 -> 3.45.1 Anuj Mittal
2024-02-16 11:40 ` [PATCH 5/9] orc: upgrade 0.4.36 -> 0.4.37 Anuj Mittal
2024-02-16 11:40 ` [PATCH 6/9] stress-ng: upgrade 0.17.04 -> 0.17.05 Anuj Mittal
2024-02-16 11:40 ` [PATCH 7/9] swig: upgrade 4.1.1 -> 4.2.0 Anuj Mittal
2024-02-17 2:59 ` [OE-core] " Khem Raj
2024-02-18 3:01 ` Khem Raj
2024-02-19 2:50 ` Mittal, Anuj
2024-02-19 4:19 ` Khem Raj
2024-02-16 11:40 ` [PATCH 8/9] gstreamer1.0: upgrade 1.22.9 -> 1.22.10 Anuj Mittal
2024-02-16 11:40 ` [PATCH 9/9] libcap-ng: fix build with swig 4.2.0 Anuj Mittal
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=ad432017ab18b6716473771869036aaa3d34a026.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox