From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [ANN] resend patches or respond to 0-day reports
Date: Fri, 26 Apr 2019 11:48:32 +0200 [thread overview]
Message-ID: <25b58249576fd5a266464bc7a13a8f7e4d4344a0.camel@sipsolutions.net> (raw)
Hi all,
Just in case it wasn't clear already - if you get a 0-day report with
something that's trivially fixed (like missing documentation etc.)
please resend the patches immediately.
I'd rather have a resend than to comment and then wait later for both
changes, or to have to double-check that those things were later
addressed (or wait for 0-day again).
Thanks,
johannes
reply other threads:[~2019-04-26 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=25b58249576fd5a266464bc7a13a8f7e4d4344a0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.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