From: Rohit Thapliyal
swiotlb default size of 64M is too big as
default value therefore it is made configurable
through command line through swiotlb_size parameter.
swiotlb allocation shall be done only when the
swiotlb size is given through command line.
Otherwise no swiotlb is allocated.
Signe
The first 9 patches are just a resend of [1], there's two patches on top
here.
Pull details below.
BR,
Jani.
[1] http://mid.gmane.org/cover.1465567017.git.jani.nik...@intel.com
The following changes since commit 8569de68e79e94cce6709831edd94accb6942ade:
docs: kernel-doc: Add "example" and "
Let the user specify file patterns where to look for the EXPORT_SYMBOLs
in addition to the file with kernel-doc comments. This is directly based
on the -export-file FILE option added to kernel-doc in "kernel-doc: add
support for specifying extra files for EXPORT_SYMBOLs", but we extend
that with gl
Leftover cruft. No functional changes.
Signed-off-by: Jani Nikula
---
Documentation/sphinx/kernel-doc.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/sphinx/kernel-doc.py
b/Documentation/sphinx/kernel-doc.py
index 4adfb0e91ecc..2856376cc62c 100644
--- a/Do
Using the default str.split doesn't return empty strings like the
current version does.
Signed-off-by: Jani Nikula
---
Documentation/sphinx/kernel-doc.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/sphinx/kernel-doc.py
b/Documentation/sphinx/kernel-doc.py
i
The modindex is for python modules.
Signed-off-by: Jani Nikula
---
Documentation/index.rst | 2 --
1 file changed, 2 deletions(-)
diff --git a/Documentation/index.rst b/Documentation/index.rst
index 71a276f34c7f..1139a7ea39ec 100644
--- a/Documentation/index.rst
+++ b/Documentation/index.rst
@@
While there's slight overlap with the DocBook help now, this can stay
intact when the DocBook help goes away.
Signed-off-by: Jani Nikula
---
Documentation/DocBook/Makefile | 4 ++--
Documentation/Makefile.sphinx | 8
Makefile | 2 ++
3 files changed, 12 insertions
If the kernel-doc comments for functions are not in the same file as the
EXPORT_SYMBOL statements, the -export and -internal output selections do
not work as expected. This is typically the case when the kernel-doc
comments are in header files next to the function declarations and the
EXPORT_SYMBOL
Scan all input files for EXPORT_SYMBOLs along with the explicitly
specified export files before actually parsing anything.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel
On 23/06/16 13:13, Manjeet Pawar wrote:
From: Rohit Thapliyal
swiotlb default size of 64M is too big as
default value therefore it is made configurable
through command line through swiotlb_size parameter.
swiotlb allocation shall be done only when the
swiotlb size is given through command line.
Since
commit 32217761ee9db0215350dfe1ca4e66f312fb8c54
Author: Jani Nikula
Date: Sun May 29 09:40:44 2016 +0300
kernel-doc: concatenate contents of colliding sections
we started getting (more) errors on duplicate section names, especially
on the default section name "Description":
include
No functional changes.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 27757c21551a..ac18eb5ed776 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -529,21 +529,18 @@ sub dump_section
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 710615f3a4ff..a6f82c812c15 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -484,10 +484,10 @@ while ($ARGV[0] =~ m/^-
Reduce duplication in follow-up work. No functional changes.
Signed-off-by: Jani Nikula
---
scripts/kernel-doc | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index a6f82c812c15..516d95fcefb7 100755
--- a/sc
On Thu, 23 Jun 2016 15:28:00 +0300
Jani Nikula wrote:
> The first 9 patches are just a resend of [1], there's two patches on top
> here.
OK, these all look good to me. Applied to the docs tree, sorry for the
delay.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
On Fri, 17 Jun 2016 09:40:02 +0800 (CST)
"Tiezhu Yang" wrote:
> I read drivers/md/raid5.c and find the following related code:
> 1) in function 'raid5_set_cache_size':
> if (size <= 16 || size > 32768)
> return -EINVAL;
> 2) #define NR_STRIPES 256
>
> So the lower limit value of st
On Sat, 11 Jun 2016 02:56:37 +0200
Michal Nazarewicz wrote:
> -For the gadget two work under Windows two conditions have to be met:
> +For the gadget to work under Windows two conditions have to be met:
Applied to the docs tree, thanks.
jon
--
To unsubscribe from this list: send the line "unsub
On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
> From: Rohit Thapliyal
>
> swiotlb default size of 64M is too big as
> default value therefore it is made configurable
> through command line through swiotlb_size parameter.
> swiotlb allocation shall be done only when the
> swiotlb
Hi,
[auto build test WARNING on v4.7-rc4]
[cannot apply to arm64/for-next/core next-20160623]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Manjeet-Pawar/arm64-swiotlb-Enable-only-when-Input
There are many basic ways to control processes, including capabilities,
cgroups and resource limits. However, there are far fewer ways to find
out useful values for the limits, except blind trial and error.
Currently, there is no way to know which capabilities are actually used.
Even the source co
Blacklisting a module in linux has long been a problem. The current
procedure is to use rd.blacklist=module_name, however, that doesn't
cover the case after the initramfs and before a boot prompt (where one
is supposed to use /etc/modprobe.d/blacklist.conf to blacklist
runtime loading). Using rd.s
On June 23, 2016 10:30:34 AM EDT, Catalin Marinas
wrote:
>On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
>> From: Rohit Thapliyal
>>
>> swiotlb default size of 64M is too big as
>> default value therefore it is made configurable
>> through command line through swiotlb_size param
On Tue, Jun 7, 2016 at 11:05 AM, Hoan Tran wrote:
> Hi Jassi,
>
> Thanks for your reply !
>
> On Tue, Jun 7, 2016 at 10:20 AM, Jassi Brar wrote:
>> On Tue, May 24, 2016 at 6:31 AM, Hoan Tran wrote:
>>> Hi Rob,
>>>
>>> Thanks for your review !
>>>
>>> On Mon, May 23, 2016 at 1:30 PM, Rob Herring
Cc: Joseph Jezak
Cc: Jörg Sommer
Cc: Mark Rutland
Signed-off-by: Stephan Linz
Acked-by: Rob Herring
Signed-off-by: Jacek Anaszewski
---
Changes in v5:
- Keep documentation for the old 'ide-disk' device tree
binding, but mark as deprecated and refer to the new
trigger 'disk-activity'
Jason Cooper wrote:
> Modern systems that receive a seed from the bootloader via the
> random-seed property (typically from the hw-rng) can mix both sources
> for increased resilience.
>
> Unfortunately, I'm not very familiar with the internals of x86
> bootstrapping. Could GRUB be scripted to d
Hey Kees, Thomas,
On Wed, Jun 22, 2016 at 10:05:51AM -0700, Kees Cook wrote:
> On Wed, Jun 22, 2016 at 8:59 AM, Thomas Garnier wrote:
> > On Wed, Jun 22, 2016 at 5:47 AM, Jason Cooper wrote:
> >> Hey Kees,
> >>
> >> On Tue, Jun 21, 2016 at 05:46:57PM -0700, Kees Cook wrote:
> >>> Notable problem
On Thu, Jun 23, 2016 at 12:33 PM, Jason Cooper wrote:
> Hey Kees, Thomas,
>
> On Wed, Jun 22, 2016 at 10:05:51AM -0700, Kees Cook wrote:
>> On Wed, Jun 22, 2016 at 8:59 AM, Thomas Garnier wrote:
>> > On Wed, Jun 22, 2016 at 5:47 AM, Jason Cooper wrote:
>> >> Hey Kees,
>> >>
>> >> On Tue, Jun 21,
On Thu, Jun 23, 2016 at 12:45 PM, Sandy Harris wrote:
> Jason Cooper wrote:
>
>> Modern systems that receive a seed from the bootloader via the
>> random-seed property (typically from the hw-rng) can mix both sources
>> for increased resilience.
>>
>> Unfortunately, I'm not very familiar with the
On 23 June 2016 at 21:58, Kees Cook wrote:
> On Thu, Jun 23, 2016 at 12:33 PM, Jason Cooper wrote:
>> Hey Kees, Thomas,
>>
>> On Wed, Jun 22, 2016 at 10:05:51AM -0700, Kees Cook wrote:
>>> On Wed, Jun 22, 2016 at 8:59 AM, Thomas Garnier wrote:
>>> > On Wed, Jun 22, 2016 at 5:47 AM, Jason Cooper
On Thu, Jun 23, 2016 at 12:59:07PM -0700, Kees Cook wrote:
> On Thu, Jun 23, 2016 at 12:45 PM, Sandy Harris wrote:
> > Jason Cooper wrote:
> >
> >> Modern systems that receive a seed from the bootloader via the
> >> random-seed property (typically from the hw-rng) can mix both sources
> >> for in
Hey Sandy,
On Thu, Jun 23, 2016 at 03:45:54PM -0400, Sandy Harris wrote:
> Jason Cooper wrote:
>
> > Modern systems that receive a seed from the bootloader via the
> > random-seed property (typically from the hw-rng) can mix both sources
> > for increased resilience.
> >
> > Unfortunately, I'm n
On Thu, Jun 16, 2016 at 08:09:42AM +0200, Wolfram Sang wrote:
> > > - removed the .resume hook as upstream changed suspend/resume hooks and
> > > there
> > > is no need in the end to re-enable host notify on resume (tested on
> > > Lenovo
> > > t440 and t450).
> >
> > Actually, this hook see
On Thu, Jun 23, 2016 at 8:07 AM, Topi Miettinen wrote:
> There are many basic ways to control processes, including capabilities,
> cgroups and resource limits. However, there are far fewer ways to find
> out useful values for the limits, except blind trial and error.
>
> Currently, there is no way
Hello,
On Thu, Jun 23, 2016 at 06:07:10PM +0300, Topi Miettinen wrote:
> There are many basic ways to control processes, including capabilities,
> cgroups and resource limits. However, there are far fewer ways to find
> out useful values for the limits, except blind trial and error.
>
> Currently
On Thu, Jun 23, 2016 at 01:55:52PM -0700, Dmitry Torokhov wrote:
> On Thu, Jun 16, 2016 at 08:09:42AM +0200, Wolfram Sang wrote:
> > > > - removed the .resume hook as upstream changed suspend/resume hooks and
> > > > there
> > > > is no need in the end to re-enable host notify on resume (tested
On Thu, Jun 23, 2016 at 11:46:55PM +0200, Wolfram Sang wrote:
> On Thu, Jun 23, 2016 at 01:55:52PM -0700, Dmitry Torokhov wrote:
> > On Thu, Jun 16, 2016 at 08:09:42AM +0200, Wolfram Sang wrote:
> > > > > - removed the .resume hook as upstream changed suspend/resume hooks
> > > > > and there
> > >
Hi Benjamin,
On Thu, Jun 09, 2016 at 04:53:50PM +0200, Benjamin Tissoires wrote:
> +
> +struct mapping_table_entry {
> + u16 rmiaddr;
Should be __le16 rmiaddr, otherwise:
CHECK drivers/input/rmi4/rmi_smbus.c
drivers/input/rmi4/rmi_smbus.c:116:33: warning: incorrect type in assignment
(d
On Thu, 23 Jun 2016 18:07:10 +0300 Topi Miettinen wrote:
> There are many basic ways to control processes, including capabilities,
> cgroups and resource limits. However, there are far fewer ways to find
> out useful values for the limits, except blind trial and error.
>
> Currently, there is no
On 06/23/16 21:38, Tejun Heo wrote:
> Hello,
>
> On Thu, Jun 23, 2016 at 06:07:10PM +0300, Topi Miettinen wrote:
>> There are many basic ways to control processes, including capabilities,
>> cgroups and resource limits. However, there are far fewer ways to find
>> out useful values for the limits,
Hi Ard,
On Thu, Jun 23, 2016 at 10:05:53PM +0200, Ard Biesheuvel wrote:
> On 23 June 2016 at 21:58, Kees Cook wrote:
> > On Thu, Jun 23, 2016 at 12:33 PM, Jason Cooper wrote:
> >> On Wed, Jun 22, 2016 at 10:05:51AM -0700, Kees Cook wrote:
> >>> On Wed, Jun 22, 2016 at 8:59 AM, Thomas Garnier
>
On 06/23/16 23:46, Andrew Morton wrote:
> On Thu, 23 Jun 2016 18:07:10 +0300 Topi Miettinen wrote:
>
>> There are many basic ways to control processes, including capabilities,
>> cgroups and resource limits. However, there are far fewer ways to find
>> out useful values for the limits, except bli
So that users know what the interface and meaning of the keyed values
are. In addition, mention that the only time that since=0 is when the
limit was changed.
Signed-off-by: Aleksa Sarai
---
Documentation/cgroup-v1/pids.txt | 18 ++
1 file changed, 18 insertions(+)
diff --git a/
This allows users to dynamically adjust their limits based on how many
failed forks happened since they last reset their limits, otherwise they
would have to track (in a racy way) how many limit failures there were
since the last limit change manually. In addition, we log the first
failure since th
While reading the patchset by Kenny Yu, I realised that not having a
field for the "recent" number of failed forks means that userspace would
have trouble accurately deciding whether or not it should increase the
limits.
In addition, by having hits_since, we get to maintain the
on-reset-we-log-fai
Dear Konrad,
On Thu, 23 Jun 2016 12:06:10 -0400 Konrad Rzeszutek Wilk wrote:
> On June 23, 2016 10:30:34 AM EDT, Catalin Marinas
> wrote:
> >On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
> >> From: Rohit Thapliyal
> >>
> >> swiotlb default size of 64M is too big as
> >> def
On Thu, Jun 23, 2016 at 6:14 PM, Topi Miettinen wrote:
> On 06/23/16 23:46, Andrew Morton wrote:
>> On Thu, 23 Jun 2016 18:07:10 +0300 Topi Miettinen wrote:
>>
>>> There are many basic ways to control processes, including capabilities,
>>> cgroups and resource limits. However, there are far fewer
Hi Stephan,
On 06/23/2016 09:38 PM, Stephan Linz wrote:
Cc: Joseph Jezak
Cc: Jörg Sommer
Cc: Mark Rutland
Signed-off-by: Stephan Linz
Acked-by: Rob Herring
Signed-off-by: Jacek Anaszewski
---
Changes in v5:
- Keep documentation for the old 'ide-disk' device tree
binding, but mark a
47 matches
Mail list logo
