From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Stefan Agner <stefan.agner@toradex.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] busybox: udhcpc: fix IPv6 support when using udhcpc
Date: Tue, 16 Jun 2020 11:50:48 +0200 [thread overview]
Message-ID: <20200616095048.im6minhd7qsjc65d@qschulz> (raw)
In-Reply-To: <20200122100655.eenl3tcnhj4kkcda@qschulz>
Hi all,
On Wed, Jan 22, 2020 at 11:06:55AM +0100, Quentin Schulz wrote:
> > > The reason why I didn't bother to send a patch to busybox before pinging
> > > on this patch was that we're already different from the upstream simple.script
> > > so it didn't make sense to me to add the Upstream-Status: pending or
> > > something on the patch (in some ways, since it's patching the file
> > > directly and not adding a patch in SRC_URI). Anyway, digressing. Do you
> > > want a patch to be sent to busybox ML (or PR or whatever they use)
> > > before taking this patch?
> > >
> >
> > I think the problem this patch fixes is generic and somewhere the
> > script OE has is also derived from
> > that example, so while the patch in itself is enough for OE, it would
> > be better if it was in upstream too
> > perhaps one less thing to worry about when we cherry pick changes from
> > upstream script in future.
> >
>
> Agreed, I'll put it on my TODO-list. If I do not send an answer on this
> mail with the link to the PR or patch in the next week, anyone, please ping me.
>
*cough* Took a bit more *cough* than a week *cough*
http://lists.busybox.net/pipermail/busybox/2020-June/088028.html
Quentin
next prev parent reply other threads:[~2020-06-16 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:44 [PATCH] busybox: udhcpc: fix IPv6 support when using udhcpc Stefan Agner
2019-06-24 12:24 ` Stefan Agner
2020-01-13 14:57 ` Quentin Schulz
2020-01-20 12:32 ` Quentin Schulz
2020-01-20 12:57 ` Stefan Agner
2020-01-20 19:26 ` Khem Raj
2020-01-21 9:23 ` Quentin Schulz
2020-01-21 18:08 ` Khem Raj
2020-01-22 10:06 ` Quentin Schulz
2020-06-16 9:50 ` Quentin Schulz [this message]
2020-06-17 9:12 ` [OE-core] " Stefan Agner
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=20200616095048.im6minhd7qsjc65d@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=stefan.agner@toradex.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