Spam detection software, running on the system "mail.turne-trans.ru", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
i...@turne-trans.ru for det
On 9 July 2016 at 08:30, Markus Mayer wrote:
> On 9 July 2016 at 05:04, Luis de Bethencourt wrote:
>> On 08/07/16 23:43, Markus Mayer wrote:
>>> Add a collection of generic functions to convert strings to lowercase
>>> or uppercase.
>>>
>>> Changing the case of a string (with or without copying i
From: Haiyang Zhang
This script helps to create bonding network devices based on synthetic NIC
(the virtual network adapter usually provided by Hyper-V) and the matching
VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
function as one network device, and fail over to the synth
> -Original Message-
> From: Nipun Gupta [mailto:nipun.gu...@nxp.com]
> Sent: Wednesday, June 29, 2016 12:15 PM
> To: gre...@linuxfoundation.org; Stuart Yoder
> Cc: de...@driverdev.osuosl.org; linux-ker...@vger.kernel.org; Nipun Gupta
> ; Bharat
> Bhushan
> Subject: [PATCH v2] fsl-mc:
On Mon, 2016-07-11 at 18:17 +0300, Andrey Utkin wrote:
[]
> diff --git a/drivers/media/pci/tw5864/tw5864-core.c
> b/drivers/media/pci/tw5864/tw5864-core.c
[]
> +static const char * const artifacts_warning =
> +"BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY\n"
> +"\n"
> +"This driver was developed by B
Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
mechanism between the host and the guest. It's somewhat like TCP over
VMBus, but the transportation layer (VMBus) is much simpler than IP.
With Hyper-V Sockets, applications between the host and the guest can talk
to each other d
FYI: you can also get the patch by (commit 5dde7975):
https://github.com/dcui/linux/tree/decui/hv_sock/net-next/20160711_v16
The delta changes between v15 and v16 are in the attached patch
delta_v15_vs_v16.patch.
--
Hyper-V Sockets (hv_sock) supplies a byt
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> ...
> Some comments below. The vast majority of them are really minor, the
> only thing which bothers me a little bit is WARN() in hvsock_sendmsg()
> which I think shouldn't be there. But I may have missed something.
Thank you for the very
Port the xattr functionality to the new xattr_handler API.
This is smallest changes needed to move to this new API. The
function ll_removexattr can be replaced by generic_removexattr
as well since it also uses the xattr_handler set xattr backend.
To tell the difference between the two cases we test
On 07/11/2016 01:48 PM, Andrey Utkin wrote:
> Thanks for review Hans!
>
> On Mon, Jul 11, 2016 at 07:58:38AM +0200, Hans Verkuil wrote:
>>> +" v4l2-ctl --device $dev --set-ctrl=video_gop_size=1; done\n"
>>
>> Replace $dev by /dev/videoX
>>
>> Wouldn't it make more sense to default to this? And sho
Thanks for review Hans!
On Mon, Jul 11, 2016 at 07:58:38AM +0200, Hans Verkuil wrote:
> > +" v4l2-ctl --device $dev --set-ctrl=video_gop_size=1; done\n"
>
> Replace $dev by /dev/videoX
>
> Wouldn't it make more sense to default to this? And show the warning only if
> P-frames are enabled?
I bel
> > > Though I normally prefer static inline functions, I see the benefits of
> > > using the macro form here.
>
> An inline could still work
> static inline void __user *u64_to_user_ptr(u64 address)
> {
> return (void __user *)(uintptr_t)address;
> }
> if th
On 07/11/2016, 07:58 AM, Hans Verkuil wrote:
>> +static char *artifacts_warning = "BEWARE OF KNOWN ISSUES WITH VIDEO
>> QUALITY\n"
>
> const char * const
Or even better, drop the extra space for pointer:
static const char artifacts_warning[] =
thanks,
--
js
suse labs
_
13 matches
Mail list logo
