Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@aperture.us>
Cc: buildroot@buildroot.org,
	 Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [RFC PATCH v1 1/1] package/rtl8821cu: bump to version 2026-08-21
Date: Thu, 17 Sep 2026 09:17:18 +0200	[thread overview]
Message-ID: <aquTkXp-nFwMQPpZ@windsurf> (raw)
In-Reply-To: <CA+h8R2pMha93DcRCsknH4qJ+wL1RCgAqJF8g8=dFWVBz9gvLTg@mail.gmail.com>

Hello,

On Wed, Sep 16, 2026 at 08:26:52PM -0700, Christian Stewart wrote:

> I sent with git send-email but using the Gmail API - which apparently
> still is forcing line-wrapping at 78 chars.
> 
> Will go back to sending with SMTP.
> 
> Was trying to use the API because the SMTP messages are marked with a
> red "dangerous" signal in Gmail and marked as inauthentic.
> 
> Is there some way to send patches via gmail that doesn't have these limitations?

On my side I'm not using Gmail, so unfortunately I cannot provide any
guidance on this specific topic. But I assume a number of other people
on this mailing list are using Gmail?

> And the RFC - oops, I just had the --rfc flag on for some reason.

No worries :-)

> Hmm, I guess yes, I think mentally I mixed this up with
> https://github.com/aircrack-ng/rtl8812AU

Easy to mix up all those out of tree realtek driver repos to be
honest. I wish there was a bit more consolidation, with people
submitting those drivers for integration in the upstream kernel, even
if they go in drivers/staging/ initially.

> which has a "THESE DRIVERS IS DEPRECATED." notice and aren't merging PRs
> 
> But - the morrownr one - I suppose is still maintained and would accept the PR.
> 
> Submitted: https://github.com/morrownr/8821cu-20210916/pull/213

Thx! I assume you will send a v2 of your patch? Or maybe even it's
already done (I haven't checked patchwork).

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:[~2026-09-17  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 23:26 [Buildroot] [RFC PATCH v1 1/1] package/rtl8821cu: bump to version 2026-08-21 Christian Stewart via buildroot
2026-09-16 21:05 ` Thomas Petazzoni via buildroot
2026-09-17  3:26   ` Christian Stewart via buildroot
2026-09-17  7:17     ` 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=aquTkXp-nFwMQPpZ@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=thomas.petazzoni@bootlin.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