Hello,
Re-sending after corrections, I've some more patches on top of this will send
them separately to avoid delaying this one with new comments.
This patch series adds very basic support for Allwinner A83T SOC.
Clock, peripherals, smp support will be added later.
Allwinner A83T is octa-core
H8Homlet Proto v2.0 Board is A83T Dev Board by Allwinner.
It has UART, ethernet, USB, HDMI, etc ports on it.
A83T patches are tested on this board.
It has UART, ethernet, USB, HDMI, etc ports on it.
For FEL mode it needs USB A-A(Male) cable. I used uart0 which
is multiplexed to microsd pins PF2
Hello, Marcelo.
On Wed, Jan 06, 2016 at 10:46:15AM -0200, Marcelo Tosatti wrote:
> Well, i suppose cgroups has facilities to handle this? That is, what is
> required is:
No, it doesn't.
> On task creation, move the new task to a particular cgroup, based on
> some visible characteristic of the
On Wed, Jan 06, 2016 at 01:05:03PM +0300, Dan Carpenter wrote:
> If memdup_user() fails then we end up passing an ERR_PTR to kfree()
> which is a bug.
Mind if I fold it (with credit, obviously)?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Heiko,
On 2016年01月02日 10:34, Xing Zheng wrote:
> Hi Heiko,
> Thank you for your patch, I will apply and test it later.
>
> Thanks.
>
>> 在 2016年1月2日，06:10，Heiko Stübner 写道：
>>
>> Hi Xing,
>>
>> Am Dienstag, 29. Dezember 2015, 10:34:09 schrieb Xing Zheng:
>>> On 2015年12月29日 09:59, Yakir
Hi Matt, Andrea,
On Tue, 22 Dec 2015 15:17:51 +, Matt Fleming wrote:
> (Cc'ing Jean since he's the maintainer)
>
> On Tue, 22 Dec, at 02:53:10PM, Andrea Arcangeli wrote:
> > The dmi_ver wasn't updated correctly before the dmi_decode method run
> > to save the uuid.
> >
> > That resulted in
The script used in the analysis below:
dmesg_with_human_timestamps () {
$(type -P dmesg) "$@" | perl -w -e 'use strict;
my ($uptime) = do { local @ARGV="/proc/uptime";<>}; ($uptime) =
($uptime =~ /^(\d+)\./);
foreach my $line (<>) {
printf(
This is a timekeeping staging patch for the printk() timestamp
functionality that adds a trylock option for the timekeeping_lock() to
ktime_get_with_offset(). When trylock is 1, calls to
ktime_get_with_offset() will return return a ktime of 0 if the
timekeeping_lock is locked.
This patch adds
Over the past years I've seen many reports of bugs that include
time-stamped kernel logs (enabled when CONFIG_PRINTK_TIME=y or
print.time=1 is specified as a kernel parameter) that do not align
with either external time stamped logs or /var/log/messages.
For example,
[root@intel-wildcatpass-06
Hi,
any comments for this patches?
Regards
Andy
--
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Fri, 18 Dec, at 11:29:51AM, sylvain.choul...@gmail.com wrote:
> From: Sylvain Chouleur
>
> This patch adds an implementation of EFI runtime services wappers which
> allow interrupts and preemption during execution of BIOS code.
>
> It's needed by Broxton platform which requires the OS to do
Hi, Sudip
On 01/04/2016 09:14 PM, Sudip Mukherjee wrote:
> On Sat, Jan 02, 2016 at 11:40:51PM +0100, Arnd Bergmann wrote:
>> On Saturday 02 January 2016 11:59:29 Sudip Mukherjee wrote:
Just to be sure we are talking about the same thing: you mean running a
64-bit
kernel in a
On Wed, Jan 06, 2016 at 12:30:11PM +, Catalin Marinas wrote:
> On Tue, Jan 05, 2016 at 05:33:35PM +, Mark Rutland wrote:
> > Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc
> > state machine that can be difficult to reason about due to duplicated
> > code and a
On Wed, Jan 06, 2016 at 12:09:50AM +0100, Thomas Gleixner wrote:
> Marcelo,
>
> On Mon, 4 Jan 2016, Marcelo Tosatti wrote:
> > On Thu, Dec 31, 2015 at 11:30:57PM +0100, Thomas Gleixner wrote:
> > > I don't have an idea how that would look like. The current structure is a
> > > cgroups based
Regards
Andy
--
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.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 12/28/2015 03:13 PM, Tetsuo Handa wrote:
> Tetsuo Handa wrote:
>> Tetsuo Handa wrote:
>> > I got OOM killers while running heavy disk I/O (extracting kernel source,
>> > running lxr's genxref command). (Environ: 4 CPUs / 2048MB RAM / no swap /
>> > XFS)
>> > Do you think these OOM killers
On 2016-01-05 15:47, One Thousand Gnomes wrote:
This means that not including the VT subsystem resulted in a 128k
reduction in runtime footprint, and having only half the number of VT's
resulted in a 52k reduction. Assuming a linear correlation between the
number of VT's and the runtime
Hi Boris,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.4-rc8 next-20160106]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Boris-Brezillon/drm-bridge-sil902x
On Wed, Jan 06, 2016 at 05:49:22PM +0530, Laxman Dewangan wrote:
> On Wednesday 06 January 2016 05:48 PM, Mark Brown wrote:
> >* PGP Signed by an unknown key
> >On Wed, Jan 06, 2016 at 11:45:22AM +0530, Laxman Dewangan wrote:
> >> Enhanced transient response (ETR) will affect the configuration
On 1/6/2016 2:15 PM, Christoph Hellwig wrote:
I'm not Doug, but all the recent for 4.5 work is in Dougs tree
at
https://github.com/dledford/linux rdma/k.o/for-4.5
Christoph,
As I wrote here, the bits are already @ kernel.org
On Wed, Dec 30, 2015 at 09:59:29AM -0800, Tony Luck wrote:
> Starting with a patch from Andy Lutomirski
> that used linker relocation trickery to free up a couple of bits
> in the "fixup" field of the exception table (and generalized the
> uaccess_err hack to use one of the classes).
>
> This
Now we have a clock driver that can control the 32k clock use this
rather than directly controlling the 32k clock from the MFD device.
Signed-off-by: Charles Keepax
---
Changes since v1:
- No long select COMMON_CLK_ARIZONA from the MFD, this can lead
to a situation where we are building
The 32k clock is unconditionally enabled by the MFD core so there is no
need to control it from the extcon device, so this patch removes the
control of the 32k clock.
Signed-off-by: Charles Keepax
---
No changes since v1.
Thanks,
Charles
drivers/extcon/extcon-arizona.c | 2 --
1 file
Add an initial clock driver for the Arizona series audio CODECs.
Currently this driver only provides support for parsing the two input
clocks (mclk1, mclk2) and providing the internally consumed 32k clock.
Signed-off-by: Charles Keepax
---
Changes since v1:
- Change in if (ret != 0) to an if
Specify the device tree binding for the input clocks to Arizona devices.
Signed-off-by: Charles Keepax
---
No changes since v1.
Thanks,
Charles
Documentation/devicetree/bindings/mfd/arizona.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
On Wed, Dec 30, 2015 at 09:59:29AM -0800, Tony Luck wrote:
> Starting with a patch from Andy Lutomirski
> that used linker relocation trickery to free up a couple of bits
> in the "fixup" field of the exception table (and generalized the
> uaccess_err hack to use one of the classes).
So I still
On Tue, 2016-01-05 at 16:39 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > You're missing Petko's patch:
> > 41c89b6 IMA: create machine owner and blacklist keyrings
>
> Hmmm... This is wrong. x509_key_preparse() shouldn't be polling the IMA MOK
> keyring under all circumstances.
The
On Tue, Jan 05, 2016 at 05:33:35PM +, Mark Rutland wrote:
> Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc
> state machine that can be difficult to reason about due to duplicated
> code and a large number of branch targets.
>
> This patch factors the common logic out
On 1/6/2016 2:01 PM, Chuck Lever wrote:
what is the URL for the branch I should rebase on?
k.o/for-4.5 on Doug's kernel.org tree
--
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
On Wednesday 06 January 2016 05:48 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Wed, Jan 06, 2016 at 11:45:22AM +0530, Laxman Dewangan wrote:
Enhanced transient response (ETR) will affect the configuration of CKADV.
+-maxim,junction-temp-warning: Junction temp warning on which
On Wed, Jan 06, 2016 at 02:22:41PM +0200, Or Gerlitz wrote:
> As I wrote here, the bits are already @ kernel.org
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git k.o/for-4.5
Ok, that's a little confusing.
Doug, any chance you could settle on one tree? I don't really care
which
> On Jan 6, 2016, at 7:01 AM, Chuck Lever wrote:
>
>
>> On Jan 4, 2016, at 2:36 PM, J. Bruce Fields wrote:
>>
>> On Sun, Jan 03, 2016 at 09:53:20PM -0500, Doug Ledford wrote:
>>> On 01/03/2016 08:44 PM, Stephen Rothwell wrote:
Hi all,
On Thu, 31 Dec 2015 13:30:22 +1100
Add basic support for the sil902x RGB -> HDMI bridge.
This driver does not support audio output yet.
Signed-off-by: Boris Brezillon
---
Hello,
This patch is only adding basic support for the sil9022 chip.
As stated in the commit log, there's no audio support, but the
driver also hardcodes a lot
On Wed 06-01-16 15:48:36, Sergey Senozhatsky wrote:
> On (01/05/16 15:37), Jan Kara wrote:
> > > How about setting 'sync_print' to 'true' in...
> > > bust_spinlocks() /* only set to true */
> > > or
> > > console_verbose() /* um... may be... */
> > > or
> > > having a separate one-liner for
On Wed, Jan 06, 2016 at 11:45:22AM +0530, Laxman Dewangan wrote:
> Enhanced transient response (ETR) will affect the configuration of CKADV.
> +-maxim,junction-temp-warning: Junction temp warning on which device generates
> + warning interrupts.
This needs to specify what the values
On Wed, Jan 06, 2016 at 07:01:14AM -0500, Chuck Lever wrote:
> Part of the plan was that Doug's tree would be merged before
> Bruce's. But the above problem description looks like the
> maintainer trees were merged into linux-next in the other order.
>
> I'd like to make this simpler for
On Tue, Jan 05, 2016 at 05:33:34PM +, Mark Rutland wrote:
> In work_pending we may skip work if the stacked SPSR value represents
> anything other than an EL0 context. We then immediately invoke the
> kernel_exit 0 macro as part of ret_to_user, assuming a return to EL0.
> This is somewhat
On Wed, Jan 06, 2016 at 08:45:38AM +0700, Khoa Dang Pham wrote:
> Hi Mark,
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is
Hi Boris,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.4-rc8 next-20160106]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Boris-Brezillon/drm-bridge-sil902x/20160106
On Wed, Jan 06, 2016 at 07:59:13PM +0800, Fengguang Wu wrote:
> Hi Guenter,
>
> > However I find that the latest mainline no longer has the error.
> > So let's we ignore this error.
>
> Oops, sorry that's not true -- I was testing rather old mainline HEAD.
>
> Here is the new build log.
>
>
On Fri, Dec 11, 2015 at 06:46:25PM -0800, Sudeep Dutt wrote:
> On Mon, 2015-11-23 at 17:24 +0530, Sudip Mukherjee wrote:
> > Instead of calling release_firmware() on every error and then jumping
> > lets have a common release_firmware() in the error path.
> > This patch also fixes a memory leak
> On Jan 4, 2016, at 2:36 PM, J. Bruce Fields wrote:
>
> On Sun, Jan 03, 2016 at 09:53:20PM -0500, Doug Ledford wrote:
>> On 01/03/2016 08:44 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> On Thu, 31 Dec 2015 13:30:22 +1100 Stephen Rothwell
>>> wrote:
Hi Doug,
Today's
Hi Guenter,
> However I find that the latest mainline no longer has the error.
> So let's we ignore this error.
Oops, sorry that's not true -- I was testing rather old mainline HEAD.
Here is the new build log.
wfg@inn ~/linux% /c/kernel-tests/reproduce-build 398c7500a 168309855
linus/master
On Wed, Jan 06, 2016 at 12:40:23PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 06, 2016 at 01:19:44PM +0200, Michael S. Tsirkin wrote:
> > On Tue, Jan 05, 2016 at 06:27:35PM -0500, Rich Felker wrote:
> > > On Thu, Dec 31, 2015 at 09:09:47PM +0200, Michael S. Tsirkin wrote:
> > > > At the moment,
On Tue, Jan 05, 2016 at 10:30:39PM +0800, Fengguang Wu wrote:
> Hi Guenter,
>
> On Tue, Jan 05, 2016 at 06:02:47AM -0800, Guenter Roeck wrote:
> > On 01/05/2016 12:22 AM, Fengguang Wu wrote:
> > >On Tue, Jan 05, 2016 at 12:09:14AM -0800, Guenter Roeck wrote:
> > >>On 01/04/2016 11:23 PM, kbuild
60] 12899 pages reserved
[ 347.891660] 0 pages cma reserved
[ 347.891660] 0 pages hwpoisoned
--
Complete log is at http://I-love.SAKURA.ne.jp/tmp/serial-20160106.txt.xz .
I don't think this depletion was caused by above patch because the last
invocation was not SysRq-f. I believe
On Wed, Jan 06, 2016 at 01:19:44PM +0200, Michael S. Tsirkin wrote:
> On Tue, Jan 05, 2016 at 06:27:35PM -0500, Rich Felker wrote:
> > On Thu, Dec 31, 2015 at 09:09:47PM +0200, Michael S. Tsirkin wrote:
> > > At the moment, xchg on sh only supports 4 and 1 byte values, so using it
> > > from
Hello Laurent,
On 01/06/2016 07:59 AM, Laurent Pinchart wrote:
> Hi Javier,
>
> Thankk you for the patch.
>
Thanks a lot for your feedback.
> On Monday 04 January 2016 09:25:31 Javier Martinez Canillas wrote:
>> After power-up, the tvp5150 decoder is in a unknown state until the
>> RESETB pin
Hi Steven,
On Mon, Jan 04, 2016 at 10:42:46AM -0500, Steven Rostedt wrote:
> On Wed, 30 Dec 2015 23:06:41 +
> Colin King wrote:
>
> > From: Colin Ian King
> >
> > Fix build warning:
> >
> > scripts/recordmcount.c:589:4: warning: format not a string
> > literal and no format arguments
Hello Laurent,
Thanks a lot for your feedback.
On 01/06/2016 07:56 AM, Laurent Pinchart wrote:
> Hi Javier,
>
> Thank you for the patch.
>
> On Monday 04 January 2016 09:25:32 Javier Martinez Canillas wrote:
>> The video decoder supports either 8-bit 4:2:2 YUV with discrete syncs
>> or 8-bit
Add Sil9022 DT bindings description.
Signed-off-by: Boris Brezillon
---
.../devicetree/bindings/display/bridge/sil902x.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/sil902x.txt
diff --git
Add basic support for the sil902x RGB -> HDMI bridge.
This driver does not support audio output yet.
Signed-off-by: Boris Brezillon
---
Hello,
This patch is only adding basic support for the sil9022 chip.
As stated in the commit log, there's no audio support, but the
driver also hardcodes a lot
On Wed, 6 Jan 2016 09:21:06 +0100
Peter Zijlstra wrote:
> On Wed, Jan 06, 2016 at 09:16:43AM +0100, Peter Zijlstra wrote:
> > On Tue, Jan 05, 2016 at 09:42:27PM +, One Thousand Gnomes wrote:
> > > > It suffers the typical problems all those constructs do; namely it
> > > > wrecks
On Wed, Jan 06, 2016 at 11:00:31AM +, Matt Fleming wrote:
> On Wed, 06 Jan, at 11:47:20AM, Paolo Bonzini wrote:
> >
> > Without testing the problematic scenario explicitly (32-bit UEFI
> > kernel), I think this patch and 26/91 should not be backported to
> > kernels that do not have
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Hennerich
commit 03fe472ef33b7f31fbd11d300dbb3fdab9c00fd4 upstream.
i2c_master_send() returns the number of bytes transferred on success while
the ad5064 driver expects that
Commit 0e748234293f ("mmc: sdhci: Add size for caller in init+register")
allows users of sdhci_pltfm to allocate private space in calls to
sdhci_pltfm_init+sdhci_pltfm_register. This patch migrates the sdhci
esdhc-imx driver to this allocation.
Signed-off-by: Jisheng Zhang
Acked-by: Arnd
Commit 0e748234293f ("mmc: sdhci: Add size for caller in init+register")
allows users of sdhci_pltfm to allocate private space in calls to
sdhci_pltfm_init+sdhci_pltfm_register. This patch migrates the
sdhci-of-arasan driver to this allocation.
Signed-off-by: Jisheng Zhang
Acked-by: Arnd
Commit 0e748234293f ("mmc: sdhci: Add size for caller in init+register")
allows users of sdhci_pltfm to allocate private space in calls to
sdhci_pltfm_init+sdhci_pltfm_register. This patch migrates sdhci-bcm2835
to this allocation.
Signed-off-by: Jisheng Zhang
Acked-by: Arnd Bergmann
---
Commit 0e748234293f ("mmc: sdhci: Add size for caller in init+register")
allows users of sdhci_pltfm to allocate private space in calls to
sdhci_pltfm_init+sdhci_pltfm_register. This patch migrates the
sdhci-of-at91 driver to this allocation.
Signed-off-by: Jisheng Zhang
Acked-by: Arnd Bergmann
Commit 0e748234293f ("mmc: sdhci: Add size for caller in init+register")
allows users of sdhci_pltfm to allocate private space in calls to
sdhci_pltfm_init+sdhci_pltfm_register. This patch migrates sdhci-msm
to this allocation.
Signed-off-by: Jisheng Zhang
Acked-by: Arnd Bergmann
---
There's no need to allocate one sdhci_msm_pdata for each sdhci_msm_host.
This patch removes the sdhci_msm_pdata member from sdhci_msm_host and
uses one static global sdhci_msm_pdata for all sdhci msm hosts. It also
marks sdhci_msm_ops as const.
Signed-off-by: Jisheng Zhang
---
On 06/01/16 10:07, Javi Merino wrote:
On Wed, Jan 06, 2016 at 04:53:44PM +0800, Leo Yan wrote:
k_po/k_pu are two proportional term constants and essentially they have
fixed ratio compared with sustainable power. In current implementation,
k_po and k_pu are absolute value after calculation and
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lars-Peter Clausen
commit 5dcbe97bedd6ba4b0f574a96cc2e293d26f3d857 upstream.
The ad5629/ad5669 are the I2C variant of the ad5628/ad5668, which has a SPI
interface. They are mostly
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Betker
commit a57f8dac46fbac5ab0e31aef1a98b3f6eb30c079 upstream.
The scaling factor for VREFN is 3.0/4096 (not 1.0/4096), just as for
VREFP. This is not immediately obvious
On Wed, Jan 06, 2016 at 09:54:57AM +0900, Namhyung Kim wrote:
> When a perf.data file has multiple events, it's likely to be similar
> (tracepoint) events. In that case, they might have same field name so
> add all of them to sort keys instead of bailing out.
>
> In addition, it contains a
This is the start of the review cycle for the Linux 3.16.7-ckt22 stable kernel.
This version contains 126 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vladimir Zapolskiy
commit 01bb70ae0b98d266fa3e860482c7ce22fa482a6e upstream.
If common clock framework is configured, the driver generates a warning,
which is fixed by this change:
On Tue, Jan 05, 2016 at 06:27:35PM -0500, Rich Felker wrote:
> On Thu, Dec 31, 2015 at 09:09:47PM +0200, Michael S. Tsirkin wrote:
> > At the moment, xchg on sh only supports 4 and 1 byte values, so using it
> > from smp_store_mb means attempts to store a 2 byte value using this
> > macro fail.
>
Hi Guenter,
On Wed, Dec 23, 2015 at 04:52:51PM -0800, Guenter Roeck wrote:
> Hi all,
>
> since commit 60792ad349f3 ("arm64: kernel: enforce pmuserenr_el0
> initialization
> and restore"), my arm64 qemu tests of linux-next are failing. After this
> commit,
> qemu does not display any output.
>
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lars-Peter Clausen
commit 785171fd6cd7dcd7ada5a733b6a2d44ec566c3a0 upstream.
While the datasheet for the AD7785 lists 0xXB as the product ID the actual
product ID is 0xX3.
Fix the
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aleksander Morgado
commit e07af133c3e2716db25e3e1e1d9f10c2088e9c1a upstream.
Also known as Verizon U620L.
The device is modeswitched from 1410:9020 to 1410:9022 by selecting the
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lorenzo Pieralisi
commit de818bd4522c40ea02a81b387d2fa86f989c9623 upstream.
The function graph tracer adds instrumentation that is required to trace
both entry and exit of a
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
commit 59536da34513c594af2a6fd35ba65ea45b6960a1 upstream.
The DEVICE_HWI type was added under the faulty assumption that Huawei
devices based on
Hi Javi,
On Wed, Jan 06, 2016 at 10:07:13AM +, Javi Merino wrote:
> On Wed, Jan 06, 2016 at 04:53:44PM +0800, Leo Yan wrote:
> > k_po/k_pu are two proportional term constants and essentially they have
> > fixed ratio compared with sustainable power. In current implementation,
> > k_po and
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yang Shi
commit 92e788b749862ebe9920360513a718e5dd4da7a9 upstream.
As previously reported, some userspace applications depend on bogomips
showed by /proc/cpuinfo. Although there is
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Nyman
commit dad67d5f3d0efe01d38c6cebcb6698280e51927b upstream.
Clear device initiated resume variables once device is fully up and running
in U0 state.
Resume needs to be
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Woodhouse
commit 1bcb49e663f88bccee35b8688e6a3da2bea31fd4 upstream.
The Honeywell HGI80 is a wireless interface to the evohome connected
thermostat. It uses a TI 3410
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jani Nikula
commit 1b9448b071caa7d10bb2569fabe3020a2c25ae59 upstream.
Unsurprisingly macbooks have backlights, just the VBT doesn't seem to
know it in this case.
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Imre Deak
commit fd0fe6acf1dd88aabfbf383f7e4c16315387a7b7 upstream.
After Damien's D3 fix I started to get runtime suspend residency for the
first time and that revealed a breakage
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li Jun
commit 251b3c8b57481bcecd3f753108e36e7389ce12ac upstream.
Since the ci->role will be set after the host role start is complete, there
will be nobody cared irq during start
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben McCauley
commit b9e51b2b1fda19143f48d182ed7a2943f21e1ae4 upstream.
In some SoCs, dwc3 is implemented as a USB2.0 only
core, meaning that it can't ever achieve SuperSpeed.
On Wed, Jan 06, 2016 at 03:41:23AM +, Wang Nan wrote:
> perf_event__synthesize_mmap_events() issues mmap2 events, but the
> memory of that event is allocated using:
>
> mmap_event = malloc(sizeof(mmap_event->mmap) + machine->id_hdr_size);
>
> If path of mmap source file is long (near
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Slaby
commit 19cd80a214821f4b558560ebd76bfb2c38b4f3d8 upstream.
It is not permitted to set task state before lock. usblp_wwait sets
the state to TASK_INTERRUPTIBLE and calls
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: OGAWA Hirofumi
commit 928a477102c4fc6739883415b66987207e3502f4 upstream.
For the root directory, . and .. are faked (using dir_emit_dots()) and
ctx->pos is reset from 2 to 0.
A
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helge Deller
commit dcbf0d299c00ed4f82ea8d6e359ad88a5182f9b8 upstream.
Drop the MADV_xxK_PAGES flags, which were never used and were from a proposed
API which was never integrated
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrew Cooper
commit 581b7f158fe0383b492acd1ce3fb4e99d4e57808 upstream.
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit ab6b52947545a5355154f64f449f97af9d05845f upstream.
(This should have gone to LKML originally. Sorry for the extra
noise, folks on the cc.)
Background:
Signal
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit efdfa2f7848f64517008136fb41f53c4a1faf93a upstream.
In tpacket_fill_skb() commit c1aad275b029 ("packet: set transport
header before doing xmit") and later on
On (01/06/16 11:21), Jan Kara wrote:
[..]
> >
> > or like this on another setup ([k|u]_ts updated to u64)
> >
> > # cat /proc/1/time_in_console_unlock
> > kern:[12.755920] user:[38.367332]
>
> So maybe that is worth addressing if it bothers you but please as a
> separate patch set. This seems
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: lucien
commit ed5a377d87dc4c87fb3e1f7f698cba38cd893103 upstream.
now sctp auth cannot work well when setting a hmacid manually, which
is caused by that we didn't use the network
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Luca Porzio
commit d3df0465db00cf4ed9f90d0bfc3b827d32b9c796 upstream.
Anytime a write operation is performed with Reliable Write flag enabled,
the eMMC device is enforced to bypass
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 3c70c132488794e2489ab045559b0ce0afcf17de upstream.
Packet sockets can be used by various net devices and are not
really restricted to ARPHRD_ETHER device
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 5cfb4c8d05b4409c4044cb9c05b19705c1d9818b upstream.
Since it's introduction in commit 69e3c75f4d54 ("net: TX_RING and
packet mmap"), TX_RING could be used from
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kamal Mostafa
commit d7475de58575c904818efa369c82e88c6648ce2e upstream.
Use the local uapi headers to keep in sync with "recently" added #define's
(e.g. SKF_AD_VLAN_TPID).
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Junxiao Bi
commit 8f1eb48758aacf6c1ffce18179295adbf3bd7640 upstream.
New created file's mode is not masked with umask, and this makes umask not
work for ocfs2 volume.
Fixes:
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Geert Uytterhoeven
commit cf89752645e47d86ba8a4157f4b121fcb33434c5 upstream.
fs/cachefiles/rdwr.c: In function ‘cachefiles_write_page’:
fs/cachefiles/rdwr.c:882: warning: ‘ret’ may
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?=
commit 705e63d2b29c8bbf091119084544d353bda70393 upstream.
There is a bit of a mess in the order of arguments to the ulpi write
callback. There is
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rainer Weikusat
commit 7d267278a9ece963d77eefec61630223fce08c6c upstream.
Rainer Weikusat writes:
An AF_UNIX datagram socket being the client in an n:1 association with
some server
3.16.7-ckt22 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sabrina Dubroca
commit e639b8d8a7a728f0b05ef2df6cb6b45dc3d4e556 upstream.
Reset pskb in macvlan_handle_frame in case skb_share_check returned a
clone.
Fixes: 8a4eb5734e8d ("net:
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> The changes in this series include the following:
>
> 1.Adding transitivity uniformly to rcu_node structure ->lock
> acquisitions. (This is implemented by the first two commits
> on top of v4.4-rc2 due to the pervasive nature of
601 - 700 of 1814 matches
Mail list logo
