On 11/25/2013 04:37 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> [Addressed all addressable review feedback in v2]
>
> Properly patching running code ("cross modification")
> is a quite complicated business on x86.
>
> The CPU has specific rules that need to be followed, including
> multiple
Hi,
On Tue, Nov 26, 2013 at 12:59:13PM -0600, Felipe Balbi wrote:
> > > diff --git a/drivers/usb/gadget/f_obex.c
> > > b/drivers/usb/gadget/f_obex.c index ad39f1d..4af2f06 100644
> > > --- a/drivers/usb/gadget/f_obex.c
> > > +++ b/drivers/usb/gadget/f_obex.c
> > > @@ -267,10 +267,12 @@ static
On 11/26/2013 12:01 PM, Olof Johansson wrote:
> On Mon, Nov 25, 2013 at 7:35 PM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> On Tue, 26 Nov 2013 13:29:46 +1100 Stephen Rothwell
>> wrote:
>>>
>>> After merging the block tree, today's linux-next build (arm
>>> multi_v7_defconfig) produced these
On Mon, Nov 25, 2013 at 7:35 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 26 Nov 2013 13:29:46 +1100 Stephen Rothwell
> wrote:
>>
>> After merging the block tree, today's linux-next build (arm
>> multi_v7_defconfig) produced these warnings:
>>
>> block/blk-merge.c: In function
Hi,
On Tue, Nov 26, 2013 at 07:10:08PM +0100, Pali Rohár wrote:
> > > > > (above dump is from 3.12-rc5 kernel)
> > > >
> > > > looks like it's trying to do i2c transfers from atomic.
> > > > But why only when obex is enabled ? Makes no sense. What
> > > > do you have on userland ? Is there
On Tue, Nov 26, 2013 at 10:37:59AM -0800, Tony Luck wrote:
> On Thu, Nov 21, 2013 at 10:57 AM, Tony Luck wrote:
> > On Thu, Nov 21, 2013 at 5:30 AM, Thomas Gleixner wrote:
> >> On Thu, 21 Nov 2013, Peter Zijlstra wrote:
> >>> Anyway, I don't object to the patch per se, but it might bloat a few
>
commit 73675c8aa07 ('gpio: pl061: proper error messages') added a printout
of a resource_size_t using %x, which produces an error for builds with
64-bit resources:
drivers/gpio/gpio-pl061.c:345:3: warning: format '%x' expects argument of
type 'unsigned int', but argument 3 has type
On Tue, Nov 26, 2013 at 10:44:16AM -0800, Linus Torvalds wrote:
> > At first I thought it was just being really slow, (especially after seeing
> > all those congestion related symbols in the stack traces), but even after
> > being left for hours, it doesn't seem to progress.
>
> It *does*
Hi Guenter,
On Mon, Nov 25, 2013 at 08:39:04PM -0800, Guenter Roeck wrote:
> Simplify the code and create mandatory 'name' attribute by using
> new hwmon API.
So this moves hwmon attributes from the parent i2c device to the hwmon
device, right? Would not that break userspace which expects to
On 11/26/2013 10:22 AM, Doug Anderson wrote:
It is valid for a watchdog driver to have 0 for a "min" and "max"
timeout if the driver doesn't need the core to enforce the concepts of
min and max. The s3c2410_wdt driver is one such driver. Specifically
it can be hard for that driver to come up
On 11/26/2013 10:22 AM, Doug Anderson wrote:
There was a minor bug in watchdog_init_timeout() where it would return
an error code if someone specified an invalid parameter on the
command line but then there was a valid parameter in the device tree
as "timeout-sec".
Signed-off-by: Doug Anderson
On Tue, Nov 26, 2013 at 08:39:20AM -0800, Guenter Roeck wrote:
> On 11/25/2013 05:44 AM, Ben Hutchings wrote:
> >This is the start of the stable review cycle for the 3.2.53 release.
> >There are 87 patches in this series, which will be posted as responses
> >to this one. If anyone has any issues
On 11/26/2013 10:30 AM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998
commit 54f8d501e8428 ('dmaengine: remove DMA unmap from drivers')
refactored some code which resulted in an unused function in the at_hdmac
driver:
drivers/dma/at_hdmac_regs.h:350:23: warning: 'chan2parent' defined but
not used [-Wunused-function]
Fixes: 54f8d501e8428 ('dmaengine: remove DMA
On Tue, Nov 26, 2013 at 10:21 AM, Dave Jones wrote:
> I've been seeing this a few times on your current tree while fuzz testing.
>
> When it happens, the machine responds to ping, but ssh always times out.
> I can log in on a tty, but as soon as it tries to exec something, that tty
> hangs.
>
>
> .desc = "MWAIT 0x51",
> - .flags = MWAIT2flg(0x58) | CPUIDLE_FLAG_TIME_VALID |
> CPUIDLE_FLAG_TLB_FLUSHED,
> + .flags = MWAIT2flg(0x51) | CPUIDLE_FLAG_TIME_VALID |
> CPUIDLE_FLAG_TLB_FLUSHED,
> .exit_latency = 15,
>
On Tue, Nov 26, 2013 at 05:48:06PM +, Matthew Garrett wrote:
> On Tue, Nov 26, 2013 at 10:35:26AM -0700, Bjorn Helgaas wrote:
> > On Tue, Nov 26, 2013 at 9:40 AM, Khalid Aziz wrote:
> > > Disabling Bus Master bit is effectively a brute force and not an elegant
> > > way
> > > to stop
On Thu, Nov 21, 2013 at 10:57 AM, Tony Luck wrote:
> On Thu, Nov 21, 2013 at 5:30 AM, Thomas Gleixner wrote:
>> On Thu, 21 Nov 2013, Peter Zijlstra wrote:
>>> Anyway, I don't object to the patch per se, but it might bloat a few
>>> !ia64 kernels for having to carry the extra text.
>
> I tried it
Hello,
On Tue, Oct 01, 2013 at 10:18:08AM -0700, Tim Kryger wrote:
> When configured with UART_16550_COMPATIBLE=NO or in versions prior to
> the introduction of this option, the Designware UART will ignore writes
> to the LCR if the UART is busy. The current workaround saves a copy of
> the last
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998 seconds and
reporting a timeout of 31 seconds.
Hi,
just a few comments, mostly code style.
2013-11-26 16:04, Peng Tao:
> @@ -1011,23 +1083,17 @@ int mgc_set_info_async(const struct lu_env *env,
> struct obd_export *exp,
> }
> if (KEY_IS(KEY_SET_FS)) {
> struct super_block *sb = (struct super_block *)val;
> -
It is valid for a watchdog driver to have 0 for a "min" and "max"
timeout if the driver doesn't need the core to enforce the concepts of
min and max. The s3c2410_wdt driver is one such driver. Specifically
it can be hard for that driver to come up with a static "max" on all
platforms without a
On 11/26/2013 08:30 PM, Santosh Shilimkar wrote:
Ivan,
On Tuesday 26 November 2013 12:44 PM, ivan.khoronzhuk wrote:
On 11/26/2013 09:20 AM, Sekhar Nori wrote:
On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote:
+static struct platform_driver davinci_aemif_driver = {
+ .probe
On 11/26/2013 08:26 PM, Santosh Shilimkar wrote:
Fair enough
Ok, I will do
--
Regards,
Ivan Khoronzhuk
--
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
Ivan,
On Tuesday 26 November 2013 12:44 PM, ivan.khoronzhuk wrote:
> On 11/26/2013 09:20 AM, Sekhar Nori wrote:
>> On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote:
>>> +static struct platform_driver davinci_aemif_driver = {
>>> + .probe = davinci_aemif_probe,
>>> +
* Joel Fernandes [131125 19:03]:
> Hi Tony,
>
> Few replies inline below. Adding Suman as well who is planning to use dmtimer
> directly for his work with DSP.
>
> On 11/22/2013 09:33 AM, Tony Lindgren wrote:
> > Hi,
> >
> > * Joel Fernandes [131121 18:00]:
> >> Multiplatform support has made
On Tuesday 26 November 2013 12:21 PM, Sekhar Nori wrote:
> On 11/26/2013 8:35 PM, Santosh Shilimkar wrote:
>> On Tuesday 26 November 2013 02:20 AM, Sekhar Nori wrote:
>>> On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote:
Add new AEMIF driver for EMIF16 davinci controller. The
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Moore
commit 4be4be8fee2ee99a52f94f90d03d2f287ee1db86 upstream.
This change fixes a problem where a Store operation to an ArgX object
that contained a reference to a field object did not
-
NOTE:
This is the LAST 3.11.x kernel I will be releasing. Everyone should
be moving to the 3.12.x series at this point in time. After this
kernel is released, 3.11 will be end-of-life.
-
This is the start of the stable
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Moore
commit 63660e05ec719613b518547b40a1c501c10f0bc4 upstream.
Previously, references to these objects were resolved only to the actual
FieldUnit or BufferField object. The correct
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit 4577b014d1bc3db386da3246f625888fc48083a9 upstream.
A user reported a problem where they were getting csum errors when running a
balance and running systemd's journal. This
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 896e23bd04ea50a146dffd342e2f96180f0812a5 upstream.
Some devices, like the Kvaser Memorator Professional, have several bulk in
endpoints. Only the first one found must be
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit a91ccd26e75235d86248d018fe3779732bcafd8d upstream.
Make sure to return errors from tiocmget rather than rely on
uninitialised stack data.
Signed-off-by: Johan Hovold
There was a minor bug in watchdog_init_timeout() where it would return
an error code if someone specified an invalid parameter on the
command line but then there was a valid parameter in the device tree
as "timeout-sec".
Signed-off-by: Doug Anderson
---
drivers/watchdog/watchdog_core.c | 8
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 upstream.
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit f262f0f5cad0c9eca61d1d383e3b67b57dcbe5ea upstream.
The cbc-aes-s390 algorithm incorrectly places the IV in the tfm
data structure. As the tfm is shared between multiple
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Thelen
commit a399b29dfbaaaf91162b2dc5a5875dd51bbfa2a1 upstream.
When IPC_RMID races with other shm operations there's potential for
use-after-free of the shm object's associated file
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Horman
commit 714b33d15130cbb5ab426456d4e3de842d6c5b8a upstream.
Stephan Mueller reported to me recently a error in random number generation in
the ansi cprng. If several small requests
On 11/26/2013 10:15 AM, Ashutosh Dixit wrote:
> Avoid declaring ALIGN() and __aligned() in
> include/uapi/linux/mic_common.h since they pollute user space
> namespace. Also, mic_aligned_size() can be simply replaced simply by
> sizeof() since all structures where mic_aligned_size() is used are
>
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit d3694d4fa3f44f6a295f8ab064937c8a1549d174 upstream.
Every PCIe device has a link, except Root Complex Integrated Endpoints
and Root Complex Event Collectors. Previously
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit cab6661344f14a09d7aecdf821a40f68ef9b18cc upstream.
SNDRV_CARDS can be specified via Kconfig since 3.11 kernel, so this
can be over 32bit integer range, which leads to a
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit ea8117478918a4734586d35ff530721b682425be upstream.
Mike reported that commit 7d1a9417 ("x86: Use generic idle loop")
regressed several workloads and caused excessive
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Skeggs
commit 13d2b35a065399fb447c84e80368927e5f8bf086 upstream.
Signed-off-by: Ben Skeggs
Cc: Ilia Mirkin
Signed-off-by: Greg Kroah-Hartman
---
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit c8b303d0206b28c4ff3aecada47108d1655ae00f upstream.
Previously we relied on the PCIe r3.0, sec 7.8, spec language that says
"For Functions that do not implement the [Link,
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Adamson
commit f1ff0c27fd9987c59d707cd1a6b6c1fc3ae0a250 upstream.
The NFS layer needs to know when a key has expired.
This change also returns -EKEYEXPIRED to the application, and the
* Borislav Petkov wrote:
> On Fri, Nov 22, 2013 at 04:39:11PM +0100, Ingo Molnar wrote:
>
> > I see no problem with that - it's basically like util/*.c is, just
> > between tools.
>
> But why? Why it is a good thing to have to pay attention to linking
> to 10 minilibs when you're using 10
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Puneet Kumar
commit 36b15875a7819a2ec4cb5748ff7096ad7bd86cbb upstream.
A bug was introduced by commit b76b51ba0cef ('ACPI / EC: Add more debug
info and trivial code cleanup') that erroneously
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Jesper Nilsson
commit 3a72660b07d86d60457ca32080b1ce8c2b628ee2 upstream.
Commit 2caacaa82a51 ("ipc,shm: shorten critical region for shmctl")
restructured the ipc shm to shorten critical
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 12ae030d54ef250706da5642fc7697cc60ad0df7 upstream.
The current default perf paranoid level is "1" which has
"perf_paranoid_kernel()" return false, and giving any
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 2441191a19039002b2c454a261fb45986df15184 upstream.
It is required to do get_device() on the struct acpi_device in
question before passing it to
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit 67aa4acbc97f6a55b328e4e2305ef19cbe949d85 upstream.
`comedi_alloc_spriv()` allocates private storage for a comedi subdevice
and sets the `SRF_FREE_SPRIV` flag in the
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Moore
commit a50abf4842dd7d603a2ad6dcc7f1467fd2a66f03 upstream.
Disallow the dereference of a reference (via index) to an uninitialized
package element. Provides compatibility with other
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Lu
commit 2c62333a408f5badd2d2ffd7177f95deeccc5ca4 upstream.
Some firmware doesn't initialize initial backlight level to a proper
value and _BQC will return 0 on first time evaluation.
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 3d8bfe141be8e5c21261fc63da8e7964d44f2645 upstream.
Since:
commit 36323f817af0376c78612cfdab714b0feb05fea5
Author: Thomas Huehn
Date: Mon Jul 23 21:33:42 2012
On Friday, November 08, 2013 1:07 PM, Dave Jones wrote:
> On Thu, Nov 07, 2013 at 06:27:54AM +, Linux Kernel wrote:
>> Gitweb:
>> http://git.kernel.org/linus/;a=commit;h=b3ff824a81e8978deb56f6d163479c1a0a606037
>> Commit: b3ff824a81e8978deb56f6d163479c1a0a606037
>> Parent:
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Markus Pargmann
commit 5d0f801a2ccec3b1fdabc3392c8d99ed0413d216 upstream.
If we handle end of block messages with higher priority than a lost message,
we can run into an endless interrupt
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 176a88d79d6b5aebabaff16734e8b3107efcaaad upstream.
According to the ACPI spec (5.0, Section 6.3.5), the "Device
insertion in progress (pending)" (0x80) _OST status
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit 6d3a1741f1e648cfbd5a0cc94477a0d5004c6f5e upstream.
Previously we allowed callers to access Slot Capabilities, Status, and
Control for Root Ports even if the Root Port did
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Mimi Zohar
commit 08de59eb144d7c41351a467442f898d720f0f15f upstream.
This reverts commit 4c2c392763a682354fac65b6a569adec4e4b5387.
Everything in the initramfs should be measured and
On 11/25/2013 03:36 PM, Doug Anderson wrote:
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq transitions unless
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Rashika Kheria
commit 46a51c80216cb891f271ad021f59009f34677499 upstream.
This patch fixes the bug in reset_store caused by accessing NULL pointer.
The bdev gets its value from bdget_disk()
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Gabor Juhos
commit 0beb1bbf19c72f17809e42b8f33522a55c2cc18c upstream.
In commit 3d81535ea5940446510a8a5cee1c6ad23c90c753
(rt2800: 5592: add chip specific vgc calculations)
the
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit b1a8014471b01dd862de9f91bbbff1296afac42d upstream.
Many btusb devices have 2 modes, a hid mode and a bluetooth hci mode. These
devices default to hid mode for BIOS use.
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 5671ab05cf2a579218985ef56595387932d78ee4 upstream.
Fix random kernel panic with below messages when remove dongle.
[ 2212.355447] BUG: unable to handle kernel NULL
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: hahnjo
commit b54629e226d196e802abdd30c5e34f2a47cddcf2 upstream.
This fixes bug 62491 (https://bugzilla.kernel.org/show_bug.cgi?id=62491).
After resuming some users got the following error
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit d049f74f2dbe71354d43d393ac3a188947811348 upstream.
The get_dumpable() return value is not boolean. Most users of the
function actually want to be testing for
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 565ce6422ff92f5af71e4d5a09f78215433b2695 upstream.
Rescind of subchannels were not being correctly handled. Fix the bug.
Signed-off-by: K. Y. Srinivasan
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit b4089d6d8e71a7293e2192025dfa507a04f661c4 upstream.
Commit "rt2x00: fix HT TX descriptor settings regression"
assumes that the control parameter to rt2x00mac_tx is always
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Mahesh Rajashekhara
commit b4789b8e6be3151a955ade74872822f30e8cd914 upstream.
It appears that driver runs into a problem here if fibsize is too small
because we allocate user_srbcmd with
Hi,
On Tue, Nov 26, 2013 at 07:06:43PM +0100, Pavel Machek wrote:
> > > > For a long time (since 3.5 or 3.8? - I do not remember) obex
> > > > subdriver in g_nokia usb gadget module causing kernel panic
> > > > after module is loaded on Nokia N900. I do not know where is
> > > > problem and due
On Tuesday 26 November 2013 18:39:54 Felipe Balbi wrote:
> Hi,
>
> On Tue, Nov 26, 2013 at 06:28:05PM +0100, Pali Rohár wrote:
>
> [ snip ]
>
> > > > (above dump is from 3.12-rc5 kernel)
> > >
> > > looks like it's trying to do i2c transfers from atomic.
> > > But why only when obex is enabled
On 11/25, Borislav Petkov wrote:
>
> On Mon, Nov 25, 2013 at 08:50:28PM +0100, Oleg Nesterov wrote:
> > This won't work if va + len overflows?
>
> Oh, right,
>
> > Perhaps we should makes this clear, and we can even check the overflow
> > in the generic code (iirc Linus suggested to do this).
>
>
Avoid declaring ALIGN() and __aligned() in
include/uapi/linux/mic_common.h since they pollute user space
namespace. Also, mic_aligned_size() can be simply replaced simply by
sizeof() since all structures where mic_aligned_size() is used are
declared using __attribute__ ((aligned(8)));
--
>From
On Tue 2013-11-26 18:17:49, Sebastian Reichel wrote:
> On Tue, Nov 26, 2013 at 06:10:22PM +0100, Pali Rohár wrote:
> > On Tuesday 19 November 2013 11:51:12 Pali Rohár wrote:
> > > For a long time (since 3.5 or 3.8? - I do not remember) obex
> > > subdriver in g_nokia usb gadget module causing
Endianness issues are now consistent as per the documentation in
host/mic_virtio.h. Note that the host can be both BE or LE whereas the
card is always LE.
Memory space sparse warnings are fixed for now by using __force. This is
sufficient for now since the driver depends on x86 but will need to
On Tue, Nov 26, 2013 at 12:00 AM, Steven Newbury wrote:
>
>> On Mon, Nov 25, 2013 at 6:28 PM, Yinghai Lu wrote:
>> > Some x86 systems expose above 4G 64bit mmio in _CRS as non-pref mmio range.
>> > [ 49.415281] PCI host bridge to bus :00
>> > [ 49.419921] pci_bus :00: root bus
This patch adds the TCO Watchdog Device IDs for the Intel Wildcat Point-LP PCH.
Signed-off-by: James Ralston
---
drivers/mfd/lpc_ich.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mfd/lpc_ich.c b/drivers/mfd/lpc_ich.c
index 9483bc8..019f578 100644
---
MIC user space daemon poll's on sysfs changes. The documentation for
sysfs_poll(...) in fs/sysfs/file.c states that "Once poll/select
indicates that the value has changed, you need to close and re-open the
file, or seek to 0 and read again". This step was missed out earlier and
resulted in the
These patches fix various issues which were reported or found with the
MIC driver.
Ashutosh Dixit (3):
misc: mic: Bug fix for sysfs poll usage.
misc: mic: Fix sparse warnings and other endianness issues.
misc: mic: Fix user space namespace pollution from mic_common.h.
Sudeep Dutt (2):
* Borislav Petkov wrote:
> On Fri, Nov 22, 2013 at 04:54:25PM +0100, Ingo Molnar wrote:
> > comet:~/tip/tools/perf> ls util/*.h
> > util/annotate.h util/data.h util/fs.h
> > util/parse-events-bison.h util/probe-event.h util/sort.h
> > util/thread.h
Hello Linus,
Sorry for the noise, my mail was filtered by several ML because of some
HTML contents.
Le 26/11/2013 14:46, Linus Walleij a écrit :
On Thu, Nov 21, 2013 at 11:34 AM, boris brezillon
wrote:
On 21/11/2013 10:48, Linus Walleij wrote:
No matter whether it's a switch or a GPIO
Hi,
On N950 with fixed vmmc regulator, MMC probe started to fail with
3.13-rc1:
[2.497406] mmc0: host doesn't support card's voltages
[2.502899] mmc0: error -22 whilst initialising MMC card
I bisected this to c368e5fc2a190923b786f2de3e79430ea3566a25
(regulator: fixed: get rid of
On 11/26, zhang.y...@zte.com.cn wrote:
>
> Userspace process doesn't want the PF_NO_SETAFFINITY, but its parent may be
> a kernel worker thread which has PF_NO_SETAFFINITY set.
... and this worker thread can do kernel_thread() to create the child.
> Clearing this flag in usersapce child to
From: Sudeep Dutt
The bug would result in incorrect 'retry' value being printed in debug
statements as well as dead code in mic_find_vqs(...) in
drivers/misc/mic/card/mic_virtio.c.
Reported-by: Michael Opdenacker
Reviewed-by: Ashutosh Dixit
Signed-off-by: Sudeep Dutt
---
From: Sudeep Dutt
virtqueue_{kick()/notify()} methods are required to return bool due to
API changes introduced in commit 5b1bf7cb673a.
Reported-by: Fengguang Wu
Reported-by: Geert Uytterhoeven
Reviewed-by: Ashutosh Dixit
Signed-off-by: Sudeep Dutt
---
drivers/misc/mic/card/mic_virtio.c |
* Jean Pihet wrote:
> Use the per-feature check flags for the unwinding feature in order
> to correctly compile the libunwind and libunwind-debug-frame feature
> checks.
>
> Tested on ARMv7 and ARMv8 with 'make DEBUG=1 LIBUNWIND_DIR=/usr/local
> -C tools/perf'
>
> Signed-off-by: Jean Pihet
>
* Jean Pihet wrote:
> Add CFLAGS and LDFLAGS for each feature to be checked. This allows
> to pass flags and parameters to the feature checks compilation.
> Also simplifies the feature check makefile, to come in a subsequent patch.
>
> Signed-off-by: Jean Pihet
> ---
>
On Mon, Nov 25, 2013 at 11:59 PM, Guo Chao wrote:
> On Mon, Nov 25, 2013 at 09:17:11PM -0700, Bjorn Helgaas wrote:
>> On Mon, Nov 25, 2013 at 6:28 PM, Yinghai Lu wrote:
>> > When one of children resources does not support MEM_64, MEM_64 for
>> > bridge get reset, so pull down whole pref resource
* Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 22, 2013 at 03:24:26PM +0100, Jiri Olsa escreveu:
> > }
> > +
> > +ssize_t perf_data_file__write(struct perf_data_file *file,
> > + void *buf, size_t size)
> > +{
> > + ssize_t total = size;
> > +
> > + while (size) {
On 11/26, Oleg Nesterov wrote:
>
> Note: this doesn't work for modules, but module's per-cpu data is
> not visible for kallsyms_lookup_name() anyway.
Rusty, I am just curious if it makes sense to change this or not...
But DEFINE_PER_CPU'ed symbols are ignored by add_kallsyms(). I guess
this is
On Tue, Nov 26, 2013 at 10:35:26AM -0700, Bjorn Helgaas wrote:
> On Tue, Nov 26, 2013 at 9:40 AM, Khalid Aziz wrote:
> > Disabling Bus Master bit is effectively a brute force and not an elegant way
> > to stop unwanted DMA. It can have side effects as Alan and others pointed
> > out in the
On 11/26/2013 09:20 AM, Sekhar Nori wrote:
> On Monday 11 November 2013 10:36 PM, Khoronzhuk, Ivan wrote:
>> Add new AEMIF driver for EMIF16 davinci controller. The EMIF16 module
>> is intended to provide a glue-less interface to a variety of
>> asynchronous memory devices like ASRA M, NOR and
On Mon, Oct 28, 2013 at 01:59:02PM +0100, Andreas Larsson wrote:
> On 2013-10-01 16:19, Felipe Balbi wrote:
> +static void gr_finish_request(struct gr_ep *ep, struct gr_request *req,
> + int status)
> +{
> + struct gr_udc *dev;
> +
> +
Preparation for the next changes. Shift "+= offset" from
update_symbol_cache() to ->fetch[FETCH_MTD_symbol], this
allows to detect the per-cpu symbols.
Also remove the !offset check in traceprobe_split_symbol_offset(),
it is never called with offset == NULL.
Signed-off-by: Oleg Nesterov
---
FETCH_FUNC_NAME(symbol) blindly dereferences sc->addr + sc->offset,
this is not what we want if this symbol is per-cpu. Change this code
to use this_cpu_ptr(sc->addr) in this case.
Note: this doesn't work for modules, but module's per-cpu data is
not visible for kallsyms_lookup_name() anyway.
On 11/26/2013 11:29 AM, Joe Perches wrote:
> On Tue, 2013-11-26 at 11:11 -0600, Rob Herring wrote:
>> I think we don't really want '+' (or '_') in compatible strings.
>
> What about lines like:
> arch/powerpc/boot/dts/kmeter1.dts: compatible = "ucc_geth";
I didn't say we don't have them, but
On 11/26, Masami Hiramatsu wrote:
>
> (2013/11/26 2:22), Oleg Nesterov wrote:
> > @symbol can't be used to dump the per-cpu variables. The same is
> > true for +offset(something) if "something" results in __percpu
> > pointer.
> >
> > With this patch parse_probe_offset() treats "~" before the
Hi,
On Tue, Nov 26, 2013 at 06:28:05PM +0100, Pali Rohár wrote:
[ snip ]
> > > (above dump is from 3.12-rc5 kernel)
> >
> > looks like it's trying to do i2c transfers from atomic. But
> > why only when obex is enabled ? Makes no sense. What do you
> > have on userland ? Is there anything
[+cc Eric, Matthew]
On Tue, Nov 26, 2013 at 9:40 AM, Khalid Aziz wrote:
> On 11/25/2013 08:33 PM, Bjorn Helgaas wrote:
>>
>> [+cc Lan, Khalid, Konstantin, Alan, Takao, Jility, Florian, linux-kernel]
>>
>> On Tue, Nov 12, 2013 at 07:40:03PM +, Chang Liu wrote:
>>>
>>> This fixes
On Tuesday 26 November 2013 18:17:49 Sebastian Reichel wrote:
> On Tue, Nov 26, 2013 at 06:10:22PM +0100, Pali Rohár wrote:
> > On Tuesday 19 November 2013 11:51:12 Pali Rohár wrote:
> > > For a long time (since 3.5 or 3.8? - I do not remember)
> > > obex subdriver in g_nokia usb gadget module
601 - 700 of 1902 matches
Mail list logo
