From: Shay Bar <Shay.Bar@celeno.com>
To: Hauke Mehrtens <hauke@hauke-m.de>,
"mcgrof@kernel.org" <mcgrof@kernel.org>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
Eliav Farber <Eliav.Farber@celeno.com>
Subject: RE: [PATCH] backports: Add time64_to_tm and ipv6_mc_check_mld
Date: Sun, 15 Nov 2020 14:07:34 +0000 [thread overview]
Message-ID: <AM0P192MB04684FF2B814EF6A61549381E7E40@AM0P192MB0468.EURP192.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <29b92ce7-9dc1-0456-34b0-6391ef628005@hauke-m.de>
Hi Hauke,
Indeed, no wifi driver is currently using them, but we plan to
commit our new driver (that uses it) to the kernel.
Should I ping this patch again once we upstream or can you
already accept it now ?
Thanks,
Shay.
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2020-11-15 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:03 [PATCH] backports: Add time64_to_tm and ipv6_mc_check_mld Shay Bar
2020-11-15 13:46 ` Hauke Mehrtens
2020-11-15 14:07 ` Shay Bar [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=AM0P192MB04684FF2B814EF6A61549381E7E40@AM0P192MB0468.EURP192.PROD.OUTLOOK.COM \
--to=shay.bar@celeno.com \
--cc=Eliav.Farber@celeno.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=mcgrof@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).