Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single fix for a long standing race versus timers scheduled on a
target cpu which got exposed by recent changes in the workqueue
implementa
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
A single regression fix to restore the wakeup behaviour of chained
interrupts.
Thanks,
tglx
-->
Grygorii Strashko (1):
On 12 November 2015 at 21:21, Laura Abbott wrote:
> The permissions in mark_rodata_ro trigger a build error
> with STRICT_MM_TYPECHECKS. Fix this by introducing
> PAGE_KERNEL_ROX for the same reasons as PAGE_KERNEL_RO.
Forgive the bikeshedding but perhaps PAGE_KERNEL_EXEC_RO is more consistent?
cfg80211 module prints a lot of messages like below. Actually printing
once is acceptable but sometimes it will print again and again, it looks
very annoying. It is better to change these detail messages to debugging
only.
cfg80211: World regulatory domain updated:
cfg80211: DFS Master region: un
On 11 November 2015 at 02:57, Laura Abbott wrote:
> Rather than always putting the least restrictived permissions
> (PAGE_KERNEL_EXEC) when spliting a pmd into pages, use
> the existing permissions from the pmd for the page.
>
> Signed-off-by: Laura Abbott
> ---
> v2: Typo and typechecking fixed
On Sun, Nov 15, 2015 at 12:53:21AM +, Ben Hutchings wrote:
> On Wed, 2015-09-16 at 07:33 +0200, Willy Tarreau wrote:
> > Hi Olga,
> >
> > On Tue, Sep 15, 2015 at 02:36:06PM +, Kornievskaia, Olga wrote:
> > >
> > > Hi Willy,
> > >
> > > After checking with the list, I believe the course o
Hi!
Kernel complains:
[5.256044] [ cut here ]
[5.259267] WARNING: CPU: 0 PID: 1 at
arch/x86/mm/dump_pagetables.c:225 note_page+0x5ec/0x790()
[5.262668] x86/mm: Found insecure W+X mapping at address
ffe69000/0xffe69000
[5.267109] Modules linked in:
[5.27
> While if the test is done in kfree_skb(), the branch predictor of the
> cpu wont be able to predict things.
>
> By feeding too many NULL pointers to kfree_skb(), we slow down it.
Would it make sense to annotate checks before such function calls
as "UNLIKELY"?
Regards,
Markus
--
To unsubscribe
Add known information about the Marvell BG2CDP SoC that's used in
the Google Chromecast 2015 and Kinoma HD devices.
Signed-off-by: Thomas Hebb
---
My previous patch somehow ended up with spaces instead of tabs on
the added lines. This one is consistent with the rest of the section.
Apologies for
Hi,
When we tested network with following case, found there is
regression with stable 4.1 kernel, connect() returns EADDRNOTAVAIL,
while a pretty old kernel 3.8 doesn't. anybody knows about this issue
and if it was fixed later ? (I am looking for devices and will do a
test with the last stable
- 'if' which is always false is removed
- variable associated with this 'if' is deleted
Signed-off-by: Chandra S Gorentla
---
drivers/staging/wilc1000/wilc_msgqueue.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_msgqueue.c
b/drivers/s
for_each_child_of_node performs an of_node_get on each iteration,
so of_node_put is required on break out of the loop.
This is done using Coccinelle. And semantic patch used for this is
as follows:
@@
expression root,e;
local idexpression child;
@@
for_each_child_of_node(root, child) {
... w
On Sat, 2015-11-14 at 20:05 +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 14 Nov 2015 19:55:00 +0100
>
> The kfree_skb() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the calls is not needed.
>
> This issue was detected by
Add known information about the Marvell BG2CDP SoC that's used in
the Google Chromecast 2015 and Kinoma HD devices.
Signed-off-by: Thomas Hebb
---
Documentation/arm/Marvell/README | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/arm/Marvell/README b/Document
These are a few changes to bring the Marvell Berlin family documentation
up to date. The old URLs were no longer redirecting properly, so I
changed them to the current ones. I also added what information I could
find about the new BG2CDP chip used in the Chromecast 2015.
Thomas Hebb (3):
Documen
The chip's design name isn't hyphenated anywhere else, and none of the
other names in the same document are hyphenated.
Signed-off-by: Thomas Hebb
---
Documentation/arm/Marvell/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/arm/Marvell/README b/Documenta
Marvell has renamed their Berlin family from "Digital Entertainment" to
"Multimedia Solutions." There aren't proper redirects set up for
device-specific pages, so update the URLs accordingly.
Signed-off-by: Thomas Hebb
---
Documentation/arm/Marvell/README | 14 +++---
1 file changed, 7 i
On Sun, Nov 15, 2015 at 12:05 AM, Ondrej Zary
wrote:
> Add support for IP1000A chips to dl2k driver.
> IP1000A chip looks like a TC9020 with integrated PHY.
>
> This allows IP1000A chips to work reliably because the ipg driver is
> buggy - it loses packets under load and then completely stops
> tr
Hi all,
Please do *not* add any material intended for v4.5 to your linux-next
included branches until after v4.4-rc1 has been released.
Changes since 20151113:
Dropped tree: target-merge (many conflicts)
The scsi tree lost its build failure.
Non-merge commits (relative to Linus' tree): 689
66
This is the combined diff for 3.2.73-rc1 relative to 3.2.72.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
diff --git a/Makefile b/Makefile
index 77ac417..2aa389f 100644
--- a/M
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Richard Guy Briggs
commit 80e0b6e8a001361316a2d62b748fe677ec46b860 upstream.
We accidentally declared pid_alive without any extern/inline connotation.
Some platforms were fine with this, some l
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
commit a41cbe86df3afbc82311a1640e20858c0cd7e065 upstream.
A test case is as the description says:
open(foobar, O_WRONLY);
sleep() --> reboot the server
close(foobar)
The bug
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then copy_to_user sequence.
Avoi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 95af587e95aacb9cfda4a9641069a5244a540dc8 upstream.
When a write to one of the legs of a RAID10 fails, the failure is
recorded in the metadata of the other legs so that after a
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream.
Currently a number of Crypto API operations may fail when a signal
occurs. This causes nasty problems as the caller of thos
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: John Stultz
commit 67dfae0cd72fec5cd158b6e5fb1647b7dbe0834c upstream.
This patch fixes one cases where abs() was being used with 64-bit
nanosecond values, where the result may be capped at 32-b
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
commit 1acea4f6ce1b1c0941438aca75dd2e5c6b09db60 upstream.
We can't rely on PPPOX_ZOMBIE to decide whether to clear po->pppoe_dev.
PPPOX_ZOMBIE can be set by pppoe_disc_rcv() eve
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: shengyong
commit 7c7feb2ebfc9c0552c51f0c050db1d1a004faac5 upstream.
UBI: attaching mtd1 to ubi0
UBI: scanning is finished
UBI error: init_volumes: not enough PEBs, required 706, available 686
U
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 53960059d56ecef67d4ddd546731623641a3d2d1 upstream.
If there is a DMA zone (usually 24bit = 16MB I believe), but no DMA32
zone, as is the case for some 32-bit kernels, then ma
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Steve French
commit 646200a041203f440fb6fcf9cacd9efeda9de74c upstream.
The error paths in set_file_size for cifs and smb3 are incorrect.
In the unlikely event that a server did not support set
On Fri, Nov 13, 2015 at 2:35 PM, H. Nikolaus Schaller
wrote:
> By this patch we still recognise the old binding ti,swap-xy in parallel to
> the common binding touchscreen-swapped-x-y. This keeps compatibility
> to older (out-of-tree) device tree binaries.
>
> We do this in a separate patch so tha
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 55ce74d4bfe1b936264c637f39a152d1e5ac upstream.
When a write to one of the legs of a RAID1 fails, the failure is
recorded in the metadata of the other leg(s) so that after a
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 94c4554ba07adbdde396748ee7ae01e86cf2d8d7 upstream.
There appears to be a race between:
(1) key_gc_unused_keys() which frees key->security and then calls
keyring_dest
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 029cd0370241641eb70235d205aa0b90c84dce44 upstream.
ath9k inserts padding between the 802.11 header and the data area (to
align it). Since it didn't declare this extra requi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit f05819df10d7b09f6d1eb6f8534a8f68e5a4fe61 upstream.
The following sequence of commands:
i=`keyctl add user a a @s`
keyctl request2 keyring foo bar @t
keyctl unl
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Northup
commit 54a20552e1eae07aa240fa370a0293e006b5faed upstream.
It was found that a guest can DoS a host by triggering an infinite
stream of "alignment check" (#AC) exceptions. This cau
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream.
If a host fails to wake up a isochronous SuperSpeed device from U1/U2
in time for a isoch transfer it will generate a "No
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ilia Mirkin
commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream.
On nv50+, we restrict the valid domains to just the one where the buffer
was originally created. However after the buffer i
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Denis Turischev
commits c09ec25d3684cad74d851c0f028a495999591279 and
0a939993bff117d3657108ca13b011fc0378aedb upstream.
The same issue like with Panther Point chipsets. If the USB ports are
swi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 31b33dfb0a144469dd805514c9e63f4993729a48 ]
Earlier patch 6ae459bda tried to detect void ckecksum partial
skb by comparing pull length to checksum offset. But i
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit e210c422b6fdd2dc123bedc588f399aefd8bf9de upstream.
If the difference is big enough between the bytes asked and received
in a bulk transfer we can get a short transfer event
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michel Stam
[ Upstream commit 3cc81d85ee01e5a0b7ea2f4190e2ed1165f53c31 ]
I've noticed every time the interface is set to 'up,', the kernel
reports that the link speed is set to 100 Mbps/Full Du
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit c340702ca26a628832fade4f133d8160a55c29cc upstream.
When a write fails and a bad-block-list is present, we can
update the bad-block-list instead of writing the data. If
this su
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sabrina Dubroca
Without this length argument, we can read past the end of the iovec in
memcpy_toiovec because we have no way of knowing the total length of the
iovec's buffers.
This is needed f
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 15e3d5a285ab9283136dba34bbf72886d9146706 upstream.
3w controller don't dma map small single SGL entry commands but instead
bounce buffer them. Add a helper to identify
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Yao-Wen Mao
commit 8484bf2981b3d006426ac052a3642c9ce1d8d980 upstream.
These two headphones need a reset-resume quirk to properly resume to
original volume level.
Signed-off-by: Yao-Wen Mao
Si
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit e8d65a8d985271a102f07c7456da5b86c19ffe16 upstream.
Add the appropriate quirk to indicate the Lenovo G50-80 has a stereo
mic input where one channel has reverse polarity
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 95913d97914f44db2b81271c2e2ebd4d2ac2df83 upstream.
So the problem this patch is trying to address is as follows:
CPU0CPU1
con
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 225db5762dc1a35b26850477ffa06e5cd0097243 upstream.
When OSS emulation is loaded on ISA SB AWE32 chip, we get now kernel
warnings like:
WARNING: CPU: 0 PID: 2791 at fs/sysf
On Fri, Nov 13, 2015 at 09:35:52PM +0100, H. Nikolaus Schaller wrote:
> commit b98abe52fa8e ("Input: add common DT binding for touchscreens")
> introduced common DT bindings for touchscreens [1] and a helper function to
> parse the DT.
>
> This has been integrated and interpretation of the inversi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit eda7d0f38aaf50dbb2a2de15e8db386c4f6f65fc upstream.
"num_read" is in byte units but we are write u16s so we end up write
twice as much as intended.
Signed-off-by: Dan Carpe
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Vincent Palatin
commit 72194739f54607bbf8cfded159627a2015381557 upstream.
Add a device quirk for the Logitech PTZ Pro Camera and its sibling the
ConferenceCam CC3000e Camera.
This fixes the fai
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/0x90
[] _
On Fri, Nov 13, 2015 at 10:03:55PM -0500, Gabriel L. Somlo wrote:
> From: Gabriel Somlo
>
> Remove redundant details from
> Documentation/devicetree/bindings/arm/fw-cfg.txt,
> and replace them with a pointer to the more comprehensive
> fw_cfg documentation privided by
> Documentation/ABI/testing/
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Cathy Avery
commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream.
xen-blkfront will crash if the check to talk_to_blkback()
in blkback_changed()(XenbusStateInitWait) returns an error.
The d
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Doron Tsur
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since ib_send_cm_sidr
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 2f84a8990ebbe235c59716896e017c6b2ca1200f upstream.
SunDong reported the following on
https://bugzilla.kernel.org/show_bug.cgi?id=103841
I think I find a linux bug,
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 95c2b17534654829db428f11bcf4297c059a2a7e upstream.
Per-IRQ directories in procfs are created only when a handler is first
added to the irqdesc, not when the irqdesc is crea
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
[ Upstream commit 436c2a5036b6ffe813310df2cf327d3b69be0734 ]
commit 3cc81d85ee01 ("asix: Don't reset PHY on if_up for ASIX 88772")
causes the ethernet on Arndale to no longer fun
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
commit 97aff2c03a1e4d343266adadb52313613efb027f upstream.
There are 24 EQ registers not 25, I suspect this bug came about because
the registers start at EQ1 not zero. The bug is
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
commit e6740165b8f7f06d8caee0fceab3fb9d790a6fed upstream.
Since commit 2b018d57ff18 ("pppoe: drop PPPOX_ZOMBIEs in pppoe_release"),
pppoe_release() calls dev_put(po->pppoe_dev)
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andreas Schwab
commit 8474ba74193d302e83401e16c85cc4b98caf upstream.
Make sure the compiler does not modify arguments of syscall functions.
This can happen if the compiler generates a tailc
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit b763ec17ac762470eec5be8ebcc43e4f8b2c2b82 upstream.
If a read is attempted which is smaller than the line length then we may
underflow the subtraction we're doing with the unsi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Vasant Hegde
commit 8832317f662c06f5c06e638f57bfe89a71c9b266 upstream.
Currently we do not validate rtas.entry before calling enter_rtas(). This
leads to a kernel oops when user space calls rta
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 8996eafdcbad149ac0f772fb1649fbb75c482a6a upstream.
Unlike shash algorithms, ahash drivers must implement export
and import as their descriptors may contain hardware state an
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kosuke Tatsukawa
commit e81107d4c6bd098878af9796b24edc8d4a9524fd upstream.
My colleague ran into a program stall on a x86_64 server, where
n_tty_read() was waiting for data even if there was da
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream.
btree_split_beneath()'s error path had an outstanding FIXME that speaks
directly to the potential for _not_ cleaning up a
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Malcolm Crossley
commit 64c98e7f49100b637cd20a6c63508caed6bbba7a upstream.
Sanitizing the e820 map may produce extra E820 entries which would result in
the topmost E820 entries being removed. T
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 296291cdd1629c308114504b850dc343eabc2782 upstream.
Currently a simple program below issues a sendfile(2) system call which
takes about 62 days to complete in my test KVM instanc
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 199dc6ed5179251fa6158a461499c24bdd99c836 upstream.
When a (e.g.) RAID5 array is reshaped to RAID0, the updating
of queue parameters (e.g. max number of sectors per bio) is
done
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Joe Thornber
commit 2871c69e025e8bc507651d5a9cf81a8a7da9d24b upstream.
Commit 4c7e309340ff ("dm btree remove: fix bug in redistribute3") wasn't
a complete fix for redistribute3().
The redistri
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit bd8688a199b864944bf62eebed0ca13b46249453 upstream.
When a write fails and a bad-block-list is present, we can
update the bad-block-list instead of writing the data. If
this su
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 176fc2d5770a0990eebff903ba680d2edd32e718 upstream.
The in kernel snprintf() will conveniently return the actual length of
the printed string even if not given an output beffer
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0 wi
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit eddd3826a1a0190e5235703d1e666affa4d13b96 upstream.
Dmitry Vyukov reported the following using trinity and the memory
error detector AddressSanitizer
(https://code.google.
This is the start of the stable review cycle for the 3.2.73 release.
There are 60 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Tue Nov 17 09:00:00 UTC 2015.
Anything receiv
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christian Zander
commit ba2374fd2bf379f933773811fdb06cb6a5445f41 upstream.
In preparation for the installation of a large page, any small page
tables that may still exist in the target IOV addr
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit 281fda27673f833a01d516658a64d22a32c8e072 upstream.
Make sure that data_size is less than LEB size.
Otherwise a handcrafted UBI image is able to trigger
an out of bound
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream.
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 6ae459bdaaeebc632b16e54dcbabb490c6931d61 ]
VXLAN device can receive skb with checksum partial. But the checksum
offset could be in outer header which is pulled
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 0c55627167870255158db1cde0d28366f91c8872 upstream.
This is mostly a hardening fix, given that write-only access to other
users' ttys is usually only given through setgid tty ex
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dāvis Mosāns
commit 2280521719e81919283b82902ac24058f87dfc1b upstream.
When pci_pool_alloc fails in mvs_task_prep then task->lldd_task stays
NULL but it's later used in mvs_abort_task as slot w
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 66eefe5de11db1e0d8f2edc3880d50e7c36a9d43 upstream.
Calling e.g. blk_queue_max_hw_sectors() after calls to
disk_stack_limits() discards the settings determined by
disk_stack_lim
3.2.73-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
This reverts commit 41e3025eacd6daafc40c3e7850fbcabc8b847805, which
was commit 6f691251c0350ac52a007c54bf3ef62e9d8cdc5e upstream.
The fix is only needed after commit f8f559422b6c
These three structures are only defined and referenced in
mach-hisi/platsmp.c.
Drop the declarations from the header and add static qualifier
to the definitions.
Signed-off-by: Masahiro Yamada
---
arch/arm/mach-hisi/core.h| 3 ---
arch/arm/mach-hisi/platsmp.c | 6 +++---
2 files changed, 3
On 14/11/15 22:31, Nicholas A. Bellinger wrote:
> Hi Luis,
>
> Apologies for the delayed response.
>
No worries. I understand maintainers are very busy.
Thanks for taking the time to review and merge :)
Enjoy your weekend,
Luis
> On Mon, 2015-10-19 at 21:18 +0100, Luis de Bethencourt wrote:
On Sun, 2015-08-02 at 21:24 -0700, Guenter Roeck wrote:
> On 08/02/2015 02:49 PM, Ben Hutchings wrote:
> > On Sat, 2015-08-01 at 19:23 -0700, Guenter Roeck wrote:
> > > On 08/01/2015 05:02 PM, Ben Hutchings wrote:
> > > > This is the start of the stable review cycle for the 3.2.70 release.
> > > >
Hi Eduardo,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 12b76f3bf336388916ddf8047156f9e9993ff4e9
commit: cb7fb4d342023d03070fcc1ed73fcd43682973d7 thermal: qcom_spmi: allow
compile test
date: 9 weeks ago
config
On Wed, 2015-09-16 at 07:33 +0200, Willy Tarreau wrote:
> Hi Olga,
>
> On Tue, Sep 15, 2015 at 02:36:06PM +, Kornievskaia, Olga wrote:
> >
> > Hi Willy,
> >
> > After checking with the list, I believe the course of action will be to
> > correct the patch with the patch below instead of rever
Hi Markus,
> The kfree_skb() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
> net/bluetooth/cmtp/core.c | 3 +--
> 1 fil
Hi Michal,
I notice that the kbuild tree (relative to Linus' tree) only contains
lots of merges and these 2 commits from April 2014:
commit 19a3cc83353e3bb4bc28769f8606139a3d350d2d
Author: Andi Kleen
Date: Wed Apr 2 21:49:27 2014 +0200
Kbuild, lto: Add Link Time Optimization support v3
Hi Markus,
> The kfree_skb() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
> net/mac802154/rx.c | 3 +--
> 1 file chang
On Sat, Nov 14, 2015 at 10:16:33PM +0100, Pavel Machek wrote:
> HiOn Sat 2015-11-14 18:49:40, Mark Brown wrote:
> > On Sat, Nov 14, 2015 at 06:59:16PM +0100, Pavel Machek wrote:
> > > Well, mfd_core.c seems to call regulator_bulk_register_supply_alias()
> > > with device that does not have dev_nam
Hi Glen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 12b76f3bf336388916ddf8047156f9e9993ff4e9
commit: d5382219138db78b82631501b0f614e5fd012ad1 staging: wilc1000:
host_int_init: add argument net_device
date: 2
--
To whom it may concern:
I am writing to both Unemployed and employed, that if you are interest
in working an extra job, non-stressful work online as our mystery
shopper should not hesitate to contact me Via This E-mail (
shopfstest0...@gmail.com ) for further information.
Sincerely yours
Hi Zain,
Am Freitag, 13. November 2015, 14:44:43 schrieb Zain:
>
> On 2015年11月12日 20:32, Heiko Stuebner wrote:
> > Hi Zain,
> >
> > I was able to sucessfully test your crypto-driver, but have found some
> > improvements below that should probably get looked at:
> >
> > Am Mittwoch, 11. November 2
Hi Luis,
Apologies for the delayed response.
On Mon, 2015-10-19 at 21:18 +0100, Luis de Bethencourt wrote:
> Smatch complains about returning hard coded error codes, silence this
> warning.
>
> drivers/target/iscsi/iscsi_target_parameters.c:211
> iscsi_create_default_params() warn: returning -1
Now that IP1000A chips are supported by dl2k driver, the buggy ipg
driver can be removed. The ipg driver loses packets under load and then
completely stops transmitting data.
Signed-off-by: Ondrej Zary
---
MAINTAINERS |7 -
drivers/net/ethernet/Kconfig |
Add support for IP1000A chips to dl2k driver.
IP1000A chip looks like a TC9020 with integrated PHY.
This allows IP1000A chips to work reliably because the ipg driver is
buggy - it loses packets under load and then completely stops
transmitting data.
Tested with Asus NX1101 v2.0 at 10, 100 and 100
This change is a prerequisite for pending patches that switch to a
dedicated EFI page table, instead of using 'trampoline_pgd' which
shares PGD entries with 'swapper_pg_dir'. The pending patches make it
impossible to dereference the runtime service function pointer without
first switching %cr3.
It
1 - 100 of 209 matches
Mail list logo