From: Stephan Henningsen <stephan@asklandd.dk>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] patch: linux-firmware-20221109
Date: Thu, 08 Dec 2022 22:19:14 +0100 [thread overview]
Message-ID: <2KCLMR.A41GGA1OVAND1@asklandd.dk> (raw)
In-Reply-To: <CAGm1_kvZRbdiG_cN0q+j2uotkH1JiQ7G0_8jh5DOMRGFzWE-Bw@mail.gmail.com>
Hi,
Thanks for your reply!
Good suggestion. I've split the patch in two and sent them separately
as they're technically unrelated.
I've tried but I can't figure out how to use git send-email.
But I did send the e-mail as plain text this time, so I hope it works
for you this time.
--
hhjj,
Stephan
On ons, dec 7 2022 at 13:56:06 +01:00:00, Yegor Yefremov
<yegorslists@googlemail.com> wrote:
> Hi Stephan, all,
>
> I would split this patch in two:
>>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-08 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:33 [Buildroot] patch: linux-firmware-20221109 Stephan Henningsen
2022-12-07 12:33 ` Bagas Sanjaya
2022-12-07 12:56 ` Yegor Yefremov via buildroot
2022-12-08 21:19 ` Stephan Henningsen [this message]
2022-12-10 6:15 ` Stephan Henningsen
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=2KCLMR.A41GGA1OVAND1@asklandd.dk \
--to=stephan@asklandd.dk \
--cc=buildroot@buildroot.org \
--cc=yegorslists@googlemail.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