Hi Pete,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: bc33b0ca11e3df46a4fa7639ba488c9d4911
commit: d0b73b488c55df905ea8faaad079f8535629ed26 xtensa: Add config files for
Diamond 233L - Rev C processor variant
Commit 63f53dea0c9866e9 ("mm: warn about allocations which stall for
too long") was a great step for reducing possibility of silent hang up
problem caused by memory allocation stalls [1]. But it became clear
that Michal Hocko is not going to make warn_alloc() bullet proof [2].
Therefore, I again pr
On Sun, 6 Nov 2016 07:09:57 +0800
kbuild test robot wrote:
> Hi Emese,
>
> FYI, the error/warning still remains.
>
>++(scripts/gcc-plugin.sh:12): main(): gcc-4.6 -E -x c++ - -o /dev/null
> -Iscripts/gcc-plugins -Iplugin/include
>scripts/Makefile.gcc-plugins:30: warning: your gcc install
Conservative governor changes the CPU frequency in steps.
That means that if a CPU runs at max frequency, it will need several
sampling periods to return at min frequency when the workload
is finished.
If the timer that calculates the load and target frequency is deferred,
the governor might need
-the-capi-c-file-that-fixes-one-instance-of-the-following-error-ERROR-do-not-use-assignment-in-if-condition/20161106-165820
config: i386-randconfig-x077-201645 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
On Sun, Nov 6, 2016 at 12:38 AM, Andi Kleen wrote:
> Vitaly Wool writes:
>
>> Most of z3fold operations are in-page, such as modifying z3fold
>> page header or moving z3fold objects within a page. Taking
>> per-pool spinlock to protect per-page objects is therefore
>> suboptimal, and the idea of
Am 05.11.2016 um 17:49 schrieb Rob Clark:
On Sat, Nov 5, 2016 at 12:38 PM, Eric Engestrom wrote:
On Saturday, 2016-11-05 13:11:36 +0100, Christian König wrote:
Am 05.11.2016 um 02:33 schrieb Eric Engestrom:
+typedef char drm_format_name_buf[32];
Please don't use a typedef for this, just defi
Hello.
On 11/5/2016 6:11 PM, Philippe Reynes wrote:
When moving from typhoon_get_settings to typhoon_getlink_ksettings
in the commit commit f7a5537cd2a5 ("net: 3com: typhoon: use new api
One "commit" is enough. :-)
ethtool_{get|set}_link_ksettings"), we use a local variable supported
but
On Thu, Nov 3, 2016 at 1:34 PM, Andy Yan wrote:
> Add basic support for rk1108 soc
>
> Signed-off-by: Andy Yan
I only see this patch from the series, I guess this is the only
patch affecting pin control so thanks for not spamming :)
Please resend with Heiko's requested fixes and his Reviewed-b
Staging: i4l: act2000:
Signed-off-by: Naeil ZOUEIDI
---
drivers/staging/i4l/act2000/capi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/i4l/act2000/capi.c
b/drivers/staging/i4l/act2000/capi.c
index b494917..62dee39 100644
--- a/drivers/staging/i4l/act2000/
Hi,
On 05-11-16 11:40, Paul Burton wrote:
On Friday, 4 November 2016 14:22:17 GMT Hans de Goede wrote:
Hi,
On 04-11-16 13:30, Paul Burton wrote:
Hi Hans,
On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
Hi All,
While booting 4.9-rc# for the first time on an Allwinner A33 tablet
On 01.11.2016 12:47, Jani Nikula wrote:
> On Tue, 01 Nov 2016, Martin Kepplinger wrote:
>> I'll come up with a nouveau system example and it was quite easy to bisect.
>> To quote the merge commit msg:
>> This also required some changes outside of the IOMMU code, but these are
>> acked by the res
On 31.10.2016 00:32, Larry Finger wrote:
> With the 4.9-rcX kernel, my Dell Latitude D600 laptop has a kernel panic on
> shutdown in routine radeon_connector_unregister(). This problem has been
> bisected to show that commit a481daa88fd4 ("drm/radeon: always apply pci
> shutdown callbacks") is a
On 03/11/16 12:56, Brian Masney wrote:
> There were several places where the driver would first call
> i2c_smbus_write_byte() to select the register on the device, and then
> call i2c_smbus_read_byte() to get the contents of that register. The
> code would look roughly like:
>
> /* Select register
On 03/11/16 12:56, Brian Masney wrote:
> There were several places where the driver would first call
> i2c_smbus_write_byte() to select the register on the device, and then
> call i2c_smbus_read_byte() to get the contents of that register. The
> code would look roughly like:
>
> /* Select register
Am 2016-11-06 um 12:21 schrieb Thorsten Leemhuis:
> On 01.11.2016 12:47, Jani Nikula wrote:
>> On Tue, 01 Nov 2016, Martin Kepplinger wrote:
>>> I'll come up with a nouveau system example and it was quite easy to bisect.
>>> To quote the merge commit msg:
>>> This also required some changes outsi
On 03/11/16 12:56, Brian Masney wrote:
> taos_probe() queries the all of the sensor's registers and loads all of
> the values into a buffer stored on the stack. Only the chip ID register
> was actually used. Change the probe function to just query the chip ID
> register on the device.
>
> Verified
On 03/11/16 12:56, Brian Masney wrote:
> in taos_defaults()
>
> The comments in taos_defaults() appear after the line of code
> that they apply to. This patch moves the comments so that they appear
> before the code. Some of the comments were updated to be more
> informative.
>
> Signed-off-by: B
On 03/11/16 12:56, Brian Masney wrote:
> taos_chip_on() explicitly turns the sensor power on and then writes the
> 8 registers that are stored in taos_config. The first register in
> taos_config is the CONTROL register and the configuration is set to
> turn the power off. The existing state sequenc
On 03/11/16 12:56, Brian Masney wrote:
> in_illuminance_lux_table_store() shuts down the chip, updates the
> contents of the lux table, and then turns the chip back on. The values
> in lux table are not used by the chip and are only used internally by
> the driver. It is not necessary to change the
On 03/11/16 12:56, Brian Masney wrote:
> taos_als_calibrate() queries the control register to determine if the
> unit is powered on and has the ADC enabled. It then queries the same
> register a second time to determine if the ADC reading is valid. This
> patch removes the redundant i2c_smbus_read_
On 03/11/16 12:56, Brian Masney wrote:
> in_illuminance_calibrate_store() did not check to see if the chip is
> suspended. This patch adds the proper check. The return value from
> taos_als_calibrate() was also not checked in this function, so the
> proper check was also added while changes are bei
On 03/11/16 12:56, Brian Masney wrote:
> taos_probe() calls i2c_smbus_write_byte() to select the control
> register, however there is no subsequent calls to i2c_smbus_read_byte().
> The write call is unnecessary and is removed by this patch.
>
> Verified that the driver still functions correctly u
On 03/11/16 12:56, Brian Masney wrote:
> When updating the in_illuminance_calibscale and
> in_illuminance_integration_time sysfs attributes, these values were not
> actually written to the chip. The chip would continue to use the old
> parameters. Extracted out tsl2583_set_als_gain() and
> tsl2583_
JFYI: I added below report to the list of regressions for Linux 4.9.
I'll watch this thread for further updates on this issue to document
progress in my weekly reports. Please let me know via
regressi...@leemhuis.info in case the discussion moves to a different
place (bugzilla or another mail threa
Staging: i4l: act200:
Signed-off-by: Naeil Zoueidi
---
drivers/staging/i4l/act2000/capi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/i4l/act2000/capi.c
b/drivers/staging/i4l/act2000/capi.c
index 62f5629..b494917 100644
--- a/drivers/staging/i4l/act2000
The boolean vmci_page_files is used to differentiate between old style
VMX and new-style, but the code actually only used this variable
at one point in an if/else that had no effect so it can be removed.
Fixes: 06164d2b72aa ("VMCI: queue pairs implementation.")
Signed-off-by: Nicholas Mc Guire
-
The condition calls the same code, further the code called does not
differentiate between old/new-style VMX anyway so the if/else here
is simply not needed.
Fixes: 06164d2b72aa ("VMCI: queue pairs implementation.")
Signed-off-by: Nicholas Mc Guire
---
problem found by coccinelle
drivers/misc/
The port assignment in the if case should be to AUX not MAIN.
Fixes: commit baa170229095 ("rtlwifi: btcoexist: Implement antenna selection")
Signed-off-by: Nicholas Mc Guire
---
problem located by coccinelle
in:
drivers/net/wireless/realtek/rtlwifi/btcoexist/halbtcoutsrc.c:exhalbtc_set_ant_num()
Am 2016-11-06 um 12:43 schrieb Martin Kepplinger:
> Am 2016-11-06 um 12:21 schrieb Thorsten Leemhuis:
>> On 01.11.2016 12:47, Jani Nikula wrote:
>>> On Tue, 01 Nov 2016, Martin Kepplinger wrote:
I'll come up with a nouveau system example and it was quite easy to
bisect. To quote the mer
Hi Matt,
please doublecheck me on this but I think we're fine using an unsigned
long.
Thanks.
---
From: Borislav Petkov
Date: Sun, 6 Nov 2016 13:49:10 +0100
Subject: [PATCH] x86/efi: Fix EFI memmap pointer size warning
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-E
On Sun, Nov 6, 2016 at 4:47 AM, Christian König
wrote:
> Am 05.11.2016 um 17:49 schrieb Rob Clark:
>>
>> On Sat, Nov 5, 2016 at 12:38 PM, Eric Engestrom wrote:
>>>
>>> On Saturday, 2016-11-05 13:11:36 +0100, Christian König wrote:
Am 05.11.2016 um 02:33 schrieb Eric Engestrom:
>
>>>
Lo! On 01.11.2016 09:18, Paul Bolle wrote:
> On Sun, 2016-10-30 at 14:20 +0100, Thorsten Leemhuis wrote:
>> As always: Are you aware of any other regressions? Then please let me
>> know (simply CC regressi...@leemhuis.info).
> Do build regressions count?
That's a good question.
> Because I was tr
Hi,
On Sat, Nov 05, 2016 at 04:05:23PM +0800, hao zhang wrote:
> Hi,
>
> This patch add the allwinner soc a64 dma support on already done driver
> sun6i-dma.
>
> A64 is a 64bit SOC, it has 8 channel DMA which flexible
> data width of 8/16/32/64-bit. Detailed info about it is on
> Allwinner_A64
On Sat, Nov 05, 2016 at 04:05:48PM +0800, Hao Zhang wrote:
> Add soc a64 dma support.
>
> Signed-off-by: Hao Zhang
> ---
> drivers/dma/sun6i-dma.c | 19 +++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
> index 8346199..00f
Hi! On 26.10.2016 17:01, Andy Shevchenko wrote:
> On Wed, 2016-10-26 at 15:06 +0100, Bryan O'Donoghue wrote:
>> On Tue, 2016-10-25 at 08:19 +0200, Lukas Wunner wrote:
>
>> So the conclusion is to apply this patch now and go and look further @
>> locking in a separate series right ? There's not much
Withdrawing this patch as it breaks restoring brightness
on resume.
Thanks,
Jacek Anaszewski
On 10/05/2016 12:03 PM, Jacek Anaszewski wrote:
delayed_set_value property was introduced in the commit
d23a22a74fde ("leds: delay led_set_brightness if stopping soft-blink").
Its aim was to allow calli
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/amd/xgbe/xgbe-ethtool.c | 68 ++
1 files changed, 37 insertions(+), 31 deletions(-)
diff --git a/drivers/n
When moving from typhoon_get_settings to typhoon_getlink_ksettings
in the commit f7a5537cd2a5 ("net: 3com: typhoon: use new api
ethtool_{get|set}_link_ksettings"), we use a local variable supported
but we forgot to update the struct ethtool_link_ksettings with
this value.
We also initialize advert
The affected files have been modified to remove redundant spaces after
casts to solve checkpatch.pl checks.
Signed-off-by: Shiva Kerdel
---
drivers/staging/speakup/main.c | 42 ++---
drivers/staging/speakup/selection.c | 2 +-
drivers/staging/speakup/seriali
On Sun, Nov 06, 2016 at 12:03:53PM +, Jonathan Cameron wrote:
> On 03/11/16 12:56, Brian Masney wrote:
> > When updating the in_illuminance_calibscale and
> > in_illuminance_integration_time sysfs attributes, these values were not
> > actually written to the chip. The chip would continue to use
Hi,
On 06-11-16 12:11, Icenowy Zheng wrote:
All A33 Q8 tablets features a LCD panel, with a resolution of either
800x480 or 1024x600.
Add "bone" device nodes to the device tree.
Bone ?
Signed-off-by: Icenowy Zheng
He, as discussed in the other thread since sun8i-a33-q8-tablet.dts
is use
On Tue, October 25, 2016 3:19 pm, Dave Chinner wrote:
> On Tue, Oct 25, 2016 at 05:50:43AM -0600, Stephen Bates wrote:
>>
>> Dave are you saying that even for local mappings of files on a DAX
>> capable system it is possible for the mappings to move on you unless the
>> FS supports locking?
>>
>
>
Hi! Here is my third regression report for Linux 4.9. It lists 17
regressions I'm aware of. 6 of them are new; 3 got fixed since
last weeks report (a fourth looks fixed as well). The console
problem ("console: don't prefer first registered [...]") got
reported to me multiple times, but the revert t
Hi,
On 04-11-16 17:46, Hans de Goede wrote:
Hi,
On 04-11-16 17:06, Jacek Anaszewski wrote:
Hi Hans,
On 11/04/2016 12:53 PM, Hans de Goede wrote:
Hi,
On 04-11-16 08:52, Jacek Anaszewski wrote:
Initially the claim about no need for lock in brightness_show()
was valid as the function was just
Hi.
Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> So it's once again a Saturday afternoon rather than Sunday, this time
> because I felt this rc was already big enough.
With kernel 4.9-rc4 I saw gfx corruptions like
https://martin-steigerwald.de/tmp/display-issues-with-ker
Hi all,
We are pleased to announce another update of Intel GVT-g for Xen.
Intel GVT-g is a full GPU virtualization solution with mediated pass-through,
starting from 4th generation Intel Core(TM) processors with Intel Graphics
processors. A virtual GPU instance is maintained for each VM, with p
On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> Hi.
>
> Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > So it's once again a Saturday afternoon rather than Sunday, this time
> > because I felt this rc was already big enough.
>
> With kernel 4.9-rc4 I saw gf
Hi all,
While spending efforts for upstreaming, we are pleased to announce another
update of Intel GVT-g for KVM.
Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with
mediated pass-through, starting from 5th generation Intel Core(TM) processors
with Intel Graphics proc
Am Sonntag, 6. November 2016, 17:25:15 CET schrieb Mihai Donțu:
> On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> > Hi.
> >
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > > So it's once again a Saturday afternoon rather than Sunday, this time
> > > becaus
Since v4.9-rc4 I get following crash in dvb-usb-cinergyT2 module.
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [] __mutex_lock_slowpath+0x6f/0x100
PGD 0
Oops: 0002 [#1] SMP
Modules lin
Hi Linus,
Please pull hwmon fixes for Linux v4.9-rc5 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.9-rc5
Thanks,
Guenter
--
The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:
Linux 4.9-rc2 (2016-1
On 05.11.2016 23:38, Gabriel C wrote:
Hello ,
I've tested 4.9-rcX and Linus git tree and have on this box the following
messages :
.
Nov 05 20:26:40 zwerg kernel: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 05 20:26:40 zwerg kernel: Tasks blocked on level-0 rcu_node (C
Hi All,
> On 11/05/2016 07:50 AM, Heinrich Schuchardt wrote:
> >fw_rev_major and fw_rev_minor are defined as int.
> >Use %d to print them.
> >
> >Signed-off-by: Heinrich Schuchardt
> >---
> > drivers/watchdog/pcwd_pci.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/
On Mon, Oct 31, 2016 at 01:44:55PM -0600, Chris Mason wrote:
> On Mon, Oct 31, 2016 at 12:35:16PM -0700, Linus Torvalds wrote:
> >On Mon, Oct 31, 2016 at 11:55 AM, Dave Jones
> >wrote:
> >>
> >> BUG: Bad page state in process kworker/u8:12 pfn:4e0e39
> >> page:ea0013838e40 count:0 ma
Hi,
I am regulary running some tests with qemu-system-cris, but getting following
stacktraces on boot now (with 4.8.6, 4.7.9 worked fine):
[7.260691] Unable to handle kernel NULL pointer dereference
[7.260919] Linux 4.8.6-1 #4 Sun Nov 6 17:48:18 CET 2016
[7.260955] Oops:
[7.2
Signed-off-by: Sanjeev Gupta
---
Documentation/development-process/1.Intro.rst | 4 ++--
Documentation/development-process/6.Followthrough.rst | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/development-process/1.Intro.rst
b/Documentation/developmen
'lustre_cfg_new()' does not return NULL but ERR_PTR(-ENOMEM)
So IS_ERR should be used to check the return value.
Signed-off-by: Christophe JAILLET
---
drivers/staging/lustre/lustre/obdclass/obd_config.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustr
'lustre_cfg_new()' can return ERR_PTR(-ENOMEM).
Handle these errors and propagate the error code to the callers.
Error handling has been rearranged in 'lustre_process_log()' with the
addition of a label in order to free some resources.
Signed-off-by: Christophe JAILLET
---
drivers/staging/lustr
On Sun, Nov 06, 2016 at 02:43:33PM +0100, Thorsten Leemhuis wrote:
> On 26.10.2016 17:01, Andy Shevchenko wrote:
> > On Wed, 2016-10-26 at 15:06 +0100, Bryan O'Donoghue wrote:
> >> So the conclusion is to apply this patch now and go and look further @
> >> locking in a separate series right ? There
Hello!
On Nov 6, 2016, at 12:11 PM, Christophe JAILLET wrote:
> 'lustre_cfg_new()' can return ERR_PTR(-ENOMEM).
> Handle these errors and propagate the error code to the callers.
>
> Error handling has been rearranged in 'lustre_process_log()' with the
> addition of a label in order to free some
I will post xfs tests that validate mount and range checking.
I will keep the policy same as what the RFC suggests for now.
Clamping can be verified once vfs is transitioned to using time64_t.
Thanks,
Deepa
From: Noam Camus
Till now we used clockevent from generic ARC driver.
This was enough as long as we worked with simple multicore SoC.
When we are working with multithread SoC each HW thread can be
scheduled to receive timer interrupt using timer mask register.
This patch will provide a way to con
On Tue, 1 Nov 2016 13:16:28 -0500
Zach Brown wrote:
> The fields bb_per_die and blocks_per_die are useful determining the
> number of bad blocks a MTD needs to allocate. How they are set will
> depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
> table.
>
> Signed-off-by: Za
Am Sonntag, 6. November 2016, 17:25:15 CET schrieb Mihai Donțu:
> On Sun, 06 Nov 2016 15:48:36 +0100 Martin Steigerwald wrote:
> > Hi.
> >
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> > > So it's once again a Saturday afternoon rather than Sunday, this time
> > > becaus
On Tue, 1 Nov 2016 13:16:25 -0500
Zach Brown wrote:
> For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
> of bad blocks per LUN that will be encountered over the lifetime of the
> device,
> so we can use that information to get a more accurate (and smaller) value for
On Tue, 1 Nov 2016 13:32:32 -0500
Zach Brown wrote:
> On Tue, Nov 01, 2016 at 02:50:58PM +0100, Boris Brezillon wrote:
> > On Fri, 28 Oct 2016 15:27:42 -0500
> > Zach Brown wrote:
> >
> > > The fields bb_per_lun and blocks_per_lun are useful determining the
> > > number of bad blocks a MTD nee
On 06/11/16 14:23, Brian Masney wrote:
> On Sun, Nov 06, 2016 at 12:03:53PM +, Jonathan Cameron wrote:
>> On 03/11/16 12:56, Brian Masney wrote:
>>> When updating the in_illuminance_calibscale and
>>> in_illuminance_integration_time sysfs attributes, these values were not
>>> actually written t
From: Noam Camus
This new header file is for NPS400 SoC (part of ARC architecture).
The header file includes macros for save/restore of HW scheduling.
The control of HW scheduling is achieved by writing core registers.
This code was moved from arc/plat-eznps so it can be used
from drivers/clockso
Hi Icenowy,
This patch (2/2) should be before the first one.
The first patch allows adjusting of the PLL and the second fixes a
problem with the adjustment of the PLL.
You should fix the problem before allowing the adjustment of the PLL.
That way, if someone builds the kernel between your two pa
May I ask some comments, please?
Thanks,
SeongJae Park
On Tue, Nov 1, 2016 at 5:27 AM, SeongJae Park wrote:
> This patchset applies ReST conversion effort for HOWTO document to its Korean
> translation. It also contains fixup of trivial nitpicks in the document and
> the translation.
>
> Chang
On Fri, 4 Nov 2016 19:43:01 +0900
Masahiro Yamada wrote:
> The nand_scan_ident/tail() returns an appropriate error value when
> it fails. Use it instead of the fixed error code -ENXIO.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> drivers/mtd/nand/lpc32xx_mlc.c | 10 --
> drivers/mtd
On Sat, Nov 05, 2016 at 11:54:28PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Tue, Sep 6, 2016 at 10:46 PM, Maxime Ripard
> wrote:
> > The A33 has a significantly different pipeline, with components that differ
> > too.
> >
> > Make sure we had compatible for them.
> >
> > Signed-off-by: Maxime Ripa
On Fri, Nov 04, 2016 at 09:08:11AM +0800, Chen-Yu Tsai wrote:
> On Fri, Nov 4, 2016 at 1:36 AM, Maxime Ripard
> wrote:
> > Hi,
> >
> > On Thu, Nov 03, 2016 at 03:55:48PM +0800, Chen-Yu Tsai wrote:
> >> +/* headphone controls */
> >> +static const char * const sun6i_codec_hp_src_enum_text[] = {
> >
On Sunday 06 November 2016 01:01 AM, Anton Blanchard wrote:
> Hi,
>
>> kprobe, uprobe, hw-breakpoint and xmon are the only user of
>> emulate_step.
>>
>> Kprobe / uprobe single-steps instruction if they can't emulate it, so
>> there is no problem with them. As I mention, hw-breakpoint is broken.
On Sat, Nov 05, 2016 at 10:38:29PM +0800, Icenowy Zheng wrote:
> Allwinner A64 have two HCI USB controllers, a OTG controller and a USB
> PHY device which have two ports. One of the port is wired to both a HCI
> USB controller and the OTG controller, which is currently not supported.
> The another
Hi,
On Sat, Nov 05, 2016 at 10:38:30PM +0800, Icenowy Zheng wrote:
> Pine64 have two USB Type-A ports, which are wired to the two ports of
> A64 USB PHY, and the lower port is the EHCI/OHCI1 port.
>
> Enable the necessary nodes to enable the lower USB port to work.
>
> Signed-off-by: Icenowy Zhe
On Wed, Oct 26, 2016 at 2:12 PM, Miklos Szeredi wrote:
> On Tue, Oct 25, 2016 at 1:57 PM, Raphael Hertzog wrote:
>
>> Do you plan to make it the default in the future when it has been
>> available for a while?
>>
>> Barring any regression introduced by your patch, it seems that the feature
>> is
From: K. Y. Srinivasan
Some miscellaneous fixes and enhancements.
V2: Fixed a build issue reported by Greg. Only Patch # 13 is affected.
V3: Address Stephen's comment. Only patch 3 is affected.
Alex Ng (6):
Drivers: hv: utils: Fix the mapping between host version and protocol
to use
Dri
Some miscellaneous fixes and enhancements.
V2: Fixed a build issue reported by Greg. Only Patch # 13 is affected.
V3: Address Stephen's comment. Only patch 3 is affected.
Alex Ng (6):
Drivers: hv: utils: Fix the mapping between host version and protocol
to use
Drivers: hv: balloon: Disabl
From: K. Y. Srinivasan
One of the factors that can result in the host concluding that a given
guest in mounting a DOS attack is if the guest generates interrupts
to the host when the host is not expecting it. If these "spurious"
interrupts reach a certain rate, the host can throttle the guest to
From: Alex Ng
We should intentionally declare the protocols to use for every known host
and default to using the latest protocol if the host is unknown or new.
Signed-off-by: Alex Ng
Signed-off-by: K. Y. Srinivasan
---
V3: Addressed Stephen's comment
drivers/hv/hv_util.c |9 +
From: K. Y. Srinivasan
Signal the host when we determine the host is to be signaled -
on th read path. The currrent code determines the need to signal in the
ringbuffer code and actually issues the signal elsewhere. This can result
in the host viewing this interrupt as spurious since the host may
From: Alex Ng
Increase the timeout of backup operations. When system is under I/O load,
it needs more time to freeze. These timeout values should also match the
host timeout values more closely.
Signed-off-by: Alex Ng
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv_snapshot.c |8 ++-
From: Alex Ng
If the guest does not support memory hotplugging, it should respond to
the host with zero pages added and successful result code. This signals
to the host that hotplugging is not supported and the host will avoid
sending future hot-add requests.
Signed-off-by: Alex Ng
Signed-off-b
From: Weibing Zhang
Remove unnecessary header files and netlink related code as the daemons
do not use netlink to communicate with the kernel now.
Signed-off-by: Weibing Zhang
Signed-off-by: K. Y. Srinivasan
---
tools/hv/hv_fcopy_daemon.c |7 ---
tools/hv/hv_kvp_daemon.c |7
From: Alex Ng
Adding log messages to help troubleshoot error cases and transaction
handling.
Signed-off-by: Alex Ng
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv_snapshot.c | 25 +++--
1 files changed, 19 insertions(+), 6 deletions(-)
diff --git a/drivers/hv/hv_snap
From: Weibing Zhang
hv_kvp_daemon.c: In function .kvp_mac_to_if_name.:
hv_kvp_daemon.c:705:2: warning: format not a string literal and no format
arguments [-Wformat-security]
snprintf(dev_id, sizeof(dev_id), kvp_net_dir);
^
hv_kvp_daemon.c:705:2: warning: format not a string literal and no f
From: Weibing Zhang
The link flag pthread is not needed.
Signed-off-by: Weibing Zhang
Signed-off-by: K. Y. Srinivasan
---
tools/hv/Makefile |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/tools/hv/Makefile b/tools/hv/Makefile
index a8c4644..0d1e61b 100644
--- a/tool
From: Alex Ng
Balloon driver was only printing the size of the info blob and not the
actual content. This fixes it so that the info blob (max page count as
configured in Hyper-V) is printed out.
Signed-off-by: Alex Ng
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv_balloon.c |9 +++-
From: Vitaly Kuznetsov
I discovered that at least WS2016TP5 host has 60 seconds timeout for the
ICMSGTYPE_NEGOTIATE message so we need to lower guest's timeout a little
bit to make sure we always respond in time. Let's make it 55 seconds.
Signed-off-by: Vitaly Kuznetsov
Signed-off-by: K. Y. Sri
meson-gx.dtsi was directly derived from meson-gxbb.dtsi, so keep the
copyrights in chronological order to not give a wrong impression.
Fixes: c328666d58aa ("ARM64: dts: amlogic: Add Meson GX dtsi from GXBB")
Cc: Neil Armstrong
Cc: Kevin Hilman
Signed-off-by: Andreas Färber
---
arch/arm64/boot/
From: Alex Ng
Added logging to help troubleshoot common ballooning, hot add,
and versioning issues.
Signed-off-by: Alex Ng
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/hv_balloon.c | 31 ---
1 files changed, 28 insertions(+), 3 deletions(-)
diff --git a/driver
From: Vitaly Kuznetsov
With wrap around mappings in place we can always provide drivers with
direct links to packets on the ring buffer, even when they wrap around.
Do the required updates to get_next_pkt_raw()/put_pkt_raw()
The first version of this commit was reverted (65a532f3d50a) to deal wi
From: K. Y. Srinivasan
Signal the host when we determine the host is to be signaled.
The currrent code determines the need to signal in the ringbuffer
code and actually issues the signal elsewhere. This can result
in the host viewing this interrupt as spurious since the host may also
poll the cha
Hi Randy,
On Sat, Nov 5, 2016 at 9:16 PM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix build errors in sound/soc/fsl/fsl_spdif.c by selecting BITREVERSE.
> Fixes these build errors:
Care to explain why the error is happening?
> sound/built-in.o: In function `spdif_write_channel_status':
>
وقد ظهرت مايكروسوفت آسيا بك البريد الإلكتروني معرف الفائز من $ 900،000،00 دولار
أمريكي ارسال
اسم:
رقم الهاتف المحمول:
الاحتلال :
عنوان:
الرد على هذا رقم البريد الإلكتروني: mox...@outlook.com
From: Markus Elfring
Date: Sun, 6 Nov 2016 20:40:20 +0100
* A function was called over the pointer "setup_if_config" in the data
structure "venc_platform_data". But the return value was not used so far.
Thus assign it to the local variable "ret" which will be checked with
the next statement
Below is the list of build error/warning regressions/improvements in
v4.9-rc4[1] compared to v4.8[2].
Summarized:
- build errors: +278/-3
- build warnings: +1618/-1190
JFYI, when comparing v4.9-rc4[1] to v4.9-rc3[3], the summaries are:
- build errors: +138/-23
- build warnings: +566/-579
I applied this patch to the 4.8.4 kernel driver (that I'm currently
running) and it caused nothing but "frontend 0/0 timed out while
tuning". Is there another patch that should be used in conjunction
with this? If not, this patch breaks the gp8psk driver.
Thanks.
On Tue, Oct 11, 2016 at 3:09 AM,
1 - 100 of 248 matches
Mail list logo
