On Wed, May 28, 2014 at 12:07:28PM +1000, Stephen Rothwell wrote:
> Hi Bruce,
>
> After merging the nfsd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
>
> fs/nfsd/nfs4xdr.c: In function 'nfsd4_encode_security_label':
> fs/nfsd/nfs4xdr.c:1945:15: error: 'pp' undeclare
On Wed, May 28, 2014 at 10:51:04AM -0500, Alex Thorlton wrote:
[..]
> A side note, though: We're going to have to figure out some way to
> determine whether or not to apply the old_map quirk on during boot
> anyway, so if it's easiest for you to just determine how the original
> kernel was booted
On Wed, 2014-05-28 at 12:00 -0600, Bjorn Helgaas wrote:
> On Thu, May 22, 2014 at 05:08:01PM -0600, Alex Williamson wrote:
> > Several PCIe-to-PCI bridges fail to provide a PCIe capability, causing
> > us to handle them as conventional PCI devices. In some cases, this
> > may be correct, in others
On Wed, May 28, 2014 at 09:59:54AM -0700, Kees Cook wrote:
> On Wed, May 28, 2014 at 4:42 AM, Djalal Harouni wrote:
> > On Tue, May 27, 2014 at 11:38:54AM -0700, Kees Cook wrote:
> >> On Mon, May 26, 2014 at 6:27 AM, Djalal Harouni wrote:
> >> > Add the deny or allow flags, so we can perform prop
On Tue, May 20, 2014 at 02:05:50PM -0700, Joe Perches wrote:
> Add format and argument checking and fix misuses in the dbg macro.
>
> Add __printf
> Use %pR for resource
> Add #include guard to samsung.h
> Move static functions from .h to .c
> Use vscnprintf instead of length unguarded vsprintf
>
On Wed, May 28, 2014 at 12:27:13PM -0700, Greg Kroah-Hartman wrote:
> On Tue, May 20, 2014 at 02:05:50PM -0700, Joe Perches wrote:
> > Add format and argument checking and fix misuses in the dbg macro.
> >
> > Add __printf
> > Use %pR for resource
> > Add #include guard to samsung.h
> > Move stati
On Wed, 2014-05-28 at 21:55 +0300, Dmitry Kasatkin wrote:
> On 28 May 2014 18:09, Mimi Zohar wrote:
> > Require all keys added to the IMA keyring be signed by an
> > existing trusted key on the system trusted keyring.
> >
> > Changelog v1:
> > - don't link IMA trusted keyring to user keyring
> >
On 05/28/2014 10:28 PM, Vasily Kulikov wrote:
> On Wed, May 28, 2014 at 16:44 +0400, Pavel Emelyanov wrote:
>> On 05/28/2014 02:24 PM, Chen Hanxiao wrote:
>>> We need a direct method of getting the pid inside containers.
>>
>> But there's more generic issue -- some day we'll need to know not only
>
On Wed, May 28, 2014 at 07:05:31PM +0200, Peter Zijlstra wrote:
> If we get the PMI (where denoted) we can actually reconstruct which
> event triggered, by looking at which bit(s) flipped between the recorded
> state and the current state (due to E coming before F)
>
just a bit flip (xor) isn't e
Commit-ID: 397335f004f41e5fcf7a795e94eb3ab83411a17c
Gitweb: http://git.kernel.org/tip/397335f004f41e5fcf7a795e94eb3ab83411a17c
Author: Thomas Gleixner
AuthorDate: Thu, 22 May 2014 03:25:39 +
Committer: Thomas Gleixner
CommitDate: Wed, 28 May 2014 17:28:13 +0200
rtmutex: Fix deadloc
On 28 May 14 12:27, Will Deacon wrote:
> Hi Larry,
>
> On Mon, May 26, 2014 at 07:56:12PM +0100, Larry Bassel wrote:
> > To implement the context tracker properly on arm64,
> > a function call needs to be made after debugging and
> > interrupts are turned on, but before the lr is changed
> > to po
Viresh,
On Wed, May 21, 2014 at 1:59 AM, Viresh Kumar wrote:
> @@ -1841,9 +1876,23 @@ static int __target_index(struct cpufreq_policy
> *policy,
> pr_err("%s: Failed to change cpu frequency: %d\n", __func__,
>retval);
>
> - if (notify)
> + if (
regulator_get_optional() doesn't hold an exclusive reference to
the regulator. Fix the documentation and reword the exclusive
documentation to fix the grammatical error "this reference is
held".
Signed-off-by: Stephen Boyd
---
drivers/regulator/core.c | 11 ---
1 file changed, 4 insertio
On Wed, May 28, 2014 at 11:39 AM, Al Viro wrote:
>
> OK, the warnings about averting your eyes very much apply; the thing below
> definitely needs more massage before it becomes acceptable
I've been looking at the this too, and I have to say, I absolutely
hate your DCACHE_MAY_FREE logic. It makes
On Wednesday 28 May 2014 17:21:51 Joel Porquet wrote:
> asm-generic/uaccess.h defines 'strncpy_from_user', 'strnlen_user' and
> 'strlen_user' as static inline functions. It makes it impossible for an
> arch to include asm-generic/uaccess.h and benefits from its content, in
> addition to defining GE
On 05/28/14 10:12, Mark Brown wrote:
> On Wed, May 28, 2014 at 05:16:46PM +0200, Uwe Kleine-König wrote:
>> On Tue, May 27, 2014 at 02:40:15PM -0700, Stephen Boyd wrote:
>>> On 05/24/14 05:48, Mark Brown wrote:
So, according to the datasheet I managed to find this device has a
supply VDD_
Hello Mark,
On 27/05/2014 21:49, Mark Brown wrote:
> On Tue, May 27, 2014 at 11:38:49AM +0200, Boris BREZILLON wrote:
>
>> I'm still waiting for inputs regarding the ipsout regulator representation:
> If you've got questions you need an answer to urgently it's possibly
> best to highlight them ou
Hi,
Some days ago, I was alerted that under important network load, something
is going wrong with perf_event sampling in frequency mode (such as perf top).
The number of samples was way too low given the cycle count (via perf stat).
Looking at the syslog, I noticed that the perf irq latency thrott
On Wed, May 28, 2014 at 12:44:35PM -0700, Stephen Boyd wrote:
> On 05/28/14 10:12, Mark Brown wrote:
> > If the supply must always be physically present the bindings should be
> > specified as it being mandatory and the code written in that fashion; as
> > an extension Linux will put a dummy in bu
Em Wed, May 28, 2014 at 03:17:40PM +, David Laight escreveu:
> From: Arnaldo Carvalho de Melo
> ...
> > > But, another question...
> > >
> > > In the case that the call is interrupted by a signal handler and some
> > > datagrams have already been received, then the call succeeds, and
> > > retu
On 5/26/2014 5:59 PM, Daniel Walter wrote:
From: Daniel Walter
Subject: [PATCH 01/12] [arch/tile] replace strict_strto* call with kstrto*
remove obsolete calls to strict_strto* and replace them
with kstrto* calls accordingly.
Signed-off-by: Daniel Walter
---
arch/tile/kernel/setup.c | 7 ++--
> Another explanation is that because we ACK the NMI early, we leave the
> door open to other interrupts, incl. NIC, and we are interrupting the
> execution
PMI executes with interrupts off.
> of the PMU IRQ handler, yet that detour is measured in the PMU handler
> latency, causing more throttl
On Wed, May 28, 2014 at 9:55 PM, Andi Kleen wrote:
>
>> Another explanation is that because we ACK the NMI early, we leave the
>> door open to other interrupts, incl. NIC, and we are interrupting the
>> execution
>
> PMI executes with interrupts off.
>
And that's coming from where?
>> of the PMU
On Wed, May 14, 2014 at 03:55:32PM +0100, Daniel Thompson wrote:
> The behaviour of the UART poll_put_char infrastructure is inconsistent
> with respect to linefeed conversions. This in turn leads to difficulty
> using kdb on serial ports that are not also consoles
> (e.g. console=ttyAMA0,115200 kg
On 05/27/2014 11:52 PM, Heesub Shin wrote:
> Hi,
>
> Here is my patchset with some modification, hoping reviews or comments
> from you guys.
>
> v2:
> o No changes in the code, just reworded changelog
> o Reorder patch
Ran this through Colin's ion-unit-tests and saw no changes in the
results on
This patch moves most data allocated in the probe function from
unmanaged interfaces to managed interfaces. The kfrees and error
handling code is done away with. Also, the unnecesary labels are
removed and the function pm860x_onkey_remove is removed as it becomes
empty after removing the no longer
On Wed, May 28, 2014 at 12:43 PM, Linus Torvalds
wrote:
> - the shrinker list logic depends on the actual freeing of the dentry
> to be delayed until the RCU grace period (already true for RCU-lookup
> dentries)
Side note: I just unconditionally removed the immediate __d_free()
case, but it coul
On Thu, May 1, 2014 at 1:04 PM, Murali Karicheri wrote:
> 8250 uart driver currently supports only software assisted hw flow
> control. The software assisted hw flow control maintains a hw_stopped
> flag in the tty structure to stop and start transmission and use modem
> status interrupt for the e
On Wed, May 28, 2014 at 09:56:35PM +0200, Stephane Eranian wrote:
> On Wed, May 28, 2014 at 9:55 PM, Andi Kleen wrote:
> >
> >> Another explanation is that because we ACK the NMI early, we leave the
> >> door open to other interrupts, incl. NIC, and we are interrupting the
> >> execution
> >
> >
This patch moves most data allocated in the probe function from
unmanaged interfaces to managed interfaces. The kfrees and error
handling code is done away with. Also, the unnecesary labels are
removed and the function pm860x_touch_remove is removed as it becomes
empty after removing the no longer
Hi,
On Tue, May 27, 2014 at 12:16:30PM +0800, Li Zefan wrote:
> On 2014/5/21 13:36, Yong Zhang wrote:
> > asid_cache must be unsigned long otherwise on 64bit system
> > it will become 0 if the value in get_new_mmu_context()
> > reaches 0x and in the end the assumption of
> > ASID_FIRST_VER
On Tue, May 27, 2014 at 02:09:21PM +0900, Yoshihiro YUNOMAE wrote:
> Add tunable RX interrupt trigger I/F of FIFO buffers.
>
> Serial devices are used as not only message communication devices but control
> or sending communication devices. For the latter uses, normally small data
> will be exchan
This patch moves most data allocated in the probe function from
unmanaged interfaces to managed interfaces. The kfrees and error
handling code is done away with. The unnecesary labels are removed
and the function max8925_onkey_remove is removed as it becomes empty
after removing the no longer requi
On Wed, May 28, 2014 at 03:04:00PM -0400, Vivek Goyal wrote:
> On Wed, May 28, 2014 at 10:51:04AM -0500, Alex Thorlton wrote:
>
> [..]
> > A side note, though: We're going to have to figure out some way to
> > determine whether or not to apply the old_map quirk on during boot
> > anyway, so if it
On Wed, May 28, 2014 at 12:16:04PM +0200, walter harms wrote:
>
>
> Am 28.05.2014 11:11, schrieb Giedrius Rekasius:
> > Local variable "box" gets assigned correct value when it is initialized.
> > There is no need to assign the same value again.
> >
> > Signed-off-by: Giedrius Rekasius
> > ---
We shouldn't be using regulator_get_optional() here. These
regulators are always present as part of the physical design and
there isn't any way to use an internal regulator or change the
source of the reference voltage via software. Given that the only
users of this driver in the kernel are DT base
This patch moves most data allocated in the probe function from
unmanaged interfaces to managed interfaces. The kfrees and error
handling code is done away with. Also, the unnecesary labels are
removed and the function ab8500_ponkey_remove is removed as it becomes
empty after removing the no longer
On Wed, May 28, 2014 at 08:52:06PM +0200, Alexander Holler wrote:
> Am 28.05.2014 10:43, schrieb Brian Norris:
> >On Tue, May 27, 2014 at 12:12:26AM +0200, Alexander Holler wrote:
> >>+{
> >>+ mtd->priv = priv;
> >
> >I don't think you should hide this one here. It will be quite obvious if
On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
> * Move SoC peripherals into an SoC container node
> * Move serial enabling into board file (qcom-msm8960-cdp.dts)
> * Cleanup cpu node to match binding spec, enable-method and compatible
> should be per cpu, not part of the container
>
On Wed, May 28, 2014 at 10:39 AM, Alexander Duyck
wrote:
> On 05/27/2014 09:12 PM, Alex Williamson wrote:
>> On Tue, 2014-05-27 at 19:19 -0600, Bjorn Helgaas wrote:
>>> Maybe resetting the PF should just fail if there's an active VF. If
>>> you need to reset the PF, you'd have to unbind the VFs
On Wed, May 28, 2014 at 12:43:24PM -0700, Linus Torvalds wrote:
> It does require that the dentry shrinking code always hold the RCU
> lock for reading, because others may actually be doing the final
> dput() while the thing is on the shrinking list (and holding the RCU
> lock is what protects the
On 28-05-14 16:26, Thierry Reding wrote:
From: Thierry Reding
Commit febdbfe8a91c (arch: Prepare for smp_mb__{before,after}_atomic())
deprecated the smp_mb__{before,after}_{atomic,clear}_{dec,inc,bit}*()
functions in favour of the unified smp_mb__{before,after}_atomic().
Signed-off-by: Thierr
On May 28, 2014, at 3:09 PM, Josh Cartwright wrote:
> On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
>> * Move SoC peripherals into an SoC container node
>> * Move serial enabling into board file (qcom-msm8960-cdp.dts)
>> * Cleanup cpu node to match binding spec, enable-method and c
On Wed, Apr 30, 2014 at 06:54:33PM +0900, AKASHI Takahiro wrote:
> +/*
> + * arch/arm64/kernel/entry-ftrace.S
> + *
> + * Copyright (C) 2013 Linaro Limited
> + * Author: AKASHI Takahiro
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of th
On 05/28/2014 12:48 PM, Stephane Eranian wrote:
> Some days ago, I was alerted that under important network load, something
> is going wrong with perf_event sampling in frequency mode (such as perf top).
> The number of samples was way too low given the cycle count (via perf stat).
> Looking at the
Greg,
On Wed, 2014-05-28 at 12:14 +0200, Paul Bolle wrote:
> I must have compile tested this with CONFIG_LIB80211_CRYPT_TKIP=m while
> the code checks for CONFIG_LIB80211_CRYPT_TKIP only (ie, builtin only).
> I'll have to have a better look at this.
>
> Greg, can the cleaning up of this mess invo
On Wed, May 28, 2014 at 01:11:12PM -0700, Stephen Boyd wrote:
> We shouldn't be using regulator_get_optional() here. These
> regulators are always present as part of the physical design and
> there isn't any way to use an internal regulator or change the
> source of the reference voltage via softwa
On Wed, May 28, 2014 at 01:02:23PM -0700, Linus Torvalds wrote:
> Anyway, one reason I looked at this is that most of the threads in
> Mika's NMI watchdog traces were stuck on _raw_spin_lock() in the whole
> d_walk() thing, and I had a *really* hard time convincing myself that
> this was all safe
On Wed, May 28, 2014 at 12:41:28PM -0700, Stephen Boyd wrote:
> regulator_get_optional() doesn't hold an exclusive reference to
> the regulator. Fix the documentation and reword the exclusive
> documentation to fix the grammatical error "this reference is
> held".
Applied, thanks.
signature.asc
On Wed, May 28, 2014 at 11:30:04AM -0500, Rob Herring wrote:
> On Wed, May 14, 2014 at 9:26 AM, Grant Likely wrote:
> > On Thu, 8 May 2014 17:23:37 -0500, Rob Herring
> > wrote:
> >> From: Rob Herring
> >>
> >> This series adds support for early serial console initialization using
> >> DT. Thi
On Mon, 5 May 2014, Kirill Tkhai wrote:
> В Сб, 03/05/2014 в 20:54 +0200, Thomas Gleixner пишет:
> > Though exercising that code path as much as we can is not a bad thing
> > either. So I'd like to see that made compile time conditional on one
> > of the lock testing CONFIG items.
>
> +#ifndef CO
On Thu, 22 May 2014, Peter Zijlstra wrote:
> On Thu, May 22, 2014 at 03:25:50AM -, Thomas Gleixner wrote:
> > The builtin tester is gone,, so the deadlock logic is now only
> > required for futexes.
> >
> > Remove the extra arguments for the public functions and also for the
> > futex specific
On Thu, May 22, 2014 at 05:07:23PM -0600, Alex Williamson wrote:
> For testing, this version can be found in my git tree:
>
> git://github.com/awilliam/linux-vfio.git dma-alias-v4
>
> Please report any issues.
>
> v4:
> - Change dma_func_alias to dma_alias_devfn, holding a single
>devfn to
On Wed, May 28, 2014 at 10:01:30AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2014-05-23 at 19:41 +1000, Benjamin Herrenschmidt wrote:
> > Some backends call hvc_kick() to wakeup the HVC thread from its
> > slumber upon incoming characters. This however doesn't work
> > properly because it uses
"Serge E. Hallyn" writes:
>> I was aware of FUSE but hadn't ever looked at it much. Looking at it
>> now, this isn't going to satisfy any of the use cases I know about,
>> which are wanting to use filesystems supported in-kernel (isofs, ext*).
>> I don't see that any of these have a FUSE implement
On 05/28/2014 04:14 PM, Bjorn Helgaas wrote:
On Wed, May 28, 2014 at 10:39 AM, Alexander Duyck
wrote:
On 05/27/2014 09:12 PM, Alex Williamson wrote:
On Tue, 2014-05-27 at 19:19 -0600, Bjorn Helgaas wrote:
Maybe resetting the PF should just fail if there's an active VF. If
you need to reset
On Wed, May 28, 2014 at 10:21:28PM +0200, Paul Bolle wrote:
> Greg,
>
> On Wed, 2014-05-28 at 12:14 +0200, Paul Bolle wrote:
> > I must have compile tested this with CONFIG_LIB80211_CRYPT_TKIP=m while
> > the code checks for CONFIG_LIB80211_CRYPT_TKIP only (ie, builtin only).
> > I'll have to have
On Wed, 28 May 2014, walter harms wrote:
> Am 28.05.2014 11:11, schrieb Giedrius Rekasius:
> > Local variable "box" gets assigned correct value when it is initialized.
> > There is no need to assign the same value again.
> >
> > Signed-off-by: Giedrius Rekasius
> > ---
> > arch/x86/kernel/cpu/pe
On Wed, 2014-05-28 at 14:29 -0600, Bjorn Helgaas wrote:
> On Thu, May 22, 2014 at 05:07:23PM -0600, Alex Williamson wrote:
> > For testing, this version can be found in my git tree:
> >
> > git://github.com/awilliam/linux-vfio.git dma-alias-v4
> >
> > Please report any issues.
> >
> > v4:
> > -
>>> "George Spelvin" 05/28/14 4:40 PM >>>
>Jan: Is support for SLE10's pre-2.18 binutils still required?
>Your PEXTRD fix was only a year ago, so I expect, but I wanted to ask.
I'd much appreciate if I would be able to build the kernel that way for another
while.
>Two other minor additional cha
On Tue, May 27, 2014 at 07:36:11PM -0700, Sudeep Dutt wrote:
> +int register_mbus_driver(struct mbus_driver *driver)
> +{
> + driver->driver.bus = &mic_bus;
> + return driver_register(&driver->driver);
> +}
> +EXPORT_SYMBOL_GPL(register_mbus_driver);
mbus_register_driver()?
> +void unregi
On 05/28/2014 05:19 AM, Philipp Kern wrote:
> audit_filter_syscall uses the syscall number to reference into a
> bitmask (e->rule.mask[word]). Not removing the x32 bit before passing
> the number to this architecture independent codepath will fail to
> lookup the proper audit bit. Furthermore it wi
On Wed, 2014-05-28 at 13:42 -0700, Greg KH wrote:
> Either is fine with me, I can revert it, or apply a fix, which ever you
> want, just let me know.
Well, a proper fix would make this whole episode worthwhile. But if I
can't come up with anything that actually builds in a day or two it'll
have to
On Wed, May 28, 2014 at 04:26:32PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> Commit febdbfe8a91c (arch: Prepare for smp_mb__{before,after}_atomic())
> deprecated the smp_mb__{before,after}_{atomic,clear}_{dec,inc,bit}*()
> functions in favour of the unified smp_mb__{before,after}_at
On Wed, May 21, 2014 at 11:21:43AM +0800, Wei Yang wrote:
> Hi~
>
> Is this fix reasonable?
I'll leave this up to Grant...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.o
Thanks too, you helped me a lot.
I can do more work, if it's not too difficult for me.
Mathieu
Le 28/05/2014 11:52, Borislav Petkov a écrit :
On Wed, May 28, 2014 at 09:12:37AM +0200, Mathieu Souchaud wrote:
Check return code of every function called by mcheck_init_device().
Signed-off-by: M
On Tue, 27 May 2014, Jiang Liu wrote:
> -static void ioapic_create_irqdomains(void)
> +static int ioapic_create_irqdomain(int idx)
...
> -static int __init io_apic_get_redir_entries(int ioapic)
> +static int io_apic_get_redir_entries(int ioapic)
Can you please split the functional changes from
Several Marvell devices and a JMicron device have a similar DMA
requester ID problem to Ricoh, except they use function 1 as the
PCIe requester ID. Add a quirk for these to populate the DMA
alias with the correct devfn.
Signed-off-by: Alex Williamson
---
v4.1: minor commitlog tweak, no code cha
On Mon, Apr 28, 2014 at 03:09:27PM +0300, Heikki Krogerus wrote:
> This allows resources such as GPIOs and clocks, which can be
> matched based on the device name when requested, to be
> assigned even when PLATFORM_DEVID_AUTO is used.
Why would anyone want to do that?
>
> Signed-off-by: Heikki K
Several PCIe-to-PCI bridges fail to provide a PCIe capability, causing
us to handle them as conventional PCI devices when they really use the
requester ID of the secondary bus. We need to differentiate these
from PCIe-to-PCI bridges that actually use the conventional PCI ID
when a PCIe capability
On Wed, May 28, 2014 at 10:47 PM, Andy Lutomirski wrote:
> On 05/28/2014 05:19 AM, Philipp Kern wrote:
> > audit_filter_syscall uses the syscall number to reference into a
> > bitmask (e->rule.mask[word]). Not removing the x32 bit before passing
> > the number to this architecture independent code
On 05/28/2014 01:47 PM, Andy Lutomirski wrote:
> On 05/28/2014 05:19 AM, Philipp Kern wrote:
>> audit_filter_syscall uses the syscall number to reference into a
>> bitmask (e->rule.mask[word]). Not removing the x32 bit before passing
>> the number to this architecture independent codepath will fail
Update documentation for HID compass true/magnetic north sensor.
Signed-off-by: Reyad Attiyat
---
Documentation/ABI/testing/sysfs-bus-iio | 76 +
1 file changed, 76 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation/ABI/testing/sy
Updated iio_chan_info_enum for compass north sensor usages,
including magnetic/true north and tilt compensation.
Signed-off-by: Reyad Attiyat
---
drivers/iio/industrialio-core.c | 4
include/linux/iio/types.h | 4
2 files changed, 8 insertions(+)
diff --git a/drivers/iio/industr
Updated magn_3d_channel enum for all possible north channels
Added functions to setup iio_chan_spec array depending on
a hid usage report
Renamed magn_val to iio_val to differentiate the index being used
Updated magn_3d_state struct to hold pointer array (magn_val_addr[]) to
iio_val and a count
Update hid-sensor-magn-3d to dynamically create IIO channels
Update IIO to include modifiers for true/magnetic north and
tilt compensation compass usages
Signed-off-by: Reyad Attiyat
Reyad Attiyat (3):
IIO: Added iio magn_north ABI documentation
IIO: Add iio_chan modifier for True/Magnetic
On Wed, 28 May 2014, Jiang Liu wrote:
> On 2014/5/28 3:58, Thomas Gleixner wrote:
> > So you have these cases covered here:
> >
> > 1) The ACPI case of secondary ioapics. You only have the strict 1:1
> >mapping for the first ioapic
> >
> > 2) The gsi < NR_IRQS_LEGACY case where you have two o
Am 28.05.2014 22:10, schrieb Brian Norris:
> On Wed, May 28, 2014 at 08:52:06PM +0200, Alexander Holler wrote:
>> Am 28.05.2014 10:43, schrieb Brian Norris:
>>> On Tue, May 27, 2014 at 12:12:26AM +0200, Alexander Holler wrote:
+{
+ mtd->priv = priv;
>>>
>>> I don't think you should
On Wed, May 28, 2014 at 1:14 PM, Al Viro wrote:
>
> Unless I'm badly misreading your patch, you are calling dentry_kill()
> with rcu_read_lock() held. And that can trigger all sorts of interesting
> things, starting with iput() and tons of disk IO...
Yes, right you are.
As to my worry:
> d_wal
On Wed, May 28, 2014 at 10:48:02PM +0200, Paul Bolle wrote:
> On Wed, 2014-05-28 at 13:42 -0700, Greg KH wrote:
> > Either is fine with me, I can revert it, or apply a fix, which ever you
> > want, just let me know.
>
> Well, a proper fix would make this whole episode worthwhile. But if I
> can't
On Wed, May 28, 2014 at 2:01 PM, H. Peter Anvin wrote:
> On 05/28/2014 01:47 PM, Andy Lutomirski wrote:
>> On 05/28/2014 05:19 AM, Philipp Kern wrote:
>>> audit_filter_syscall uses the syscall number to reference into a
>>> bitmask (e->rule.mask[word]). Not removing the x32 bit before passing
>>>
> +static void sensor_hub_fill_attr_info(
> + struct hid_sensor_hub_attribute_info *info,
> + s32 index, s32 report_id, struct hid_field *field)
> +{
> + info->index = index;
> + info->report_id = report_id;
> + info->units = field->unit;
> + info
Laba diena,
Mēs esam DIAMOND ŠVEICES aizdevumu uzņēmumam sniedzot aizdevumus ar pasta
reklāma. Mēs piedāvājam dažāda veida aizdevumu (īstermiņa un ilgtermiņa
aizdevumi, individuālie aizņēmumi, aizdevumi uzņēmumiem uc), par 3% procentu
likmi. Mēs izsniegt aizdevumus cilvēkiem, kam nepiecieš
On 05/28/2014 02:15 PM, Andy Lutomirski wrote:
>>
>>> 3. The OOPS you're fixing doesn't seem like it's fixed. What if some
>>> other random high bits are set?
>>
>> There is a range check in entry_*.S for the system call.
>
> I can imagine that causing a certain amount of confusion to fancy
> sec
On 05/28/2014 02:15 PM, Reyad Attiyat wrote:
+static void sensor_hub_fill_attr_info(
+ struct hid_sensor_hub_attribute_info *info,
+ s32 index, s32 report_id, struct hid_field *field)
+{
+ info->index = index;
+ info->report_id = report_id;
+ info->un
On Wed, 28 May 2014, Thomas Gleixner wrote:
> On Wed, 28 May 2014, Jiang Liu wrote:
> > This is used to work around special non-ISA interrupts with GSI below
> > NR_IRQS_LEGACY. The original code for the special case is:
> > /*
> > * Provide an identity mapping of gsi == irq except on truly
> > *
Commit-ID: 6b8f0c8780c71d78624f736d7849645b64cc88b7
Gitweb: http://git.kernel.org/tip/6b8f0c8780c71d78624f736d7849645b64cc88b7
Author: David E. Box
AuthorDate: Fri, 9 May 2014 13:44:05 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 9 May 2014 14:56:15 -0700
x86, iosf: Make IOSF drive
Commit-ID: 04725ad59474d24553d526fa774179ecd2922342
Gitweb: http://git.kernel.org/tip/04725ad59474d24553d526fa774179ecd2922342
Author: Ong Boon Leong
AuthorDate: Fri, 9 May 2014 13:44:08 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 9 May 2014 14:57:35 -0700
x86, iosf: Add PCI ID ma
Commit-ID: 7ef1def800e907edd28ddb1a5c64bae6b8749cdd
Gitweb: http://git.kernel.org/tip/7ef1def800e907edd28ddb1a5c64bae6b8749cdd
Author: Ong Boon Leong
AuthorDate: Fri, 9 May 2014 13:44:06 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 9 May 2014 14:57:08 -0700
x86, iosf: Added Quark M
Commit-ID: 90916e048c1e0c1d379577e43ab9b8e331490cfb
Gitweb: http://git.kernel.org/tip/90916e048c1e0c1d379577e43ab9b8e331490cfb
Author: Ong Boon Leong
AuthorDate: Fri, 9 May 2014 13:44:07 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 9 May 2014 14:57:23 -0700
x86, iosf: Add Quark X10
On Wed, May 28, 2014 at 06:52:51PM +1000, Scott Weir wrote:
> This patch corrects coding style issue:
> WARNING: Missing a black line after declarations
>
> Signed-off-by: Scott Weir
> ---
> drivers/staging/android/sync_debug.c | 4
This file isn't in my tree. Always work against linux-nex
On Wed, May 28, 2014 at 02:11:51PM -0700, Linus Torvalds wrote:
> > d_walk() covers its arse with ->d_lock (and it wants the starting point
> > to be pinned, obviously). So AFAICS RCU is not a problem.
>
> It's not RCU itself, it's that DCACHE_MAY_FREE bit. Yes, d_walk() gets
> ->d_lock, but den
On Wed, May 28, 2014 at 07:32:39AM -0700, Chaitanya Hazarey wrote:
> -static int r8192_wx_set_scan_type(struct net_device *dev, struct
> iw_request_info *aa, union
> - iwreq_data *wrqu, char *p){
> +static int r8192_wx_set_scan_type(struct net_device *dev, struc
On 05/28/2014 01:50 PM, 'Arnaldo Carvalho de Melo' wrote:
What is being discussed here is how to return the EFAULT that may happen
_after_ datagram processing, be it interrupted by an EFAULT, signal, or
plain returning all that was requested, with no errors.
This EFAULT _after_ datagram process
Hey Srinivas,
Well I could use sensor_hub_input_get_attribute_info() for each usage
attribute. I was just thinking that since each usage attribute is
found in a row, one for each field I think, it'd be easier to create
iio channels that way. This would eliminate running the for loop
search for usa
On 05/28/2014 11:52 AM, Mike Turquette wrote:
Quoting Saravana Kannan (2014-05-28 10:47:46)
On 05/26/2014 04:14 AM, Peter De Schrijver wrote:
On Sat, May 24, 2014 at 12:24:32AM +0200, Saravana Kannan wrote:
On 05/23/2014 03:59 AM, Peter De Schrijver wrote:
This patch flattens the clk tree in
On 05/19/2014 05:36 AM, Arnd Bergmann wrote:
>
> My feeling is that all devices we can think of fall into at least one
> of these categories:
>
> * legacy PC stuff that needs only byte access
> * PCI devices that can be accessed through sysfs
> * devices on x86 that can be accessed using iopl
>
On Wed, May 28, 2014 at 2:19 PM, H. Peter Anvin wrote:
> On 05/28/2014 02:15 PM, Andy Lutomirski wrote:
>>>
3. The OOPS you're fixing doesn't seem like it's fixed. What if some
other random high bits are set?
>>>
>>> There is a range check in entry_*.S for the system call.
>>
>> I can i
Masami-san,
While trying:
[root@zoo ~]# perf probe 'vfs_getname=getname_flags:65
pathname=result->name:string'
Failed to find the location of result at this address.
Perhaps, it has been optimized out.
Failed to find 'result' in this function.
Error: Failed to add events. (-2)
[root@z
On 05/23/2014 09:40 AM, Andy Lutomirski wrote:
>
> I don't think this should be something configured by the
> administrator, unless the administrator is the builder of a kiosky
> thing like Chromium OS. In that case, the administrator can use
> vsyscall=none.
>
> I think this should be handled b
501 - 600 of 1111 matches
Mail list logo
