On Thu, Jul 23, 2015 at 2:56 PM, Andy Lutomirski wrote:
> native_load_sp0 relies on this. I'm not sure why we haven't seen
> reports of crashes. Maybe no one tests new kernels on non-SEP CPUs.
It's already statically initialized in cpu_tss.
--
Brian Gerst
--
To unsubscribe from this list:
On Thu, Jul 23, 2015 at 01:33:36PM -0400, Jason Baron wrote:
> > That would be bad, how can we force it to emit 5 bytes?
> hmmI don't think that's an issue, the patching code can
> detect if its a 2-byte jump - 0xeb, or 5-byte: 0xe9, and do
> the correct no-op. Same going the other way. See
On Thu, Jul 23, 2015 at 07:54:36PM +0200, Borislav Petkov wrote:
> On Thu, Jul 23, 2015 at 07:08:11PM +0200, Peter Zijlstra wrote:
> > That would be bad, how can we force it to emit 5 bytes?
>
> .byte 0xe9 like we used to do in static_cpu_has_safe().
Like so then?
static __always_inline bool
Show frequency, CPU Utilization and percent performance for each symbol
in perf report by --stdio --show-freq-perf
In sampling group, only group leader do sampling. So only need to print
group leader's freq in --group.
Here is an example.
$ perf report --stdio --group --show-freq-perf
Save group read results from cycles/ref-cycles/TSC/ASTATE/MSTATE in
struct perf_sample. The following sample process function can easily
use them to caculate freq/CPU%/CORE_BUSY% and add them in hists.
Signed-off-by: Kan Liang
---
tools/perf/util/event.h | 11 +++
Get cpu max frequency from the first online cpu, and save the MHz value
in get_cpu_max_freq.
Signed-off-by: Kan Liang
---
tools/perf/builtin-report.c | 2 ++
tools/perf/util/cpumap.c| 32
tools/perf/util/cpumap.h| 2 ++
3 files changed, 36
.alert() is meant to be generic, but there is currently no way
for the device driver to know which protocol generated the alert.
Add a parameter in .alert() to help the device driver to understand
what is given in data.
This patch is required to have the support of SMBus Host Notify protocol
As of cf991de2f614 ("x86/asm/msr: Make wrmsrl_safe() a function"),
wrmsrl_safe is a function, but wrmsrl is still a macro. The wrmsrl
macro performs invalid shifts if the value argument is 32 bits.
This makes it unnecessarily awkward to write code that puts an
unsigned long into an MSR.
To make
native_load_sp0 relies on this. I'm not sure why we haven't seen
reports of crashes. Maybe no one tests new kernels on non-SEP CPUs.
Signed-off-by: Andy Lutomirski
---
Of course, I haven't tested on a non-SEP CPU either. Where would I
find one?
arch/x86/kernel/cpu/common.c | 19
SMBus Host Notify allows a slave device to act as a master on a bus to
notify the host of an interrupt. On Intel chipsets, the functionality
is directly implemented in the firmware. We just need to export a
function to call .alert() on the proper device driver.
i2c_handle_smbus_host_notify()
The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
in
http://www.intel.com/content/dam/doc/datasheet/82801ca-io-controller-hub-3-datasheet.pdf
Enable the functionality unconditionally and propagate the alert
on each notification.
With a T440s and a Synaptics touchpad that
Hi,
this is the v4 of this patch series which fixes the race we discovered this
week when accessing the registers in i2c_i801.
Compared to v3, i2c_handle_smbus_host_notify can now be called in a non sleeping
thread because a worker will be spawn later on.
That also means that we need to allocate
Od Dr. Harry Thomas
Brondesbury, North West
Londýn Anglicko
Drahý Priateľovi.
Som doktor Harry Thomas z Brondesbury, North West London, tu v Anglicku.
Pracujem pre UBS Investment Bank v Londýne. Píšem vám o návrhu, obchodné, ktorá
bude z obrovskej prínos pre nás oboch. V mojom oddelení,
On Thu, Jul 23, 2015 at 11:42 AM, Andy Lutomirski wrote:
>
> On third thought, no v2. It's *64-bit* CPUs that might want the
> _safe. We aren't currently checking SEP. Maybe there's a non-SEP AMD
> CPU and we never noticed because SEP was never useful on AMD 64-bit
> CPUs.
I don't see the
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-4.01 - man pages for Linux
This release includes two new man pages and makes changes
in over 100 other pages, based on input and contributions from
nearly 50 people.
Tarball download:
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
>> Something new in kernel 4.2 seems to have broken one of my hard drives
>> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
>> relevant logs.
>>
> ...
On Thu, Jul 23, 2015 at 11:33 AM, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 11:01 AM, Andy Lutomirski wrote:
>> On Thu, Jul 23, 2015 at 10:27 AM, Brian Gerst wrote:
>>> On Thu, Jul 23, 2015 at 12:02 PM, Andy Lutomirski
>>> wrote:
On Thu, Jul 23, 2015 at 8:56 AM, Steven Rostedt
From: Roland Dreier
In a performance profile, taking a mutex in iscsit_increment_maxcmdsn()
shows up very high. However taking a mutex around "sess->max_cmd_sn += 1"
seems pretty silly: we're not serializing against other contexts in
any useful way.
I did a quick audit and there don't appear
From: Alexander Usyskin
For the FW with HBM version >= 2.0 we don't need to reset the whole
device in case of a particular client failing to connect, it is enough
to send disconnect a request to bring the device to the stable state.
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas
HBM version 2.0 and above allows ME clients in the system to
register/unregister after the system is fully initialized.
Clients may be added or removed after enum_resp message was
received
1. To preserve backward compatibility the driver can opt-in to receive
client add messages by setting
On Thu, Jul 23, 2015 at 08:10:07PM +0200, Jakub Sitnicki wrote:
> On Thu, Jun 18, 2015 at 08:31 AM CEST, Jakub Sitnicki
> wrote:
> > Flag is never set. Remove it and the code that is dead because of it.
> >
> > Signed-off-by: Jakub Sitnicki
> > ---
>
> Looks like this patch got lost in the
On Thu, Jul 23, 2015 at 08:11:03PM +0200, Jakub Sitnicki wrote:
> On Wed, Jun 24, 2015 at 07:23 AM CEST, Jakub Sitnicki
> wrote:
> > linux/ieee80211.h already defines constants for information element IDs.
> > Include it where needed, resolve discrepancies in naming, and remove the
> >
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
> Something new in kernel 4.2 seems to have broken one of my hard drives
> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
> relevant logs.
>
...
> [6.547628] ata2.00: qc timeout (cmd 0xec)
> [
On Thu, Jul 23, 2015 at 11:01 AM, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 10:27 AM, Brian Gerst wrote:
>> On Thu, Jul 23, 2015 at 12:02 PM, Andy Lutomirski
>> wrote:
>>> On Thu, Jul 23, 2015 at 8:56 AM, Steven Rostedt wrote:
On Thu, 23 Jul 2015 08:31:39 -0700
Andy
On 07/23/2015 07:40 AM, Naoya Horiguchi wrote:
> Nowaday, set/unset_migratetype_isolate() is defined and used only in
> mm/page_isolation, so let's limit the scope within the file.
>
> Signed-off-by: Naoya Horiguchi
Acked-by: Vlastimil Babka
> ---
> include/linux/page-isolation.h | 5 -
>
Hello, Tang.
On Thu, Jul 23, 2015 at 12:44:53PM +0800, Tang Chen wrote:
> Allocating cpuid when a new cpu comes up and reusing the cpuid when it
> comes up again is possible. But I'm not quite sure if it will be less
> modification
> because we still need an array or bit map or something to keep
On Thu, Jul 23, 2015 at 02:27:09PM -0400, Tejun Heo wrote:
> bio_associate_blkcg(), bio_associate_current() and wbc_account_io()
> are used to implement cgroup writeback support for filesystems and
> thus need to be exported. Export them.
Thanks, these were the only three I needed on the btrfs
bio_associate_blkcg(), bio_associate_current() and wbc_account_io()
are used to implement cgroup writeback support for filesystems and
thus need to be exported. Export them.
Signed-off-by: Tejun Heo
Reported-by: Stephen Rothwell
---
Hello, Jens.
While this change isn't strictly necessary for
On 07/22/2015 07:33 PM, Alban Bedel wrote:
diff --git a/arch/mips/jz4740/gpio.c b/arch/mips/jz4740/gpio.c
index 54c80d4..3dc500c 100644
--- a/arch/mips/jz4740/gpio.c
+++ b/arch/mips/jz4740/gpio.c
@@ -262,18 +262,6 @@ uint32_t jz_gpio_port_get_value(int port, uint32_t mask)
}
On 07/23/2015 09:52 AM, Mark Rutland wrote:
[...]
+MSI clients
+===
+
+MSI clients are devices which generate MSIs. For each MSI they wish to
+generate, the doorbell and payload may be configured, though sideband
+information may not be configurable.
+
+Required properties:
When we open a device file descriptor, we currently have the
following:
vfio_group_get_device_fd()
mutex_lock(>device_lock);
open()
...
if (ret)
release()
If we hit that error case, we call the backend driver release path,
which for vfio-pci looks like this:
On Mon, 2015-07-13 at 11:35 -0400, Mike Snitzer wrote:
> On Mon, Jul 13 2015 at 1:12am -0400,
> Ming Lin wrote:
>
> > On Mon, 2015-07-06 at 00:11 -0700, m...@kernel.org wrote:
> > > Hi Mike,
> > >
> > > On Wed, 2015-06-10 at 17:46 -0400, Mike Snitzer wrote:
> > > > I've been busy getting DM
The "highlight" code is very sensible to the order of the hash keys,
but the order of the keys cannot be predicted on Perl. It generates
faulty DocBook entries like:
- @device_for_each_child
We should use an array for that job, so we can guarantee that the order
of the regex execution on
Markdown support is given by calling an external tool, pandoc, for all
highlighted text on kernel-doc.
Pandoc converts Markdown text to proper Docbook tags, which will be
later translated to pdf, html or other targets.
This adds the capability of adding human-readle text highlight (bold,
Functions, Structs and Parameters definitions on kernel documentation
are pure cosmetic, it only highlights the element.
To ease the navigation in the documentation we should use inside
those tags so readers can easily jump between methods directly.
This was discussed in 2014[1] and is
DRM Docbook is now Markdown ready. This means its doc is able to
use markdown text on it.
* Documentation/DocBook/drm.tmpl: Contains a table duplicated from
drivers/gpu/drm/i915/i915_reg.h. This is not needed anymore
* drivers/gpu/drm/drm_modeset_lock.c: had a code example that used
to look
This series add supports for hyperlink cross-references on Docbooks and
an optional markup syntax for in-source Documentation.
Danilo Cesar Lemes de Paula (4):
scripts/kernel-doc: Adding cross-reference links to html
documentation.
scripts/kernel-doc: Replacing highlights hash by an array
Em Thu, Jul 23, 2015 at 02:11:33PM -0400, Steven Rostedt escreveu:
> On Thu, 23 Jul 2015 14:10:39 -0400 Steven Rostedt wrote:
> > On Thu, 23 Jul 2015 14:25:54 -0300
> > Arnaldo Carvalho de Melo wrote:
> > > diff --git a/tools/lib/traceevent/event-parse.c
> > >
Hi Chao,
On Wed, Jul 22, 2015 at 06:21:52PM +0800, Chao Yu wrote:
> Firstly, spliting init_inode_metadata into two parts as below since they
> are relatively independent.
> 1) init_inode_metadata: init datas belong to newly created inode;
> 2) update_inode_metadata: update inode info for linking
On Thu, 23 Jul 2015 13:33:36 -0400
Jason Baron wrote:
> On 07/23/2015 01:08 PM, Peter Zijlstra wrote:
> > On Thu, Jul 23, 2015 at 11:34:50AM -0400, Steven Rostedt wrote:
> >> On Thu, 23 Jul 2015 12:42:15 +0200
> >> Peter Zijlstra wrote:
> >>
> >>> static __always_inline bool
We were previously using free_bootmem() and just getting lucky
that nothing too bad happened.
Signed-off-by: Chris Metcalf
Cc: sta...@vger.kernel.org
---
arch/tile/kernel/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/tile/kernel/setup.c
On Thu, 23 Jul 2015 14:25:54 -0300
Arnaldo Carvalho de Melo wrote:
> diff --git a/tools/lib/traceevent/event-parse.c
> b/tools/lib/traceevent/event-parse.c
> index cc25f059ab3d..2750e7e7efff 100644
> --- a/tools/lib/traceevent/event-parse.c
> +++ b/tools/lib/traceevent/event-parse.c
> @@ -418,7
On Wed, Jun 24, 2015 at 07:23 AM CEST, Jakub Sitnicki
wrote:
> linux/ieee80211.h already defines constants for information element IDs.
> Include it where needed, resolve discrepancies in naming, and remove the
> duplicated definitions.
>
> While at it, wrap a line that was too long and remove
On Thu, 23 Jul 2015 14:10:39 -0400
Steven Rostedt wrote:
> On Thu, 23 Jul 2015 14:25:54 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > diff --git a/tools/lib/traceevent/event-parse.c
> > b/tools/lib/traceevent/event-parse.c
> > index cc25f059ab3d..2750e7e7efff 100644
> > ---
On Thu, Jul 23, 2015 at 11:02:55AM -0700, Jörn Engel wrote:
> Spencer spotted something nasty in the round_up macro. We were
> wondering why round_up() worked differently from ALIGN. The only real
> difference between the two patterns is overflow behaviour. And both
> version are buggy when
On Thu, 2015-07-23 at 10:40 -0700, Dan Williams wrote:
> On Thu, Jul 23, 2015 at 10:33 AM, Toshi Kani wrote:
> > During power failure, Asynchronous DRAM Refresh (ADR) flushes
> > the write buffer in memory controllers into NVDIMM, but does not
> > flush processor caches. While the kernel and
On Friday, July 17, 2015 10:53:26 PM Matthias Brugger wrote:
> Mediatek SoC needs the regmap/syscon infrastructure.
> The infrastructure is used by the clock and pinctrl driver.
> This patch adds MD_SYSCON to Kconfig for all Mediatek devices.
>
> Signed-off-by: Matthias Brugger
> ---
>
On Tuesday, July 14, 2015 02:58:11 PM Mars Cheng wrote:
> This patch adds basic chip support for Mediatek 8-core chip, mt6795.
> It is also named as Helio X10. It is based on:
> 1. 4.2-rc1
> 2. [PATCH v4 0/2] Add mt6580 basic chip support
>
> The second one has added some device tree binding
On Thu, Jul 23, 2015 at 10:27 AM, Brian Gerst wrote:
> On Thu, Jul 23, 2015 at 12:02 PM, Andy Lutomirski wrote:
>> On Thu, Jul 23, 2015 at 8:56 AM, Steven Rostedt wrote:
>>> On Thu, 23 Jul 2015 08:31:39 -0700
>>> Andy Lutomirski wrote:
>>>
Switch from wrmsr to wrmsrl_safe to prepare to
On Thu, Jul 23, 2015 at 12:02:06PM +0800, Minfei Huang wrote:
> On 07/22/15 at 09:40am, Josh Poimboeuf wrote:
> > Is it really safe to assume that there are no dependencies between
> > patches which patch different objects?
> >
>
> I think so.
What about the following scenario:
1. register and
On Thu, Jul 23, 2015 at 12:02:40AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jul 22, 2015 at 08:14:46PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Jul 22, 2015 at 09:04:40PM -0500, Felipe Balbi wrote:
> > > On Wed, Jul 22, 2015 at 02:39:34PM -0700, Greg Kroah-Hartman wrote:
> > > > On Tue,
Spencer spotted something nasty in the round_up macro. We were
wondering why round_up() worked differently from ALIGN. The only real
difference between the two patterns is overflow behaviour. And both
version are buggy when used for signed integer types, round_up will
underflow on INT_MIN,
Current implemantation ptr argument evaluate 2 times.
It'll be an unexpected result.
Changes v5:
Remove unnecessary const.
Changes v4:
Temporary pointer type change to const void*
Changes v3:
Some build error fix.
Changes v2:
Argument x protect.
Signed-off-by: Yoshinori Sato
---
On Thu, Jul 23, 2015 at 07:08:11PM +0200, Peter Zijlstra wrote:
> That would be bad, how can we force it to emit 5 bytes?
.byte 0xe9 like we used to do in static_cpu_has_safe().
Or you can copy the insn sizing from the alternatives macros which I
added recently.
--
Regards/Gruss,
Boris.
On 07/23/15 02:17, Johannes Thumshirn wrote:
> Change men-chameleon-bus.txt according to the comments made by Randy Dunlap in
> https://lkml.org/lkml/2015/7/17/691.
>
> These are:
> * Some minor gramatical changes
> * Spelling fixes
> * Write the word "Chameleon" capitalized throughout the whole
On Thu, Jul 23, 2015 at 05:47:44PM +0100, Guenter Roeck wrote:
> On 07/23/2015 09:12 AM, Bjorn Helgaas wrote:
> > On Thu, Jul 09, 2015 at 11:59:16AM +0100, Lorenzo Pieralisi wrote:
> >> When a PCI bus is scanned, upon PCI bridge detection the kernel
> >> has to read the bridge registers to set-up
On 07/22/15 23:57, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150722:
>
on x86_64:
when CONFIG_I2C=m and
CONFIG_SERIAL_SC16IS7XX_CORE=y
CONFIG_SERIAL_SC16IS7XX=y
CONFIG_SERIAL_SC16IS7XX_I2C=y
CONFIG_SERIAL_SC16IS7XX_SPI=y
drivers/built-in.o: In function `sc16is7xx_i2c_probe':
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
relevant logs.
Kernel 4.1:
[1.435809] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.435837] ata1: SATA link up 3.0 Gbps (SStatus 123
On Thu, Jul 23, 2015 at 05:12:57PM +0100, Bjorn Helgaas wrote:
> On Thu, Jul 09, 2015 at 11:59:16AM +0100, Lorenzo Pieralisi wrote:
> > When a PCI bus is scanned, upon PCI bridge detection the kernel
> > has to read the bridge registers to set-up its resources so that
> > the PCI resource
Pali,
On 07/23/2015 11:20 AM, Pali Rohár wrote:
> On Wednesday 22 July 2015 16:51:59 Andrew F. Davis wrote:
>> Add support for additional devices and register equivalent family devices
>> including the bq27010, bq27210, bq272500, bq27510, bq27520, bq27530,
>> bq27531, bq27541, bq27542, bq27546,
On Thu, Jul 23, 2015 at 01:23:43PM -0400, Theodore Ts'o wrote:
> On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
> > > After merging the ext4 tree, today's linux-next build (x86_64
> > > allmodconfig) failed like this:
> > >
> > > ERROR: "wbc_account_io" [fs/ext4/ext4.ko]
On Thu, Jul 23, 2015 at 10:33 AM, Toshi Kani wrote:
> During power failure, Asynchronous DRAM Refresh (ADR) flushes
> the write buffer in memory controllers into NVDIMM, but does not
> flush processor caches. While the kernel and application code
> need to take care of processor cache flush,
On Thursday, July 23, 2015 01:49:11 PM Eddie Huang wrote:
> From: Greta Zhang
>
> Without .shutdown(), watchdog might reset the system during power off.
> For example, if watchdog's timeout is set to 30s, then it is reset to
> zero by mtk_wdt_ping(). During power off, no app will ping watchdog,
On Thursday, July 23, 2015 01:49:10 PM Eddie Huang wrote:
> From: Greta Zhang
>
> add wdt driver suspend/resume support
>
> Signed-off-by: Greta Zhang
> Signed-off-by: Roger Lu
> Signed-off-by: Eddie Huang
> ---
> drivers/watchdog/mtk_wdt.c | 30 ++
> 1 file
On Jul 23, 2015 10:08 AM, "Peter Zijlstra" wrote:
>
> On Thu, Jul 23, 2015 at 11:34:50AM -0400, Steven Rostedt wrote:
> > On Thu, 23 Jul 2015 12:42:15 +0200
> > Peter Zijlstra wrote:
> >
> > > static __always_inline bool arch_static_branch_jump(struct static_key
> > > *key, bool inv)
> > > {
>
During power failure, Asynchronous DRAM Refresh (ADR) flushes
the write buffer in memory controllers into NVDIMM, but does not
flush processor caches. While the kernel and application code
need to take care of processor cache flush, they may not be able
to do so during panic or reboot.
Add
On 07/23/2015 01:08 PM, Peter Zijlstra wrote:
> On Thu, Jul 23, 2015 at 11:34:50AM -0400, Steven Rostedt wrote:
>> On Thu, 23 Jul 2015 12:42:15 +0200
>> Peter Zijlstra wrote:
>>
>>> static __always_inline bool arch_static_branch_jump(struct static_key *key,
>>> bool inv)
>>> {
>>> if (!inv)
Debugging input devices, specifically laptop touchpads, can be tricky
without having the physical device handy. Here we try to remedy that
with userio. This module allows an application to connect to a character
device provided by the kernel, and emulate any serio device. In
combination with
On Thu, Jul 23, 2015 at 1:59 PM, Lee Jones wrote:
>> On Fri, Jul 17, 2015 at 5:34 PM, Lee Jones wrote:
>> > +static void sti_mbox_enable_channel(struct mbox_chan *chan)
>> > +{
>> > + struct sti_channel *chan_info = chan->con_priv;
>> > + struct sti_mbox_device *mdev =
Since both CONFIG_ACPI and CONFIG_CLKSRC_OF can be enabled on ARM64,
we get this device tree warnings even when booting using ACPI which is
not valid. We can use of_have_populated_dt to check if the device tree
is populated or not and avoid spurious warning.
This patch uses of_have_populated_dt
On 07/23/2015 10:17 AM, Eric B Munson wrote:
On Thu, 23 Jul 2015, Mike Kravetz wrote:
On 07/23/2015 08:17 AM, Eric B Munson wrote:
On Wed, 22 Jul 2015, Mike Kravetz wrote:
On 07/22/2015 03:30 PM, Andrew Morton wrote:
On Wed, 22 Jul 2015 15:19:54 -0700 Davidlohr Bueso wrote:
I didn't
On 07/22/15 23:57, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150722:
>
on x86_64:
../sound/soc/codecs/sti-sas.c: In function 'stih416_dac_probe':
../sound/soc/codecs/sti-sas.c:227:2: error: implicit declaration of function
'devm_reset_control_get'
On Thu, Jul 23, 2015 at 12:02 PM, Andy Lutomirski wrote:
> On Thu, Jul 23, 2015 at 8:56 AM, Steven Rostedt wrote:
>> On Thu, 23 Jul 2015 08:31:39 -0700
>> Andy Lutomirski wrote:
>>
>>> Switch from wrmsr to wrmsrl_safe to prepare to merge the 32-bit and
>>> 64-bit code, and use __KERNEL_CS
> I understand the value of the tsc and smi events. It is not
> clear to me what aperf/mperf buys you over cycles and ref-cycles:
>
> $ perf stat -a -e msr/aperf/,msr/mperf/,cycles,ref-cycles -C 1 -I 1000 sleep
> 10
> # time counts unit events
> 2.000361718
[+cc Matthew for PCIe-SSD perspective]
On Wed, Jul 22, 2015 at 03:07:46PM -0500, Jordan Hargrave wrote:
> On Tue, Jul 21, 2015 at 8:09 PM, Bjorn Helgaas wrote:
> > On Tue, Jul 21, 2015 at 12:31:35PM -0500, Jordan Hargrave wrote:
> >> On Tue, Jul 21, 2015 at 11:57 AM, Bjorn Helgaas
> >> wrote:
When the the sensor data uses 32 bits out of 32, generic_buffer prints
the value 0 for all data read.
In this case, the mask is shifted 32 bits, which is beyond the size of
an integer. This will lead to the mask always being 0. Before printing,
the mask is applied to the raw value, thus
Running generic_buffer without enabling any channel of the
sensor will fail without printing any error message.
Add an error message that indicates buffer enable failed.
Signed-off-by: Irina Tirdea
---
tools/iio/generic_buffer.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
Em Thu, Jul 23, 2015 at 12:21:30PM -0400, Steven Rostedt escreveu:
> On Thu, 23 Jul 2015 12:04:33 -0300 Arnaldo Carvalho de Melo
> wrote:
> > +static struct func_map *
> > +find_func(struct pevent *pevent, unsigned long long addr)
> > +{
> > + static struct func_map map;
> I know there's
On Thu, Jul 09, 2015 at 06:34:23PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> dma_alloc_writecombine()'s call and return value check is tangled in all
> in one call. Untangle both calls according to kernel coding style.
>
This looks okay, does it have dependency on anything
On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
> > After merging the ext4 tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > ERROR: "wbc_account_io" [fs/ext4/ext4.ko] undefined!
> > ERROR: "bio_associate_blkcg" [fs/ext4/ext4.ko] undefined!
> >
> >
Fixes for a couple of small issues found while testing the
bmc150_magn driver.
Irina Tirdea (2):
tools: iio: fix mask for 32 bit sensor data
tools: iio: print error message when buffer enable fails
tools/iio/generic_buffer.c | 5 -
tools/iio/iio_utils.c | 2 +-
2 files changed, 5
On Thu, 23 Jul 2015, Vinod Koul wrote:
> On Wed, Jul 22, 2015 at 03:26:01PM +0100, Alex Smith wrote:
>
> > >>>I think the explicit devm_free_irq() here is unnecessary, as when remove
> > >>>is
> > >>>called there should be no remaining users of the DMA controller and
> > >>>therefore
> >
Hi Alex,
On Thu, Jul 23, 2015 at 11:07:37AM -0600, Alex Williamson wrote:
> Thanks for the report. I think I found it. I'll do further testing
> myself, but would appreciate if you're able to see if this clears the
> problem. Thanks,
Just tested it and the lockdep warning is gone. Thanks for
Hi Lee,
On Fri, Jul 17, 2015 at 3:04 PM, Lee Jones wrote:
> ST's platforms currently support a maximum of 5 Mailboxes, one for
> each of the supported co-processors situated on the platform. Each
> Mailbox is divided up into 4 instances which consist of 32 channels.
> Messages are passed
Hi Viresh,
On Thu, Jul 23, 2015 at 8:09 AM, Viresh Kumar wrote:
> On 22-07-15, 18:42, Rafael J. Wysocki wrote:
>> > 3. what happens when 'policy' is NULL at the point when the first (few)
>> > CPUs
>> >are added - how do the symlinks get created later if/when policy becomes
>> >non-NULL
Hi Stefano,
On 16/07/15 16:11, Stefano Stabellini wrote:
> On Thu, 9 Jul 2015, Julien Grall wrote:
>> All the usage of the field pfn are done using the same idiom:
>>
>> pfn_to_page(grant->pfn)
>>
>> This will return always the same page. Store directly the page in the
>> grant to clean up the
On 07/23/2015 11:15 AM, Pali Rohár wrote:
> On Wednesday 22 July 2015 16:51:58 Andrew F. Davis wrote:
>> Fix typos and change "relative state of charge" to "state of charge" as not
>> all supported devices use relative state of charge.
>>
>> Signed-off-by: Andrew F. Davis
>> ---
>>
On Wed, Jul 22, 2015 at 03:26:01PM +0100, Alex Smith wrote:
> >>>I think the explicit devm_free_irq() here is unnecessary, as when remove is
> >>>called there should be no remaining users of the DMA controller and
> >>>therefore
> >>>no chance of an IRQ occurring between the controller being
On Thu, 23 Jul 2015 19:08:11 +0200
Peter Zijlstra wrote:
> On Thu, Jul 23, 2015 at 11:34:50AM -0400, Steven Rostedt wrote:
> > On Thu, 23 Jul 2015 12:42:15 +0200
> > Peter Zijlstra wrote:
> >
> > > static __always_inline bool arch_static_branch_jump(struct static_key
> > > *key, bool inv)
> >
On Thu, 23 Jul 2015, Mike Kravetz wrote:
> On 07/23/2015 08:17 AM, Eric B Munson wrote:
> >On Wed, 22 Jul 2015, Mike Kravetz wrote:
> >
> >>On 07/22/2015 03:30 PM, Andrew Morton wrote:
> >>>On Wed, 22 Jul 2015 15:19:54 -0700 Davidlohr Bueso
> >>>wrote:
> >>>
> >
> >I didn't know that
On Thu, Jul 23, 2015 at 09:41:28AM -0700, Bjorn Andersson wrote:
> > We still need Mark to look at this.
> Mark, would you mind giving us a statement on the regulator subnode of
> this binding?
I have no idea what's going on here, sorry. I've not been reading this
thread.
signature.asc
A couple of small cleanup patches starting from Hartmut's series.
There are no conflicts with the rest of Hartmut's patches, so they
can be applied in any order.
Irina Tirdea (2):
iio: magn: bmc150_magn: add locking comment for runtime resume
iio: magn: bmc150_magn: do not set power state
When setting the trigger state, the device power state is set through
buffer preenable and postdisable hooks. There is no need
to also set it in the trigger set state call.
Remove duplicate set power state from the trigger set
state call.
Signed-off-by: Irina Tirdea
---
Runtime resume function is called with the data->mutex lock held.
Add a comment to indicate this.
Signed-off-by: Irina Tirdea
---
drivers/iio/magnetometer/bmc150_magn.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/iio/magnetometer/bmc150_magn.c
On Thu, Jul 23, 2015 at 09:55:33AM -0700, Dave Hansen wrote:
> On 07/23/2015 09:16 AM, Catalin Marinas wrote:
> > Anyway, if you want to keep the option of a full TLB flush for x86 on
> > huge pages, I'm happy to repost a v2 with a separate
> > flush_tlb_pmd_huge_page that arch code can define as
Really same as previous pull, but as a problem was found in that one, I
rebased and fixed.
The following changes since commit 59a5b0f7bf74f88da6670bcbf924d8cc1e75b1ee:
virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200)
are available in the git repository at:
On Jun 23 2015 or thereabouts, Benjamin Tissoires wrote:
> Hi Dmitry,
>
> As mentioned in the thread on linux-i2c[1], I am making good progress on the
> RMI4 SMBus implementation [2].
> I am still missing the PS/2 pass-through function but I have an intern
> (Chandler,
> CC-ed) working on that.
Linux 4.1 added the possibility of perf_event_open() returning
EBUSY if an existing exclusive event controls the PMU.
This was introduced by the following commit:
commit bed5b25ad9c8a2f5d735ef0bc746ec870c01c1b0
Author: Alexander Shishkin
Date: Fri Jan 30 12:31:06 2015
On Wed, 22 Jul 2015, Dave Chinner wrote:
> On Wed, Jul 22, 2015 at 10:09:23AM +1000, Dave Chinner wrote:
> > On Tue, Jul 21, 2015 at 01:47:53PM -0400, Mike Snitzer wrote:
> > > On Tue, Jul 21 2015 at 11:34am -0400, Eric Sandeen
> > > wrote:
> > > > On 7/20/15 5:36 PM, Dave Chinner wrote:
> >
The rdpmc instruction allows reading performance counters directly
from usersapce. Prior to Linux 4.0 any process could use this
instruction when a perf event was running, even if the process itself
did not have any open. The following changesets changed the default
behavior so that only
301 - 400 of 1842 matches
Mail list logo
