On Mon, Nov 27, 2017 at 3:25 PM, David Howells wrote:
>
> This function has a list of requisite parameters for the caller:
.. and so what?
When you call "free()", that has a requisite parameter: the data to
free. If you don't supply it, we should BUG_ON(), right?
No.
On Mon, Nov 27, 2017 at 3:25 PM, David Howells wrote:
>
> This function has a list of requisite parameters for the caller:
.. and so what?
When you call "free()", that has a requisite parameter: the data to
free. If you don't supply it, we should BUG_ON(), right?
No. Instead we do the sane
On Mon, Nov 27, 2017 at 3:25 PM, David Howells wrote:
> Linus Torvalds wrote:
>
>> I'm not seeing why it would ever be ok to do BUG_ON() instead of just
>> returning an error, though.
>
> This function has a list of requisite parameters for the
On Mon, Nov 27, 2017 at 3:25 PM, David Howells wrote:
> Linus Torvalds wrote:
>
>> I'm not seeing why it would ever be ok to do BUG_ON() instead of just
>> returning an error, though.
>
> This function has a list of requisite parameters for the caller:
>
> BUG_ON(!pkey); <-- You
Linus Torvalds wrote:
> I'm not seeing why it would ever be ok to do BUG_ON() instead of just
> returning an error, though.
This function has a list of requisite parameters for the caller:
BUG_ON(!pkey); <-- You need the public key to use,
Linus Torvalds wrote:
> I'm not seeing why it would ever be ok to do BUG_ON() instead of just
> returning an error, though.
This function has a list of requisite parameters for the caller:
BUG_ON(!pkey); <-- You need the public key to use,
BUG_ON(!sig);
On Mon, 2017-11-27 at 21:46 +, Linus Torvalds wrote:
> On Sat, Nov 25, 2017 at 7:07 PM, Fengguang Wu wrote:
> > FYI, we noticed the following commit (built with gcc-4.8):
> >
> > commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
> > regulatory
On Mon, 2017-11-27 at 21:46 +, Linus Torvalds wrote:
> On Sat, Nov 25, 2017 at 7:07 PM, Fengguang Wu wrote:
> > FYI, we noticed the following commit (built with gcc-4.8):
> >
> > commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
> > regulatory keys/database later")
>
On Sat, Nov 25, 2017 at 7:07 PM, Fengguang Wu wrote:
> FYI, we noticed the following commit (built with gcc-4.8):
>
> commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
> regulatory keys/database later")
The attached 'dmesg.xz' doesn't actually match
On Sat, Nov 25, 2017 at 7:07 PM, Fengguang Wu wrote:
> FYI, we noticed the following commit (built with gcc-4.8):
>
> commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
> regulatory keys/database later")
The attached 'dmesg.xz' doesn't actually match the kernel or the
FYI, we noticed the following commit (built with gcc-4.8):
commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
regulatory keys/database later")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64
FYI, we noticed the following commit (built with gcc-4.8):
commit: d7be102f2945a626f55e0501e52bb31ba3e77b81 ("cfg80211: initialize
regulatory keys/database later")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-x86_64
12 matches
Mail list logo