All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Quentin Schulz <foss+yocto@0leil.net>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: Re: [yocto] [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11
Date: Mon, 13 Dec 2021 17:30:05 -0500	[thread overview]
Message-ID: <20211213223005.GA36849@localhost> (raw)
In-Reply-To: <CAMKF1sorO4VR2GaN0gn2rS5-Lti_rXGy=9GsQWCgEAgN5gO9nQ@mail.gmail.com>

Hi Quentin/Khem,

On Mon 2021-12-13 @ 09:35:53 AM, Khem Raj wrote:
> On Mon, Dec 13, 2021 at 9:18 AM Quentin Schulz <foss+yocto@0leil.net> wrote:
> >
> > Hi Khem,
> >
> > On December 13, 2021 4:04:03 PM GMT+01:00, Khem Raj <raj.khem@gmail.com> wrote:
> > >On Mon, Dec 13, 2021 at 1:00 AM Quentin Schulz <
> > >quentin.schulz@theobroma-systems.com> wrote:
> > >
> > >> Hi Trevor,
> > >>
> > >> Gentle ping :)
> > >>
> > >> Honister 3.4.1 being out it's less of an issue but the question remains
> > >> at least for settling on a policy :)

I apologize for not reviewing this patch in a timely manner; I'm sorry for the
frustration it caused.

Would this have been solved by (me) creating a honister  branch? I usually
don't create a release branch until openembedded-core moves, but this looks
like it was a case where master and the latest branch diverged?

If so, would that still be useful?

Best regards,
	Trevor


      reply	other threads:[~2021-12-13 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211116153256.3639663-1-quentin.schulz@theobroma-systems.com>
2021-11-16 17:00 ` [yocto] [meta-rockchip][PATCH] kernel: linux-yocto: fix broken Ethernet MAC controller on RK3399 on 5.14 >= version <= 5.14.11 Khem Raj
     [not found]   ` <20211116170406.abau3j6liwsdonbp@fedora>
2021-11-16 17:08     ` Khem Raj
     [not found]       ` <20211116171242.7dyycd3d2qwb4ske@fedora>
2021-11-16 17:45         ` Khem Raj
2021-11-16 18:03           ` Quentin Schulz
2021-11-16 18:50             ` Khem Raj
     [not found]               ` <20211213090032.dy47s56sykoikbfc@fedora>
2021-12-13 15:04                 ` Khem Raj
2021-12-13 17:18                   ` Quentin Schulz
2021-12-13 17:35                     ` Khem Raj
2021-12-13 22:30                       ` Trevor Woerner [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=20211213223005.GA36849@localhost \
    --to=twoerner@gmail.com \
    --cc=foss+yocto@0leil.net \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=raj.khem@gmail.com \
    --cc=yocto@lists.yoctoproject.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.