Em Wed, 11 Oct 2017 01:18:58 +0300
Sakari Ailus escreveu:
> > So, if you look, for example, at the chapter 1 name:
> > "common API elements"
> >
> > it implies that every single V4L2 device node supports what's there.
> > But that's not the case, for example, for what's
Em Wed, 11 Oct 2017 01:41:00 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> On Tue, Oct 10, 2017 at 08:37:43AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 6 Oct 2017 15:48:22 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > On
On Tue 10-10-17 14:13:00, David Rientjes wrote:
[...]
> For these reasons: unfair comparison of root mem cgroup usage to bias
> against that mem cgroup from oom kill in system oom conditions, the
> ability of users to completely evade the oom killer by attaching all
> processes to child cgroups
On Wed, Oct 11, 2017 at 01:21:47PM -0700, David Rientjes wrote:
> On Tue, 10 Oct 2017, Roman Gushchin wrote:
>
> > > We don't need a better approximation, we need a fair comparison. The
> > > heuristic that this patchset is implementing is based on the usage of
> > > individual mem cgroups.
On Wed, 11 Oct 2017, Michal Hocko wrote:
> > For these reasons: unfair comparison of root mem cgroup usage to bias
> > against that mem cgroup from oom kill in system oom conditions, the
> > ability of users to completely evade the oom killer by attaching all
> > processes to child cgroups
On Mon 2017-10-09 07:19:10, Mauro Carvalho Chehab wrote:
> There is a mess with media bus flags: there are two sets of
> flags, one used by parallel and ITU-R BT.656 outputs,
> and another one for CSI2.
>
> Depending on the type, the same bit has different meanings.
>
> @@ -86,11 +125,22 @@
CONFIG_BLK_DEV_HD_IDE was removed in commit 80aa31cb460d ("ide:
remove CONFIG_BLK_DEV_HD_IDE config option (take 2)") but the ide-cd
documentation was not updated and still asks users to disable it,
which is misleading and involves a fruitless search.
Signed-off-by: Finn Thain
On 10/09/2017 03:35 PM, Jonathan Cameron wrote:
On Mon, 9 Oct 2017 10:08:42 +0200
Maciej Purski wrote:
On 10/08/2017 11:47 AM, Jonathan Cameron wrote:
On Wed, 04 Oct 2017 09:11:31 +0200
Maciej Purski wrote:
On 10/01/2017 12:29 PM, Jonathan
Hi,
On Tue, Oct 10, 2017 at 8:59 PM, Masahiro Yamada
wrote:
> Hi Douglas,
>
>
> 2017-10-05 7:37 GMT+09:00 Douglas Anderson :
>> While timing a "no-op" build of the kernel (incrementally building the
>> kernel even though nothing changed) in
On Wed, 11 Oct 2017 16:42:53 +0200
Maciej Purski wrote:
> On 10/09/2017 03:35 PM, Jonathan Cameron wrote:
> > On Mon, 9 Oct 2017 10:08:42 +0200
> > Maciej Purski wrote:
> >
> >> On 10/08/2017 11:47 AM, Jonathan Cameron wrote:
> >>> On Wed, 04 Oct
On Tue, Oct 10, 2017 at 02:13:00PM -0700, David Rientjes wrote:
> On Tue, 10 Oct 2017, Roman Gushchin wrote:
>
> > > This seems to unfairly bias the root mem cgroup depending on process
> > > size.
> > > It isn't treated fairly as a leaf mem cgroup if they are being compared
> > > based on
Em Mon, 9 Oct 2017 10:19:55 -0300
Mauro Carvalho Chehab escreveu:
> > > I really don't want to add that much noise to the docs build; I think it
> > > will defeat any hope of cleaning up the warnings we already have. I
> > > wonder if we could suppress warnings about
On Tue, 10 Oct 2017, Roman Gushchin wrote:
> > We don't need a better approximation, we need a fair comparison. The
> > heuristic that this patchset is implementing is based on the usage of
> > individual mem cgroups. For the root mem cgroup to be considered
> > eligible, we need to
On Sat, Oct 07, 2017 at 10:51:42AM +0300, Gilad Ben-Yossef wrote:
> On Sat, Oct 7, 2017 at 6:05 AM, Herbert Xu
> wrote:
> > On Tue, Sep 05, 2017 at 03:38:40PM +0300, Gilad Ben-Yossef wrote:
> >>
> >> diff --git a/crypto/algif_hash.c b/crypto/algif_hash.c
> >> index
14 matches
Mail list logo