On Fri 14-10-16 22:46:04, Minchan Kim wrote:
[...]
> > > > Why don't you simply mimic what shrink_inactive_list does? Aka count the
> > > > number of isolated pages and then account them when appropriate?
> > > >
> > > I think i am correcting clearly wrong part. So, there is no need to
> > > descri
On Oct 14 2016 or thereabouts, Jiri Kosina wrote:
> On Thu, 13 Oct 2016, Benjamin Tissoires wrote:
>
> > Hi Jiri,
> >
> > David and I are facing an issue in RHEL with the HP Zbook 15 Studio mWS.
> > This laptops uses the pinctrl-sunrisepoint controller for the GPIOs and
> > it failed on RHEL. We
The following changes since commit
3c76ff4765fbd382c095acc37f87e136a8dfc73d:
URL changed for Linux Foundation TAB (2016-10-01 00:57:13 -0600)
are available in the git repository at:
git://git.lwn.net/linux.git tags/docs-4.9-2
for you to fetch changes up to 819bf593767c0966f320c51c6ed3f38350
Hello My Dear
How are you doing ? Hope you are fine by grace of God, My
Name is Mrs Mirian Michel from Germany i need your urgent assistance and
collaboration on a projet, I am witting for your urgent reply for more details
My Email missmiriammiche...@hotmail.com
Thanks
Mrs M
On Thu, 13 Oct 2016, Benjamin Tissoires wrote:
> Hi Jiri,
>
> David and I are facing an issue in RHEL with the HP Zbook 15 Studio mWS.
> This laptops uses the pinctrl-sunrisepoint controller for the GPIOs and
> it failed on RHEL. We found out what the issue was, but in the meantime
> realized tha
Hi Javier,
Thanks for the patch.
Applied to the for-4.10 branch of linux-leds.git.
Best regards,
Jacek Anaszewski
On 10/14/2016 02:23 PM, Javier Martinez Canillas wrote:
If the driver is built as a module, I2C module alias information is not
filled so the module won't be autoloaded if the devi
KASAN stack instrumentation poisons stack redzones on function entry
and unpoisons them on function exit. If a function exits abnormally
(e.g. with a longjmp like jprobe_return()), stack redzones are left
poisoned. Later this leads to random KASAN false reports.
Unpoison stack redzones in the fram
On Fri, Oct 14, 2016 at 3:08 PM, Mark Rutland wrote:
> On Fri, Oct 14, 2016 at 01:54:30PM +0200, Dmitry Vyukov wrote:
>> KASAN stack instrumentation poisons stack redzones on function entry
>> and unpoisons them on function exit. If a function exits abnormally
>> (e.g. with a longjmp like jprobe_r
Hi Jaegeuk,
On 2016/10/14 4:49, Jaegeuk Kim wrote:
> Hi Chao,
>
> On Thu, Oct 13, 2016 at 12:14:27AM +0800, Chao Yu wrote:
>> From: Chao Yu
>>
>> tests/generic/251 of fstest reports a f2fs bug in below message:
>>
>> [ cut here ]
>> invalid opcode: [#1] PREEMPT SMP
>
From: Javier Martinez Canillas
Date: Wed, 12 Oct 2016 15:55:41 -0300
> When the device is registered via OF, the OF table is used to match the
> driver instead of the SPI device ID table, but the entries in the later
> are used as aliasses to load the module if the driver was not built-in.
>
> T
From: Javier Martinez Canillas
Date: Wed, 12 Oct 2016 16:05:59 -0300
> The driver only has runtime but no build time dependency with FSL_SOC ||
> ARCH_MXC || ARCH_LAYERSCAPE. So it can be built for testing purposes if
> the COMPILE_TEST option is enabled.
>
> This is useful to have more build c
Am Dienstag, 27. September 2016, 13:53:46 CEST schrieb Vagrant Cascadian:
> This essentially mimics what was done with rk3288-veyron-minnie in
> commit 984926781122f034d5bc9962815d135b6c4a8e1d.
>
> The eMMC of the speedy Chromebook also appears to need the same tuning
> workaround, as it frequentl
They are buggy:
while (usec > 0)
udelay(usec % 1024);
usec -= 1024;
For example, for usec = 100*1024 + 1, old code will udelay(1) 101 times,
i.e. it will be approximately equivalent to udelay(101),
not the expected udelay(102400).
This did not bite because a
* Jacek Anaszewski [161013 23:37]:
> On 10/13/2016 04:20 PM, Matt Ranostay wrote:
> > On Thu, Oct 13, 2016 at 4:05 PM, Jacek Anaszewski
> > wrote:
> > > Why DT property? Is it somehow dependent on the board configuration?
> > > How this period-scale value is calculated? Is it inferred empirically
> On 14 Oct 2016, at 14:46, Johannes Berg wrote:
>
>
>>
>> Is the aad[] actually reused? I would assume it only affects the mac
>> on encryption, and the verification on decryption but I don't think
>> we actually need it back from the crypto routines.
>
> I don't think it's reused.
>
>> Exa
On Fri, Oct 14, 2016 at 03:40:22PM +0200, Paul Bolle wrote:
> Hi,
>
> It took me quite some time to get v4.4.24 to successfully boot (this
> was a 32 bits build on Fedora 24). Especially annoying was that it
> failed silently on real hardware. Only after messing around with Qemu
> it became clear
On Wed, Oct 12, 2016 at 11:01 AM, Dan Williams wrote:
> Commit 917db484dc6a "x86/boot: Fix kdump, cleanup aborted E820_PRAM
> max_pfn manipulation" fixed up the broken manipulations of max_pfn in
> the presence of E820_PRAM ranges. However, it also broke the
> sanitize_e820_map() support for not m
From: Javier Martinez Canillas
Date: Wed, 12 Oct 2016 15:55:40 -0300
> If the driver is built as a module, module alias information isn't filled
> so the module won't be autoloaded. Add a SPI device ID table and use the
> MODULE_DEVICE_TABLE() macro so the information is exported in the module.
>
From: Alexander Alemayhu
Date: Thu, 13 Oct 2016 17:09:51 +0200
> This fixes the following errors when trying to clone the urls:
>
> Cloning into 'net'...
> fatal: repository
> 'http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/' not found
> Cloning into 'net-next'...
> fatal: repository
For mounts that have the new "nolinks" option, don't follow symlinks
and reject to open files with a hard link count larger than one. The
new option is similar in spirit to the existing "nodev", "noexec", and
"nosuid" options.
Note that symlinks and hard links may still be created on mounts where
Hello,
This small series contains trivial fixes to allow modules to be autoloaded
when its correspoinding thermal device is registered.
Best regards,
Javier
Javier Martinez Canillas (3):
thermal: max77620: Fix module autoload
thermal: tango: Fix module autoload
thermal: db8500: Fix module
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
On Fri, 14 Oct 2016, Felipe Balbi wrote:
> argh, we have nested spinlocks :-( Well, we shouldn't call
> usb_ep_disable() with locks held AFAICR. So the following should be
> enough:
>
> diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
> index 919d7d1b611c..2e9359c58eb9
From: David Howells
Date: Thu, 13 Oct 2016 17:12:09 +0100
>
> This set of patches contains a bunch of fixes:
>
> (1) Fix use of kunmap() after change from kunmap_atomic() within AFS.
>
> (2) Don't use of ERR_PTR() with an always zero value.
>
> (3) Check the right error when using ip6_rout
On Fri, Oct 14, 2016 at 03:53:34PM +0200, Michal Hocko wrote:
> On Fri 14-10-16 22:46:04, Minchan Kim wrote:
> [...]
> > > > > Why don't you simply mimic what shrink_inactive_list does? Aka count
> > > > > the
> > > > > number of isolated pages and then account them when appropriate?
> > > > >
> >
On Fri, Oct 14, 2016 at 04:28:25PM +0200, Mattias Nissler wrote:
> For mounts that have the new "nolinks" option, don't follow symlinks
> and reject to open files with a hard link count larger than one. The
> new option is similar in spirit to the existing "nodev", "noexec", and
> "nosuid" options.
On Fri, Oct 14, 2016 at 03:55:15PM +0100, Al Viro wrote:
> > Setting the "nolinks" mount option helps prevent privileged writers
> > from modifying files unintentionally in case there is an unexpected
> > link along the accessed path. The "nolinks" option is thus useful as a
> > defensive measure a
On Thu, Oct 13, 2016 at 6:29 PM, John Stultz wrote:
> From: Chen Yu
>
> The Hi6220's usb controller is limited in that it does not
> automatically autonegotiate the usb speed. Thus it requires a
> quirk so that we can manually negotiate the best usb speed for
> the attached device.
>
> Cc: Wei Xu
On 10/14/16 15:18, Laszlo Ersek wrote:
> On 10/14/16 10:05, Andrew Jones wrote:
>> On Fri, Oct 14, 2016 at 12:50:29AM +0200, Laszlo Ersek wrote:
>>> (4) Analysis (well, a lame attempt at that, because I have zero
>>> familiarity with this code). Let me quote the patch:
>>>
commit 7ba5f605f3a0d
On Fri 14-10-16 23:44:48, Minchan Kim wrote:
> On Fri, Oct 14, 2016 at 03:53:34PM +0200, Michal Hocko wrote:
> > On Fri 14-10-16 22:46:04, Minchan Kim wrote:
> > [...]
> > > > > > Why don't you simply mimic what shrink_inactive_list does? Aka
> > > > > > count the
> > > > > > number of isolated pa
Hello, Michael.
On Tue, Oct 11, 2016 at 10:22:13PM +1100, Michael Ellerman wrote:
> The oops happens because we're in enqueue_task_fair() and p->se->cfs_rq
> is NULL.
>
> The cfs_rq is NULL because we did set_task_rq(p, 2048), where 2048 is
> NR_CPUS. That causes us to index past the end of the t
Hello, Balbir.
On Tue, Oct 11, 2016 at 11:21:09PM +1100, Balbir Singh wrote:
> FYI: I see the samething on my cpu as well, its just that I get lucky
> and cpu_online(cpu) returns false.
Are you seeing this on x86 or is your test setup also a power machine?
Thanks.
--
tejun
On Fri, Oct 14, 2016 at 2:39 PM, Brian Starkey wrote:
>> - Besides the above property, writeback hardware can have provisions
>> for scaling, color space conversion and rotation. This would mean that
>> we'd eventually add more writeback specific props/params in
>> drm_connector/drm_connector_stat
Le Friday 14 Oct 2016 à 14:10:07 (+0100), Dietmar Eggemann a écrit :
> On 14/10/16 09:24, Vincent Guittot wrote:
> > On 13 October 2016 at 23:34, Vincent Guittot
> > wrote:
> >> On 13 October 2016 at 20:49, Dietmar Eggemann
> >> wrote:
> >>> On 13/10/16 17:48, Vincent Guittot wrote:
> On 1
Em Fri, Oct 14, 2016 at 05:57:25AM -0700, Stephane Eranian escreveu:
> On Fri, Oct 14, 2016 at 4:13 AM, Arnaldo Carvalho de Melo
> wrote:
> > Em Thu, Oct 13, 2016 at 03:05:40PM -0500, Nilay Vaish escreveu:
> >> Do we not need to release the memory for err_msg if the condition for
> >> the 'if' st
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ $ modinfo dri
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
On 10/14/2016 12:24 AM, Linus Torvalds wrote:
> On Thu, Oct 13, 2016 at 1:21 PM, Anna Schumaker
> wrote:
>>
>> git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.9-1
>
> Please keep the summary of changes in the email too. I can see it in
> the tag, and it will show up when I do
On 10/14/2016 03:02 PM, Joao Pinto wrote:
> Hi Niklas,
>
>
> On 10/14/2016 1:41 PM, Niklas Cassel wrote:
>> Hello
>>
>> Because of recent changes to drivers/pci/host/pcie-artpec6.c,
>> I was going to try out Bjorn's tag pci-v4.9-changes-2,
>> however I was greeted by an imprecise external abort:
>>
KASAN uses stackdepot to memorize stacks for all kmalloc/kfree calls.
Current stackdepot capacity is 16MB (1024 top level entries x
4 pages on second level). Size of each stack is (num_frames + 3) *
sizeof(long). Which gives us ~84K stacks. This capacity was chosen
empirically and it is enough to r
On Fri, Oct 14, 2016 at 05:03:55PM +0200, Michal Hocko wrote:
> On Fri 14-10-16 23:44:48, Minchan Kim wrote:
> > On Fri, Oct 14, 2016 at 03:53:34PM +0200, Michal Hocko wrote:
> > > On Fri 14-10-16 22:46:04, Minchan Kim wrote:
> > > [...]
> > > > > > > Why don't you simply mimic what shrink_inactive
On 10/14/16 17:01, Laszlo Ersek wrote:
> Maybe the code I
> tried to analyze in this email was never *meant* to associate CPU#0 with
> any NUMA node at all (not even node 0); instead, other code -- for
> example code removed by 7ba5f605f3a0 -- was meant to perform that
> association.
Staring a bi
> > addfield(map, &extra_desc, ". ",
> > " Supports address when precise",
> > NULL);
> > + } else if (json_streq(map, field, "Unit")) {
>
> so I remember you said you're preparing
On 14/10/2016 16:35, Javier Martinez Canillas wrote:
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias information using the M
Em Thu, Oct 13, 2016 at 02:15:23PM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> Move the scale factor parsing code to an own function
> to reuse it in an upcoming patch.
>
> Signed-off-by: Andi Kleen
> ---
> tools/perf/util/pmu.c | 64
> +++---
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
On Fri, Oct 14, 2016 at 05:27:58PM +0200, Laszlo Ersek wrote:
> On 10/14/16 17:01, Laszlo Ersek wrote:
>
> > Maybe the code I
> > tried to analyze in this email was never *meant* to associate CPU#0 with
> > any NUMA node at all (not even node 0); instead, other code -- for
> > example code removed
Em Thu, Oct 13, 2016 at 02:15:24PM -0700, Andi Kleen escreveu:
> From: Andi Kleen
>
> With uncore event aliases which are duplicated over multiple PMUs
> the "Using CPUID" message with -v could be printed many times.
> Only print it once.
Thanks, applied.
- Arnaldo
> Signed-off-by: Andi Kleen
> So if we can't convert the scale because of an allocation failure
> related to locale issues we silently trow it away and do no scale at
> all?
That is right. If your machine is thrashing to death in a OOM this
is your smallest problem.
-Andi
On 10/14/16 15:44, Andrew Jones wrote:
> On Fri, Oct 14, 2016 at 03:18:00PM +0200, Laszlo Ersek wrote:
>> On 10/14/16 10:05, Andrew Jones wrote:
>>> On Fri, Oct 14, 2016 at 12:50:29AM +0200, Laszlo Ersek wrote:
(4) Analysis (well, a lame attempt at that, because I have zero
familiarity wi
Em Thu, Oct 13, 2016 at 06:18:11PM +0200, Alexander Alemayhu escreveu:
> The latter version occurs much more when running git grep.
Thanks, applied, but please next time add to the CC list people that
last touched this code, like Wang, that I'm CC'ing here and in the patch
I just applied.
- Arnal
On Fri, Oct 14, 2016 at 5:00 PM, Al Viro wrote:
>
> On Fri, Oct 14, 2016 at 03:55:15PM +0100, Al Viro wrote:
> > > Setting the "nolinks" mount option helps prevent privileged writers
> > > from modifying files unintentionally in case there is an unexpected
> > > link along the accessed path. The "
Em Wed, Oct 12, 2016 at 11:48:22PM +0200, Alexis Berlemont escreveu:
> Hi,
>
> Here is a small patch which tries to fulfill a point in the perf todo
> list:
>
> * Make pressing 'V' multiple times to go on cycling thru various
> verbosity levels in 'perf top', so that info that is present in
>
I am going to leave Synopsys and so this patch changes the Maintainer
for UFS Synopsys' specific drivers to my colleagues Manjunath and Prabu.
Signed-off-by: Joao Pinto
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5ac91d8a.
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
Em Mon, Oct 10, 2016 at 07:43:27AM +0200, Alexis Berlemont escreveu:
> Hi,
>
> In the perf wiki todo-list, there is an entry regarding initial-delay and
> perf trace; the following small patch tries to fulfill this point. It
> has been generated against the branch tip/perf/core.
>
> It has only b
On 10/14/2016 11:18 AM, Vincent Guittot wrote:
> Le Friday 14 Oct 2016 à 14:10:07 (+0100), Dietmar Eggemann a écrit :
>> On 14/10/16 09:24, Vincent Guittot wrote:
>>> On 13 October 2016 at 23:34, Vincent Guittot
>>> wrote:
On 13 October 2016 at 20:49, Dietmar Eggemann
wrote:
> On
I am going to leave Synopsys and so this patch changes the Maintainer
for PCIe Designware Platform driver to my colleague Jose Abreu.
Signed-off-by: Joao Pinto
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 01bff8e..5ac91d8a 10
In order to aid debugging, we add a debugfs interface to the driver
that allows direct interaction with the AVS co-processor.
The debugfs interface provides a means for reading all and writing some
of the mailbox registers directly from the shell prompt and enables a
user to execute the communicat
On Fri, Oct 14, 2016 at 01:08:42PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Oct 14, 2016 at 08:45:15AM -0700, Andi Kleen escreveu:
> > > So if we can't convert the scale because of an allocation failure
> > > related to locale issues we silently trow it away and do no scale at
> > > all?
>
Em Fri, Oct 14, 2016 at 08:45:15AM -0700, Andi Kleen escreveu:
> > So if we can't convert the scale because of an allocation failure
> > related to locale issues we silently trow it away and do no scale at
> > all?
> That is right. If your machine is thrashing to death in a OOM this
> is your smal
On 10/14/2016 4:24 PM, Niklas Cassel wrote:
> On 10/14/2016 03:02 PM, Joao Pinto wrote:
>> Hi Niklas,
>>
>>
>> On 10/14/2016 1:41 PM, Niklas Cassel wrote:
>>> Hello
>>>
(snip)
> }
> }
>
> - pp->iatu_unroll_enabled = dw_pcie_iatu_unroll_enabled(pp);
> -
> if
On Fri, 2016-10-14 at 16:08 +0200, Greg KH wrote:
> Did you apply that patch and it worked properly for you? If so, yes,
> I'll be glad to queue it up.
Yes I did and it did.
But I do find this commit as magical as they can get so I'd hoped that
hjl would speak up. But if my word is enough for yo
Em Fri, Oct 14, 2016 at 09:15:16AM -0700, Andi Kleen escreveu:
> On Fri, Oct 14, 2016 at 01:08:42PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Oct 14, 2016 at 08:45:15AM -0700, Andi Kleen escreveu:
> > > > So if we can't convert the scale because of an allocation failure
> > > > related to
On 13/10/16 20:37, Baicar, Tyler wrote:
Hello Suzuki,
On 10/13/2016 2:50 AM, Suzuki K Poulose wrote:
On 12/10/16 23:10, Baicar, Tyler wrote:
Please could you keep the people who reviewed/commented on your series in the
past,
whenever you post a new version ?
Do you mean to just send the ne
On 10/14/16 17:42, Lorenzo Pieralisi wrote:
> On Fri, Oct 14, 2016 at 05:27:58PM +0200, Laszlo Ersek wrote:
>> On 10/14/16 17:01, Laszlo Ersek wrote:
>>
>>> Maybe the code I
>>> tried to analyze in this email was never *meant* to associate CPU#0 with
>>> any NUMA node at all (not even node 0); inst
Forgot to mention: I realize my motivation is very specific to Chrome
OS, however the nolinks option seemed useful also as a mitigation to
generic privilege escalation symlink attacks, for cases where
disabling symlinks/hardlinks is acceptable.
On Fri, Oct 14, 2016 at 5:50 PM, Mattias Nissler wro
On Fri, 2016-10-14 at 15:47 +0200, Greg KH wrote:
> Makes sense to me, can you forward on a patch that applies cleanly and
> I'll queue it up for the next round (after this one.)
Hope to do that later today. If it turns out I've messed things up Jens
can still speak up.
Thanks,
Paul Bolle
> I tools/ specifically, I try to use the same constructs, list.h, rbtree,
> WARN_, pr_, etc, not panic()'ing, etc.
>
> In this specific case, doing a:
>
>printf("life is hard, I give up"); exit(1);
Ok that would be just what a wrapper does, only open coded.
How about we just add helpers fo
On Fri, Oct 14, 2016 at 9:21 AM, Paul Bolle wrote:
> On Fri, 2016-10-14 at 16:08 +0200, Greg KH wrote:
>> Did you apply that patch and it worked properly for you? If so, yes,
>> I'll be glad to queue it up.
>
> Yes I did and it did.
>
> But I do find this commit as magical as they can get so I'd
Em Fri, Oct 14, 2016 at 09:36:42AM -0700, Andi Kleen escreveu:
> > I tools/ specifically, I try to use the same constructs, list.h, rbtree,
> > WARN_, pr_, etc, not panic()'ing, etc.
> >
> > In this specific case, doing a:
> >
> >printf("life is hard, I give up"); exit(1);
>
> Ok that would
On Fri, Oct 14, 2016 at 05:28:58PM +0100, Suzuki K Poulose wrote:
> On 13/10/16 20:37, Baicar, Tyler wrote:
> >On 10/13/2016 2:50 AM, Suzuki K Poulose wrote:
> >>Is it always the same endianness as that of the CPU ?
> >
> >It is a fair assumption that the firmware populating this record will
> >use
Hello, Kyle.
On Sat, Oct 08, 2016 at 06:15:14PM -0700, Kyle Sanderson wrote:
> How is this even a discussion when hard numbers, and trying any
> reproduction case easily reproduce the issues that CFQ causes. Reading
> this thread, and many others only grows not only my disappointment,
> but whenev
On 10/14/2016 05:15 AM, r...@redhat.com wrote:
> From: Rik van Riel
>
> The __{fpu,cpu}_invalidate_fpregs_state functions can only be used
> to invalidate a resource they control. Document that, and change
> the API a little bit to reflect that.
>
> Go back to open coding the fpu_fpregs_owner_c
From: Luis Oliveira
Signed-off-by: Luis Oliveira
---
drivers/i2c/busses/i2c-designware-core.c| 71 +++--
drivers/i2c/busses/i2c-designware-platdrv.c | 37 +--
2 files changed, 71 insertions(+), 37 deletions(-)
diff --git a/drivers/i2c/busses/i2c-designwa
From: Luis Oliveira
Add support in existing I2C Designware Core driver for I2C slave mode.
Refactored *_master() functions out of existing ones in the first patch
Added *_slave() functions to enable Slave mode.
Updated the description of the i2c-designware.txt and changed Kconfig to
auto enabl
From: Luis Oliveira
Signed-off-by: Luis Oliveira
---
drivers/i2c/busses/i2c-designware-core.c| 113 ++--
drivers/i2c/busses/i2c-designware-platdrv.c | 24 +++---
2 files changed, 68 insertions(+), 69 deletions(-)
diff --git a/drivers/i2c/busses/i2c-designware-core.
From: Luis Oliveira
Signed-off-by: Luis Oliveira
---
Documentation/devicetree/bindings/i2c/i2c-designware.txt | 5 -
drivers/i2c/busses/i2c-designware-platdrv.c | 4 +++-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-de
From: Luis Oliveira
Signed-off-by: Luis Oliveira
---
drivers/i2c/busses/Kconfig | 3 +-
drivers/i2c/busses/i2c-designware-core.c| 180 ++--
drivers/i2c/busses/i2c-designware-core.h| 6 +
drivers/i2c/busses/i2c-designware-platdrv.c | 33 -
On Fri, Oct 14, 2016 at 12:23:51PM -0300, Javier Martinez Canillas wrote:
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias inf
On Fri, Oct 14, 2016 at 12:23:50PM -0300, Javier Martinez Canillas wrote:
> If the driver is built as a module, autoload won't work because the module
> alias information is not filled. So user-space can't match the registered
> device with the corresponding module.
>
> Export the module alias inf
On Fri, Oct 14, 2016 at 06:22:55PM +0200, Laszlo Ersek wrote:
> On 10/14/16 17:42, Lorenzo Pieralisi wrote:
> > On Fri, Oct 14, 2016 at 05:27:58PM +0200, Laszlo Ersek wrote:
> >> On 10/14/16 17:01, Laszlo Ersek wrote:
> >>
> >>> Maybe the code I
> >>> tried to analyze in this email was never *meant
If user sets panic_on_warn, he wants kernel to panic if there is
anything barely wrong with the kernel. KASAN-detected errors
are definitely not less benign than an arbitrary kernel WARNING.
Panic after KASAN errors if panic_on_warn is set.
We use this for continuous fuzzing where we want kernel
> Il giorno 14 ott 2016, alle ore 18:40, Tejun Heo ha scritto:
>
> Hello, Kyle.
>
> On Sat, Oct 08, 2016 at 06:15:14PM -0700, Kyle Sanderson wrote:
>> How is this even a discussion when hard numbers, and trying any
>> reproduction case easily reproduce the issues that CFQ causes. Reading
>> thi
On 10/11/2016 07:44 PM, Mike Snitzer wrote:
On Tue, Oct 11 2016 at 11:44am -0400,
Heinz Mauelshagen wrote:
On 10/11/2016 05:38 PM, Andy Whitcroft wrote:
On Tue, Oct 11, 2016 at 05:04:34PM +0200, Heinz Mauelshagen wrote:
Andy,
good catch.
We should rather check for V190 support only in
On 10/14/2016 05:15 AM, r...@redhat.com wrote:
> From: Rik van Riel
>
> By moving all of the new fpu state handling into switch_fpu_finish,
> the code can be simplified some more. This does get rid of the
> prefetch, but given the size of the fpu register state on modern
> CPUs, and the amount of
The patch replaces the macro with a function (dgnc_get_board) and
substitutes the macro statement with a call to that function and a
comparison on the returned value.
This removes a checkpatch warning.
Signed-off-by: Fernando Apesteguia
---
drivers/staging/dgnc/dgnc_sysfs.c | 74 +++
DAX IO path does not support iostat, but its metadata IO path does.
Therefore, iostat shows metadata IO statistics only, which has been
confusing to users.
Add iostat support to the DAX read/write path.
Note, iostat still does not support the DAX mmap path as it allows
user applications to access
On Fri, Oct 14, 2016 at 08:36:05PM +1030, Joel Stanley wrote:
> From: Yi Li
>
> The adm1278 can optionally monitor the VOUT pin. This functionality is
> not enabled at reset, so PMON_CONFIG needs to be modified in order to
> enable it.
>
> Signed-off-by: Yi Li
> Signed-off-by: Joel Stanley
> -
On Fri, Oct 14, 2016 at 05:52:50PM +0100, luis.olive...@synopsys.com wrote:
> - is_slave = device_property_read_bool(&pdev->dev, "isslave");
Which tree is this based on? I cant see the existing isslave property in
mainline HEAD (commit 29fbff8698fc0ac1).
> +#ifndef CONFIG_ACPI
> +
On 14/10/16 03:08, Cheng Chao wrote:
> Marc,
>
> Thanks for your comments.
>
> Cheng
>
> on 10/13/2016 11:31 PM, Marc Zyngier wrote:
>> On Thu, 13 Oct 2016 18:57:14 +0800
>> Cheng Chao wrote:
>>
>>> GIC can distribute an interrupt to more than one cpu,
>>> but now, gic_set_affinity sets only
On Fri, Oct 14, 2016 at 10:25 AM, Toshi Kani wrote:
> DAX IO path does not support iostat, but its metadata IO path does.
> Therefore, iostat shows metadata IO statistics only, which has been
> confusing to users.
>
> Add iostat support to the DAX read/write path.
>
> Note, iostat still does not s
From: Tony Luck
If you edit a kernfs backed file with vi(1), you see an ugly error
message when you write the file because vi tries to fsync(2) the
file after writing, which fails.
We have noop_fsync() for this, use it.
Signed-off-by: Tony Luck
---
fs/kernfs/file.c | 1 +
1 file changed, 1 in
the tag at all (Bottomley, for
example, tends to have just something like "scsi-20161014" in his tag)
and then the explanation and summary in the email.
All of those options are _fine_. I don't really mind much one way or
the other. But what I don't want in *either* the tag
Th 10/13/2016 22:34, Christoph Hellwig wrote:
> > Style wise you can further remove the extra parens around
> > SCpnt->device->tagged_supported
> > As well as the now redundant braces.
>
> I did send a patch looking just like that earlier :)
I'll remove the patch from the patchset. I must have
(Resending with proper mailing lists included)
PVH v2 support for unprivileged guests.
Previous version was posted long time ago. Major changes:
1. Drop PVH v1 support
2. Enable ACPI. This allows us to use much more of native code and
results in making this series much simpler (for example, PV
301 - 400 of 536 matches
Mail list logo
