Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
	Christian Stewart via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/rtl8821cu: new package
Date: Sun, 11 Dec 2022 22:47:04 +0100	[thread overview]
Message-ID: <20221211224704.33be71cd@windsurf> (raw)
In-Reply-To: <CA+h8R2qPG=2ghvntT=jXAp0s+0tsZANvJUvV7F1iU7ukLkh1Ng@mail.gmail.com>

On Sun, 11 Dec 2022 12:32:59 -0800
Christian Stewart <christian@paral.in> wrote:

> The first, yes, and it's been merged:
> 
> https://github.com/morrownr/8821cu-20210118/commit/3b594e7654ef1320ff9cac6b6472fa1b17af134b
> 
> The second, no. Since removing the compiler version check for
> -Wno-date-time is not something they want, and more of a Buildroot
> thing, I think the patch probably will need to stay.
> 
> Shall I resubmit or can you fixup those two little things?

If you could resubmit, with the details of the upstream status for each
patch, and the license hash fixed, it would be great. Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-12-11 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  1:45 [Buildroot] [PATCH v2 1/1] package/rtl8821cu: new package Christian Stewart via buildroot
2022-12-11 20:25 ` Thomas Petazzoni via buildroot
2022-12-11 20:32   ` Christian Stewart via buildroot
2022-12-11 21:47     ` Thomas Petazzoni via buildroot [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=20221211224704.33be71cd@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@paral.in \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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