Commit-ID: 322a126a8fa8af80d9dc06e7168db11d1aabdba7
Gitweb: http://git.kernel.org/tip/322a126a8fa8af80d9dc06e7168db11d1aabdba7
Author: Michael Opdenacker
AuthorDate: Tue, 4 Mar 2014 21:31:51 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 4 Mar 2014 21:47:51 +0100
mn10300: Remove
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Pekon Gupta
commit bb38eefb6858ce16b34716145b9597a5680aa54c upstream.
This patch excludes reserved-marker byte-position from oobfree->length
calculation. Thus all bytes from oobfree->offset
On Wed, Feb 26, 2014 at 4:41 PM, Bjorn Helgaas wrote:
> Several architectures implement a simple pcibios_enable_device() that looks
> like this:
>
> int pcibios_enable_device(struct pci_dev *dev, int mask)
> {
> return pci_enable_resources(dev, mask);
> }
>
> This puts a weak
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Denis CIOCCA
commit a0657716416f834ef7710a9044614d50a36c3bdc upstream.
The driver was not able to manage the sensor: during probe function
and wai check, the driver stops and writes: "device
On Wed, Feb 26, 2014 at 12:37 PM, Bjorn Helgaas wrote:
> I'm trying to unify the way we handle unassigned PCI BARs, i.e., resources
> where we know the type and size, but we haven't assigned an address yet.
> The PCI core and the various architectures don't really have a consistent
> way of
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Beisert
commit 760dbe1dcb6d3dd3ead73dc69b23f206b52273bb upstream.
Releasing the touchscreen lets the internal statemachine left in a wrong state.
Due to this the release coordinate
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tomasz Nowicki
commit b685f3b1744061aa9ad822548ba9c674de5be7c6 upstream.
acpi_pci_link_allocate_irq() can return negative gsi even if
entry != NULL. For that case we have a memory leak, so
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Bi
commit accb884b32e82f943340688c9cd30290531e73e0 upstream.
In mei_cl_read_start(), if it fails to send flow control request, it
will release "cl->read_cb" but forget to set pointer to
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Pekon Gupta
commit eae39cb4934d3daab3ec828c5201c955b2e56af9 upstream.
Fixes: commit a919e51161b58ed7e6e663daba99ab7d558808f3
mtd: nand: omap2: clean-up BCHx_HW and BCHx_SW ECC
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Hesselbarth
commit 7b119fd1bdc59a8060df5b659b9f7a70e0169fd6 upstream.
It is good practice to mask and clear pending irqs on init. We already
mask all irqs, so also clear the bridge
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Twiss
commit ebf6dad0de89677aa58a4d8b009014ff88a23452 upstream.
Bug fix to allow the setting of maximum voltage for certain LDOs.
What the bug is:
There is a problem caused by an
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit c9d09e2748eaa55cac2af274574baa6368189bc1 upstream.
Commit a44a9791e778 ("iommu/arm-smmu: use mutex instead of spinlock for
locking page tables") replaced the page table
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 57ca90f6800987ac274d7ba065ae6692cdf9bcd7 upstream.
Whilst trying to bring-up an SMMUv2 implementation with the table
walker plumbed into a coherent interconnect, I noticed
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit e3703f8cdfcf39c25c4338c3ad8e68891cca3731 upstream.
Drew Richardson reported that he could make the kernel go *boom* when
hotplugging
while having perf events active.
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 37c367ecdb9a01c9acc980e6e17913570a1788a7 upstream.
HP Folio 13 may have a broken BIOS that doesn't set up the mute LED
GPIO properly, and the driver guesses it wrongly,
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 79d26a6a19ace19faabf8d8d27d3430be2e26d34 upstream.
glibc 2.17 is missing this on sparc, despite the fact that it's not
architecture-specific.
Signed-off-by: Ben
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 6dd35f45b8dac827b6f9dd86f5aca6436cdd2410 upstream.
Now that we populate page tables as we traverse them ("iommu/arm-smmu:
fix pud/pmd entry fill sequence"), we need to
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lai Jiangshan
commit 5bdfff96c69a4d5ab9c49e60abf9e070ecd2acbb upstream.
When a kworker should die, the kworkre is notified through WORKER_DIE
flag instead of kthread_should_stop(). This,
On Tue, 25 Feb 2014, Andy Lutomirski wrote:
> On 02/20/2014 08:23 AM, Alexey Perevalov wrote:
> > From: Anton Vorontsov
> >
> > This patch implements a userland-side API for generic deferrable timers,
> > per linux/timer.h:
> >
> > * A deferrable timer will work normally when the system is
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Yifan Zhang
commit 97a644208d1a08b7104d1fe2ace8cef011222711 upstream.
The ARM SMMU driver's population of puds and pmds is broken, since we
iterate over the next level of table repeatedly
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit 2d1f7af3d60dd09794e0738a915d272c6c27abc5 upstream.
Commit 3dc6475 ("bcm63xx_enet: add support Broadcom BCM6345 Ethernet")
changed the ENETDMA[CS] macros such that they
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Lunn
commit 322a8e91844f4ae2093e0d3d8a318d0ef2596756 upstream.
Marvell SoCs place the SoC number into the PCIe endpoint device ID. The
SoC stepping is placed into the PCIe revision.
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Matthieu CASTET
commit 5bf5dbeda2454296f1984adfbfc8e6f5965ac389 upstream.
ENDPTFLUSH and ENDPTPRIME registers are set by software and clear
by hardware. There is a bit for each endpoint. When
On Tue, Mar 04, 2014 at 09:43:10PM +0100, Richard Weinberger wrote:
> I remember a discussion with Al where he noted that register_exec_domain()
> is currently only used by out of tree horrors. B-)
>
> I'm sure we can rip it out of most archs. They seem to have it only because
> they've copy it
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Dorchain
commit 6dbd46c849e071e6afc1e0cad489b0175bca9318 upstream.
Hello,
the following patch adds an entry for the PID of a Cressi Leonardo
diving computer interface to kernel 3.13.0.
On Tue, 2014-03-04 at 10:06PM +0200, Eli Billauer wrote:
> Hello Sören,
>
> wp-inverted solves the practical problem indeed, and fools the
> driver into thinking that the card has an inverted write protection
> sensor, and the logic zero that it finds in the hardware register
> means that the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 862474f8b46f6c1e600d4934e40ba40646c696ec upstream.
It is needed to check the number of channels returned by the HW because it
cannot be greater than MAX_NET_DEVICES
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Dirk Brandewie
commit 4042e7570cff740460b75c6fc604c629621d3dd2 upstream.
LFM (max efficiency ratio) is the max frequency at minimum voltage
supported by the processor. Using LFM as the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit c091c71ad2218fc50a07b3d1dab85783f3b77efd upstream.
GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
flags, where meaningful is the LACK of
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jean Delvare
commit c0f5eeed0f4cef4f05b74883a7160e7edde58b6a upstream.
The reference count changes done by pci_get_device can be a little
misleading when the usage diverges from the most
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lan Tianyu
commit f3ca4164529b875374c410193bbbac0ee960895f upstream.
acpi_processor_set_throttling() uses set_cpus_allowed_ptr() to make
sure that the (struct
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit bd8ba20597f0cfef3ef65c3fd2aa92ab23d4c8e1 upstream.
Some devices have duplicate entries in there brightness levels table, ie
on my Dell Latitude E6430 the table looks like
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Aleksander Morgado
commit 12df84d4a80278a5b1abfec3206795291da52fc9 upstream.
This interface is to be handled by the qmi_wwan driver.
CC: Hans-Christoph Schemmel
CC: Christian Schmiedl
CC:
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 3e8d6d85adedc59115a564c0a54b36e42087c4d9 upstream.
High-speed USB connections revert back to full-speed signalling when
the device goes into suspend. This takes several
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit 1f42db786b14a31bf807fc41ee5583a00c08fcb1 upstream.
Some firmware leaves the Interrupt Disable bit set even if the device uses
INTx interrupts. Clear Interrupt Disable so
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 9eb2ddb48ce3a7bd745c14a933112994647fa3cd upstream.
Fix a race in which the RPC client is shutting down while the
gss daemon is processing a downcall. If the RPC client
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Levente Kurusa
commit 67809f85d31eac600f6b28defa5386c9d2a13b1d upstream.
Samsung's pci-e SSDs with device ID 0x1600 which are found on some
macbooks time out on NCQ commands. Blacklist NCQ
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 26e61e8939b1fe8729572dabe9a9e97d930dd4f6 upstream.
Vince "Super Tester" Weaver reported a new round of syscall fuzzing (Trinity)
failures,
with perf WARN_ON()s
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Arnaldo Carvalho de Melo
commit 844ae5b46c08dbc7ba695b543c023f9cf3bbf9ff upstream.
Supporting decoding the ioctl 'request' parameter needs more work to
properly support more architectures,
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hui Wang
commit 4913e0bf239dafee356bc7fab61806cc2518930c upstream.
When we plug a 3-ring headset on the Dell machines (Vendor ID:
0x10ec0255, Subsystem ID: 0x10280657; Vendor ID: 0x10ec0255,
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit e0cf957614976896111e676e5134ac98ee227d3d upstream.
We need to unmangle the full address, not just the register
number, and we also need to support the real
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit 2f3f38e4d3d03dd4125cc9a1f49ab3cc91d8d670 upstream.
The OPAL firmware functions opal_xscom_read and opal_xscom_write
take a 64-bit argument for the XSCOM (PCB)
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Breeds
commit 41dd03a94c7d408d2ef32530545097f7d1befe5c upstream.
Currently we're storing a host endian RTAS token in
rtas_stop_self_args.token. We then pass that directly to rtas. This
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Laurent Dufour
commit f5295bd8ea8a65dc5eac608b151386314cb978f1 upstream.
In copy_oldmem_page, the current check using max_pfn and min_low_pfn to
decide if the page is backed or not, is not
Hi everyone
22.02.2014, 11:30, "Alexander Shiyan" :
> Configuration for masters and slaves is included only if W1 symbol
> enabled, so no reason to check it once more.
>
> Signed-off-by: Alexander Shiyan
> ---
> drivers/w1/masters/Kconfig | 3 +--
> drivers/w1/slaves/Kconfig | 5 -
> 2
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: "Srivatsa S. Bhat"
commit c3274763bfc3bf1ececa269ed6e6c4d7ec1c3e5e upstream.
The powernow-k8 driver maintains a per-cpu data-structure called
powernow_data that is used to perform the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 0dc83bd30b0bf5410c0933cfbbf8853248eff0a9 upstream.
This reverts commit c4a391b53a72d2df4ee97f96f78c1d5971b47489. Dave
Chinner has reported the commit may cause some
inodes to
Remove mc_capable() and smt_capable(). Neither is used.
Both were added by 5c45bf279d37 ("sched: mc/smt power savings sched
policy"). Uses of both were removed by 8e7fbcbc22c1 ("sched: Remove stale
power aware scheduling remnants and dysfunctional knobs").
Signed-off-by: Bjorn Helgaas
---
This is just cleanup of a couple unused interfaces and (for sparc64) a
supporting variable.
---
Bjorn Helgaas (2):
sched: Remove unused mc_capable() and smt_capable()
sparc64: Remove unused sparc64_multi_core
arch/arm/include/asm/topology.h |3 ---
Remove sparc64_multi_core because it's not used any more.
It was added by a2f9f6bbb30e ("Fix {mc,smt}_capable()"), and the last uses
were removed by e637d96bf462 ("sched: Remove unused mc_capable() and
smt_capable()").
Signed-off-by: Bjorn Helgaas
---
arch/sparc/include/asm/smp_64.h |1 -
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 9f9c47f00ce99329b1a82e2ac4f70f0fe3db549c upstream.
It's a bit odd to see a newer device showing mod15write; however, the
reported behavior is highly consistent and other
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 48573a893303986e3b0b2974d6fb11f3d1bb7064 upstream.
cgroup_cfts_commit() walks the cgroup hierarchy that the target
subsystem is attached to and tries to apply the file
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: "Denis V. Lunev"
commit efb9e0f4f43780f0ae0c6428d66bd03e805c7539 upstream.
Without the patch the kernel generates the following error.
ata11.15: SATA link up 1.5 Gbps (SStatus 113 SControl
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit 573ebfa6601fa58b439e7f15828762839ccd306a upstream.
The new ELFv2 little-endian ABI increases the stack redzone -- the
area below the stack pointer that can be used for
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 7b4ec8dd7d4ac467e9eee4d49f2c9574d773efbb upstream.
sparse complains about any __ksymtab symbols with the following:
warning: symbol '__ksymtab_...' was not declared.
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 532de3fc72adc2a6525c4d53c07bf81e1732083d upstream.
Currently, there's nothing preventing cgroup_enable_task_cg_lists()
from missing set PF_EXITING and race against
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 75306820248e26d15d84acf4e297b9fb27dd3bb2 upstream.
The driver reads from the DC offset control registers during callibration
but since the registers are marked as volatile
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Dylan Reid
commit c42c8922c46d33ed769e99618bdfba06866a0c72 upstream.
Sync regcache when entering STANDBY from OFF. ON isn't entered with
OFF as the current state, so the registers were not
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch
commit 624aef494f86ed0c58056361c06347ad62b26806 upstream.
When the driver tries to access Function Unit 10, the KEF X300A
speakers' firmware apparently locks up, making even
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 7a6c0a58dc824523966f212c76322d47c5b0e6fe upstream.
wm8770 codec driver defines ain_enum with a wrong number of items.
Use SOC_ENUM_DOUBLE_DECL() macro and it's
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Shawn Guo
commit 47cf84e17ebb79a20e6244b954c4ea4e18a82d43 upstream.
The commit 1abe729 (ASoC: fsl: Add missing pm to current machine
drivers) enables pm support for a few IMX machine drivers.
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Thomson
commit 07b0e5b10258b48e5edfb6c8ac156f05510eb775 upstream.
Currently the I2C device Ids conflict for the MFD and CODEC so
cannot be both instantiated on one platform. This patch
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jarkko Nikula
commit b31b2b6d5de71c569413d8dc4f7b050cbe25a09e upstream.
Realtek RT5640 uses ACPI ID "10EC5640" for Intel Baytrail platforms.
Signed-off-by: Jarkko Nikula
Signed-off-by: Mark
On 03/03/2014 10:07 AM, Khalid Aziz wrote:
>
> I am working on a feature that has been requested by database folks that
> helps with performance. Some of the oft executed database code uses
> mutexes to lock other threads out of a critical section. They often see
> a situation where a thread
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Shiyan
commit 9febd494d15c4a351e9c9cae7184643144eea892 upstream.
This patch fixes a crash caused by commit 3bed3344c826
(ASoC: txx9aclc_ac97: Convert to devm_ioremap_resource()).
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit 1b385cbdd74aa803e966e01e5fe49490d6044e30 upstream.
Commit e504c9098ed6 (kvm, vmx: Fix lazy FPU on nested guest, 2013-11-13)
highlighted a real problem, but the fix was
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 06ea0bfe6e6043cb56a78935a19f6f8ebc636226 upstream.
When a send failure occurs due to the socket being out of buffer space,
we call xs_nospace() in order to have the RPC
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 70ff00f82a6af0ff68f8f7b411738634ce2f20d0 upstream.
codec->control_data contains a pointer to the regmap struct of the device, not
to the device private data. Use
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 025c3fa9256d4c54506b7a29dc3befac54f5c68d upstream.
Preset EQ enum of sta32x codec driver declares too many number of
items and it may lead to the access over the actual
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 548da08fc1e245faf9b0d7c41ecd8e07984fc332 upstream.
The codec->control_data contains a pointer to the device's regmap struct. But
wm8994_bulk_write() expects a
This patch removes the use of the IRQF_DISABLED flag
from arch/m32r/kernel/time.c
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
arch/m32r/kernel/time.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/m32r/kernel/time.c
On 03/04/2014 05:25 AM, David Vrabel wrote:
On 04/03/14 02:40, Boris Ostrovsky wrote:
Xen PV guests support only few APIC registers and writes to
unsupported registers result in WARN_ONs. Most APIC accesses in these
guests have been eliminated; however, lapic_suspend/resume are still
called
Folks,
Could you please queue up the following for the v3.15 merge window?
The following changes since commit 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2:
Linux 3.14-rc3 (2014-02-16 13:30:25 -0800)
are available in the git repository at:
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Honig
commit a08d3b3b99efd509133946056531cdf8f3a0c09b upstream.
The problem occurs when the guest performs a pusha with the stack
address pointing to an mmio address (or an invalid
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Antonio Quartulli
[ Upstream commit 05c3c8a636aa9ee35ce13f65afc5b665615cc786 ]
When the TVLV parsing routine succeed the skb is left
untouched thus leading to a memory leak.
Fix this by
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Simon Wunderlich
[ Upstream commit b2262df7fcf2c395eca564df83238e931d88d7bf ]
Since batadv_orig_node_new() sets the refcount to two, assuming that
the calling function will use a reference
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hui Wang
commit 1de7ca5e844866f56bebb2fc47fa18e090677e88 upstream.
The front headphone and mic jackes on a HP desktop model (Vendor Id:
0x111d76c7 Subsystem Id: 0x103c2b17) can not work, the
This patch removes the use of the IRQF_DISABLED flag
from arch/score/kernel/time.c
It's a NOOP since 2.6.35 and it will be removed one day.
Signed-off-by: Michael Opdenacker
---
arch/score/kernel/time.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Mar 4, 2014 at 12:00 PM, Al Viro wrote:
>
> OK, with the attached set (the first one is essentially unchanged from
> your first one), it seems to work and produce better code on all targets
> I've tried. Comments?
I'm certainly ok with it. You seem to have left the fput_light()
function
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hsin-Yu Chao
commit 13c12dbe3a2ce17227f7ddef652b6a53c78fa51f upstream.
Incorrect ADC is picked in ca0132_capture_pcm_prepare(),
where it assumes multiple streams while there is one stream
per
It moves the state setting for query into rndis_filter_receive_response().
All callbacks including query-complete and status-callback are synchronized
by channel->inbound_lock. This prevents pentential race between them.
Signed-off-by: Haiyang Zhang
---
drivers/net/hyperv/netvsc_drv.c |4
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hsin-Yu Chao
commit 28fba95087a7f3d107a3a6728aef7dbfaf3fd782 upstream.
When a HDMI stream is opened with the same stream tag
as a following opened stream to ca0132, audio will be
heard from
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: willy tarreau
[ Upstream commit 74c41b048db1073a04827d7f39e95ac1935524cc ]
Stats writers are mvneta_rx() and mvneta_tx(). They don't lock anything
when they update the stats, and as a result,
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit b58c89986a77a23658682a100eb15d8edb571ebb upstream.
cgroup_create() was returning 0 after allocation failures. Fix it.
Signed-off-by: Tejun Heo
Acked-by: Li Zefan
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit eb46bf89696972b856a9adb6aebd5c7b65c266e4 upstream.
When cgroup_mount() fails to allocate an id for the root, it didn't
set ret before jumping to unlock_drop ending up
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Antonio Quartulli
[ Upstream commit a30e22ca8464c2dc573e0144a972221c2f06c2cd ]
When computing the CRC on a 2byte variable the order of
the bytes obviously alters the final result. This means
This patch removes the use of the IRQF_DISABLED flag
from drivers/block/hd.c
It's a NOOP since 2.6.35 and it will be removed one day.
This also removes a related comment which is obsolete too.
Signed-off-by: Michael Opdenacker
---
drivers/block/hd.c | 12 +---
1 file changed, 1
Hi Sebastian,
On Sat, Mar 1, 2014 at 12:22 AM, Sebastian Reichel wrote:
> Hi Marek,
>
> On Fri, Feb 28, 2014 at 11:32:22PM +0100, Belisko Marek wrote:
>> Seems I found issue. I have missing property ti,system-uses-second-madc-irq
>> as original twl4030_madc_battery used SW2 but this change
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: willy tarreau
[ Upstream commit 290213667ab53a95456397763205e4b1e30f46b5 ]
If a queue timeout is reported, we can oops because of some
schedules while the caller is atomic, as shown below :
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit ffd5939381c609056b33b7585fb05a77b4c695f3 ]
SCTP's sctp_connectx() abi breaks for 64bit kernels compiled with 32bit
emulation (e.g. ia32 emulation or
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit ed98df3361f059db42786c830ea96e2d18b8d4db ]
sock_alloc_send_pskb() & sk_page_frag_refill()
have a loop trying high order allocations to prepare
skb with low
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: willy tarreau
[ Upstream commit 71f6d1b31fb1f278a345a30a2180515adc7d80ae ]
Right now the mvneta driver doesn't handle Tx IRQ, and relies on two
mechanisms to flush Tx descriptors : a flush at
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Nithin Sujir
[ Upstream commit c6993dfd7db9b0c6b7ca7503a56fda9236a4710f ]
Quoting David Vrabel -
"5780 cards cannot have jumbo frames and TSO enabled together. When
jumbo frames are enabled
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit de960aa9ab4decc3304959f69533eef64d05d8e8 upstream.
This moves part of Eric Dumazets skb_gso_seglen helper from tbf sched to
skbuff core so it may be reused by upcoming
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit fe6cc55f3a9a053482a76f5a6b2257cee51b4663 upstream.
Marcelo Ricardo Leitner reported problems when the forwarding link path
has a lower mtu than the incoming one if the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: willy tarreau
[ Upstream commit 40ba35e74fa56866918d2f3bc0528b5b92725d5e ]
Marvell has not published the chip's datasheet yet, so it's very hard
to find the relevant bits to manipulate to
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: willy tarreau
[ Upstream commit dc4277dd41a80fd5f29a90412ea04bc3ba54fbf1 ]
Better count packets and bytes in the stack and on 32 bit then
accumulate them at the end for once. This saves two
Hello Mike,
On 10/15/2013 12:17 AM, Miller, Mike (OS Dev) wrote:
>
>> -Original Message-
>> From: Michael Opdenacker [mailto:michael.opdenacker@free-
>> electrons.com]
>> Sent: Friday, October 11, 2013 11:15 PM
>> To: chirag.kantha...@hp.com
>> Cc: ISS StorageDev;
On Sun, 2 Mar 2014 19:09:58 +0530 Gideon Israel Dsouza
wrote:
> To increase compiler portability there is which
> provides convenience macros for various gcc constructs. Eg: __weak
> for __attribute__((weak)). I've replaced all instances of gcc
> attributes with the right macro in the
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Antonio Quartulli
[ Upstream commit f1791425cf0bcda43ab9a9a37df1ad3ccb1f6654 ]
pskb_may_pull() returns 1 on success and 0 in case of failure,
therefore checking for the return value being
1701 - 1800 of 2246 matches
Mail list logo