From: Johannes Berg <johannes@sipsolutions.net>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Paul Menzel <pmenzel+linux-wireless@molgen.mpg.de>,
Damian Tometzki <damian.tometzki@icloud.com>
Subject: Re: [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c
Date: Tue, 19 Dec 2017 21:11:30 +0100 [thread overview]
Message-ID: <1513714290.26145.24.camel@sipsolutions.net> (raw)
In-Reply-To: <20171219192303.31395-1-briannorris@chromium.org> (sfid-20171219_202313_371734_5DF1684C)
On Tue, 2017-12-19 at 11:23 -0800, Brian Norris wrote:
>
> In practice, this is seen often by having a separate source and build
> directory, where the build artifacts remain but the source tree changes
> (even if Seth's cert doesn't change, it might get created/removed when
> checking out different source revisions).
>
> I don't see why this rule should be an append; we're writing the file
> all in one go.
Yeah, that was an oversight from the code prior to my changes to make
it write it only once.
> Fixes: 90a53e4432b1 ("cfg80211: implement regdb signature checking")
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> ---
> This is an error introduced in 4.15-rc1.
>
> I've seen other errors reported by Paul and Damian (CC'd); I think Paul's
> failure was fixed already, but Damian might have still been having problems
> with not having a "clean" environment. Perhaps he was hitting this bug?
I'm not really sure what that problem was - I think a combination of
missing clean-files and this perhaps? Anyway, I applied another fix for
this today, and it's on the way to Linus's tree, along with the missing
clean-files and a conversion to non-binary files so that patches work
better.
johannes
next prev parent reply other threads:[~2017-12-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 19:23 [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c Brian Norris
2017-12-19 20:11 ` Johannes Berg [this message]
2017-12-19 20:38 ` Brian Norris
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=1513714290.26145.24.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=briannorris@chromium.org \
--cc=damian.tometzki@icloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel+linux-wireless@molgen.mpg.de \
/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).