On Sat, 2015-08-01 at 12:33 -0400, Mike Snitzer wrote:
> On Sat, Aug 01 2015 at 2:58am -0400,
> Ming Lin wrote:
>
> > On Fri, 2015-07-31 at 17:38 -0400, Mike Snitzer wrote:
> > >
> > > OK, once setup, to run the 2 tests in question directly you'd do
> > > something like:
> > >
> > > dmtest
During unbinding the driver was dereferencing a pointer to memory
already freed by power_supply_unregister().
Driver was freeing its internal description of battery through pointers
stored in power_supply structure. However, because the core owns the
power supply instance, after calling
On 03-08-15, 05:50, MyungJoo Ham wrote:
> Acked-by: MyungJoo Ham
>
>
> please let me know when the series is ready to go.
It wouldn't harm even if you apply it without 1/15. So, just go on and
apply :)
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Consider the following case:
Task A trigger lmk with a lock held, while task B try to
get this lock, but unfortunately B is the very culprit task lmk select to
kill. Then B will never be killed, and A will forever select B to kill.
Such dead lock will trigger softlock up issue.
This patch try to
> On 03-08-15, 05:10, MyungJoo Ham wrote:
> > > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> > > is no need to do that again from its callers. Drop it.
> > >
> > > Signed-off-by: Viresh Kumar
> >
> > @ from include/linux/err.h
> > #define IS_ERR_VALUE(x) unlikely((x)
With gcc 5.1 I get:
warning: switch condition has boolean value [-Wswitch-bool]
Signed-off-by: Tomer Barletz
---
drivers/mtd/mtd_blkdevs.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/mtd/mtd_blkdevs.c b/drivers/mtd/mtd_blkdevs.c
index 41acc50..8830475
On 03-08-15, 05:10, MyungJoo Ham wrote:
> > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> > is no need to do that again from its callers. Drop it.
> >
> > Signed-off-by: Viresh Kumar
>
> @ from include/linux/err.h
> #define IS_ERR_VALUE(x) unlikely((x) >= (unsigned
Declare the file_operations structure ll_file_operations as const, as done
elsewhere in the kernel, as there are no modifications to its fields.
Problem found using checkpatch:
WARNING: struct file_operations should normally be const
Signed-off-by: Shraddha Barke
---
On Fri, 2015-07-31 at 14:08 +0530, Viresh Kumar wrote:
> IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> is no need to do that again from its callers. Drop it.
>
> Signed-off-by: Viresh Kumar
> ---
> drivers/target/tcm_fc/tfc_cmd.c | 2 +-
> 1 file changed, 1
On Sun, Aug 02, 2015 at 11:04:22PM +0530, Shraddha Barke wrote:
Your subject says 'Revert "Staging : lustre: Struct file_operations
should be const"'. This patch reverts which commit?
> Declare the file_operations structure ll_file_operations as const, as done
> elsewhere in the kernel, as there
On 2015-08-02 09:51:16, Richard Weinberger wrote:
> Am 02.08.2015 um 03:03 schrieb Tyler Hicks:
> > Thanks for the report and for the patch, Richard!
> >
> > On 2015-07-31 12:23:10, Richard Weinberger wrote:
> >> Mounting the same lower path multiple times should not result
> >> into multiple
On Fri, 31 Jul 2015, Salvatore Mesoraca wrote:
> Without this patch YAMA will not work at all if it is chosen
> as the primary LSM instead of being "stacked".
>
> Signed-off-by: Salvatore Mesoraca
> ---
> security/yama/yama_lsm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
> IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> is no need to do that again from its callers. Drop it.
>
> Signed-off-by: Viresh Kumar
@ from include/linux/err.h
#define IS_ERR_VALUE(x) unlikely((x) >= (unsigned long)-MAX_ERRNO)
...
static inline bool __must_check
On 07/31/2015 07:18 PM, Sekhar Nori wrote:
> On Tuesday 28 July 2015 02:11 PM, Vignesh R wrote:
>> Add qspi memory mapped region entries for DRA7xx based SoCs.
>>
>> Signed-off-by: Vignesh R
>> ---
>> arch/arm/boot/dts/am4372.dtsi | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
The nand controller in IPQ806x is of the 'EBI2 type'. Use the corresponding
compatible string.
Cc: devicet...@vger.kernel.org
Reviewed-by: Andy Gross
Signed-off-by: Archit Taneja
---
arch/arm/boot/dts/qcom-ipq8064.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git
Enable the NAND controller node on the AP148 platform. Provide pinmux
information.
Cc: devicet...@vger.kernel.org
Signed-off-by: Archit Taneja
---
arch/arm/boot/dts/qcom-ipq8064-ap148.dts | 36
1 file changed, 36 insertions(+)
diff --git
Add DT bindings document for the Qualcomm NAND controller driver.
Cc: devicet...@vger.kernel.org
v3:
- Don't use '0x' when specifying nand controller address space
- Add optional property for on-flash bbt usage
Acked-by: Andy Gross
Signed-off-by: Archit Taneja
---
The Qualcomm NAND controller is found in SoCs like IPQ806x, MSM7xx,
MDM9x15 series.
It exists as a sub block inside the IPs EBI2 (External Bus Interface 2)
and QPIC (Qualcomm Parallel Interface Controller). These IPs provide a
broader interface for external slow peripheral devices such as LCD and
Some controllers can access the factory bad block marker from OOB only
when they read it in raw mode. When ECC is enabled, these controllers
discard reading/writing bad block markers, preventing access to them
altogether.
The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks.
This
Add support for the NAND controller driver for SoC's that contain EBI2.
For now, the only SoC upstream that has EBI2 is IPQ806x.
The original version was posted a while back. The main comments were
about the driver not being able to use nand_bbt. This was because the
controller could read factory
On 08/01/2015 02:58 AM, Brian Norris wrote:
> On Tue, Jul 28, 2015 at 02:11:15PM +0530, Vignesh R wrote:
>> Add qspi memory mapped region entries for DRA7xx based SoCs.
>>
>> Signed-off-by: Vignesh R
>> ---
>> arch/arm/boot/dts/am4372.dtsi | 4 +++-
>> 1 file changed, 3 insertions(+), 1
On 07/31/2015 11:49 PM, Mark Brown wrote:
> On Tue, Jul 28, 2015 at 02:11:15PM +0530, Vignesh R wrote:
>> Add qspi memory mapped region entries for DRA7xx based SoCs.
>>
>> Signed-off-by: Vignesh R
>
>> qspi: qspi@4790 {
>> compatible = "ti,am4372-qspi";
Hi,
On 7/31/2015 11:47 PM, Mark Brown wrote:
> On Tue, Jul 28, 2015 at 02:11:12PM +0530, Vignesh R wrote:
>
>> Introduce use_mmap_read field in spi_message struct. This can be set by
>> mtd devices (m25p80) to indicate to spi-master (ti-qspi) to perform
>> memory mapped read. This helps to
> Hello Myungjoo,
>
> On 07/23/2015 10:30 AM, Javier Martinez Canillas wrote:
> > Hello Chanwoo,
> >
> > On 07/23/2015 10:19 AM, Chanwoo Choi wrote:
> >> Hi Javier,
> >>
> >> On 07/13/2015 03:58 PM, Javier Martinez Canillas wrote:
> >>> The exynos-ppmu driver is only a clock consumer and not a
On Fri, 2015-07-31 at 09:29 -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 31, 2015 at 05:01:01PM +1000, Michael Ellerman wrote:
> > It's obviously possible that some samples build with that configuration, but
> > building against another arch'es kernel headers just seems like it's asking
> > for
On 03.08.2015 09:01, Krzysztof Kozlowski wrote:
> During unbinding the driver was dereferencing a pointer to memory
> already freed by power_supply_unregister().
>
> Driver was freeing its internal description of battery through pointers
> stored in power_supply structure. However, because the
Ezequiel Garcia writes:
> Just tested linux-next (hence *without* the patchset) and I see
> the same "Wait time out". In other words, pxa3xx-nand is broken
> on PXA :/
>
> Interestingly, the culprit doesn't seem to be in pxa3xx-nand itself.
> Reverting the recent commits on pxa3xx-nand doesn't
Hi
On Fri, 31 Jul 2015, Viresh Kumar wrote:
> IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> is no need to do that again from its callers. Drop it.
>
> gemini driver was using likely() for a failure case while the rtc driver
> is getting registered. That looks wrong
On Mon, Aug 3, 2015 at 12:22 PM, Julian Calaby wrote:
> Hi Chen-Yu,
>
> On Mon, Aug 3, 2015 at 12:37 PM, Chen-Yu Tsai wrote:
>> Hi,
>>
>> On Mon, Aug 3, 2015 at 7:35 AM, Julian Calaby
>> wrote:
>>> Hi Timo,
>>>
>>> On Mon, Aug 3, 2015 at 5:23 AM, Timo Sigurdsson
>>> wrote:
sun7i-a20.dtsi
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.
There are 164 patches in this series, which will be posted as responses
to this
Hi Chen-Yu,
On Mon, Aug 3, 2015 at 12:37 PM, Chen-Yu Tsai wrote:
> Hi,
>
> On Mon, Aug 3, 2015 at 7:35 AM, Julian Calaby wrote:
>> Hi Timo,
>>
>> On Mon, Aug 3, 2015 at 5:23 AM, Timo Sigurdsson
>> wrote:
>>> sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
>>> boards
On Tue, Jul 21, 2015 at 12:25:30PM -0400, Jarod Wilson wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=99841
>
> Seems like a read of all 1's from a register of a device that has gone
> away should be taken as a sign that the device has gone away.
> Section 6.2.10 of the PCIE spec (v4.0, rev
On 08/02/2015 07:05 PM, Xishi Qiu wrote:
>> > Also, this might not do very much good in practice. If you are
>> > splitting a high-order page, you are doing the split because the
>> > lower-order lists are empty. So won't that list_add() be to an empty
>
> I made a mistake, you are right, all
This makes no sense and causes warnings on boot.
Signed-off-by: Sasha Levin
---
fs/orangefs/pvfs2-mod.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/orangefs/pvfs2-mod.c b/fs/orangefs/pvfs2-mod.c
index 69289c5..d80537d 100644
--- a/fs/orangefs/pvfs2-mod.c
+++
Hi, Shawn.
On 07/28/2015 12:06 PM, Shawn Lin wrote:
> This patch fixes the following issues reported by checkpatch.pl:
> - use -EINVAL instead of -ENOSYS, to fix warning message:
> "ENOSYS means 'invalid syscall nr' and nothing else"
> - split lines whose length is greater than 80 characters
>
gpio can keep state even the clock disable, for save power
consumption, only enable gpio clock when it setting
Signed-off-by: Heiko Stuebner
Signed-off-by: huang lin
Signed-off-by: huang lin
---
drivers/pinctrl/pinctrl-rockchip.c | 60 ++
1 file changed,
pclk_pd_pmu needs to keep running and with the upcoming gpio clock
handling this is not always the case anymore. So add it to the list
of critical clocks for now.
Signed-off-by: Heiko Stuebner
Signed-off-by: huang lin
---
drivers/clk/rockchip/clk-rk3288.c | 1 +
1 file changed, 1 insertion(+)
HI, Laurent
On 7/31/2015 10:37 PM, Laurent Pinchart wrote:
Hi Josh,
Thank you for the patch.
On Wednesday 17 June 2015 18:39:39 Josh Wu wrote:
As in set_fmt() function we only need to know which format is been set,
we don't need to access the ISI hardware in this moment.
So move the
On 31-07-15, 09:37, Stephen Boyd wrote:
> For qcom platforms, the frequency is almost always constant.
> There may be some tables where we have a couple higher
> frequencies than others because the speed bin is different.
> Otherwise the voltage/current is changing based on the silicon
>
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index f0c0c53..6996308 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
When igb_init_interrupt_scheme in igb_sriov_reinit is failed, the lock
acquired by rtnl_lock() is not released, which causes a deadlock.
This patch adds rtnl_unlock() in error handling to fix it.
Signed-off-by: Jia-Ju Bai
---
drivers/net/ethernet/intel/igb/igb_main.c |1 +
1 file changed,
Signed-off-by: Liu.Zhao
---
drivers/usb/serial/option.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
index f0c0c53..6996308 100644
--- a/drivers/usb/serial/option.c
+++ b/drivers/usb/serial/option.c
DesignWare MMC Controller can support two types of DMA
mode: external dma and internal dma. We get a RK312x platform
integrated dw_mmc and ARM pl330 dma controller. This patch add
edmac ops to suuport these platforms. I've tested it on RK312x
platform with edmac mode and RK3288 platform with idmac
When remove module g_serial on quark platform, the following Warning on:
Modules linked in: usb_f_acm u_serial g_serial(-) pch_udc libcomposite configfs
udc_core
ad7298 industrialio_triggered_buffer kfifo_buf tpm_i2c_infineon indus
CPU: 0 PID: 369 Comm: modprobe Not tainted
When vortex_up is failed, the skb buffers allocated by __netdev_alloc_skb
in vortex_open are not released, which may cause resource leaks.
This bug has been submitted before.
This patch modifies the error handling code to fix it.
Signed-off-by: Jia-Ju Bai
---
drivers/net/ethernet/3com/3c59x.c |
On 2015/08/02 19:02, Thomas Gleixner wrote:
> On Wed, 29 Jul 2015, Takao Indoh wrote:
>> +/*
>> + * Table of Physical Addresses bits
>> + */
>> +enum topa_sz {
>> +TOPA_4K = 0,
>> +TOPA_8K,
>> +TOPA_16K,
>> +TOPA_32K,
>> +TOPA_64K,
>> +TOPA_128K,
>> +TOPA_256K,
>> +
On 01-08-15, 17:04, Viresh Kumar wrote:
> On 31-07-15, 08:30, Radivoje Jovanovic wrote:
> > I agree with you that this patch is trivial for the current
> > implementation since the notifier, as it is currently, will enforce
> > cpu_cooling policy change at every CPUFREQ_ADJUST which would cause
>
Hi,
I happened to build a kernel with "make deb-pkg" on a machine with no
network connectivity, but this failed with:
[...]
INSTALL debian/headertmp/usr/include/asm/ (65 files)
hostname: Name or service not known
../scripts/package/Makefile:90: recipe for target 'deb-pkg' failed
make[2]: ***
Its all about caching min/max freq requested by userspace, and
the name 'cpufreq_real_policy' doesn't fit that well. Rename it to
cpufreq_user_policy.
Signed-off-by: Viresh Kumar
---
include/linux/cpufreq.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Its always same as policy->governor, and there is no need to keep
another copy of it. Remove it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 7 ++-
include/linux/cpufreq.h | 1 -
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c
Its always same as policy->policy, and there is no need to keep another
copy of it. Remove it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 10 +-
include/linux/cpufreq.h | 1 -
2 files changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c
Driver is guaranteed to be present on a call to cpufreq_parse_governor()
and there is no need to check for !cpufreq_driver. Drop it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c
cpufreq_get_policy() is useful if the pointer to policy isn't available
in advance. But if it is available, then there is no need to call
cpufreq_get_policy(). Directly use memcpy() to copy the policy.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 8 ++--
1 file changed, 2
'user_policy' caches properties of a policy that are set by userspace.
And these must be updated only if cpufreq core was successful in
updating them based on request from user space.
In store_scaling_governor(), we are updating user_policy.policy and
user_policy.governor even if
What's being done from CPUFREQ_INCOMPATIBLE, can also be done with
CPUFREQ_ADJUST. There is nothing special with CPUFREQ_INCOMPATIBLE
notifier.
Kill CPUFREQ_INCOMPATIBLE and fix its usage sites.
This also updates the numbering of notifier events to remove holes.
Signed-off-by: Viresh Kumar
---
On Sun, Aug 2, 2015 at 3:08 AM, Pali Rohár wrote:
> On Sunday 02 August 2015 03:45:32 Robert Hancock wrote:
>> On Sat, Aug 1, 2015 at 2:09 PM, Pali Rohár
>> wrote:
>> > On Thursday 25 December 2014 07:22:13 Robert Hancock wrote:
>> >> On Tue, Dec 23, 2014 at 1:51 PM, Pali Rohár
>> >>
>> >>
Hello Rui,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes
to receive Thermal-SoC Management updates for v4.2-rc6 with top-most
3c19d237dd8148926e49259e495ee411f09c:
thermal: exynos: Remove unused code related to platform_data on probe()
The following changes since commit d61be4b3f2684b6d76ef8c1d28ecdeb9bb20fa8f:
Merge tag 'arm64-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2015-07-28 11:26:13
-0700)
are available in the git repository at:
Thomas Gleixner writes:
> No point in assigning the interrupt vectors if there is no interrupt
> chip installed. Move it to lguest_setup_irq().
>
> Signed-off-by: Thomas Gleixner
> Cc: Rusty Russell
> ---
> arch/x86/lguest/boot.c | 13 -
> 1 file changed, 8 insertions(+), 5
On 20 July 2015 at 16:49, Robert Jarzmik wrote:
> Ezequiel Garcia writes:
>
>> Here you go:
>>
>> http://git.infradead.org/users/ezequielg/linux/shortlog/refs/heads/pxa3xx-nand-timing-rework-v2
>
> Okay, I've tested this on cm-x300. The result is not bright :
> nand: device found,
Paolo Bonzini wrote on 2015-07-31:
>
>
> On 31/07/2015 04:49, Steve Rutherford wrote:
>> Oh... Yeah. That's a damn good point, given that the interrupt can be
>> injected from another thread while one is in that guest vcpu.
>>
>> Easiest time to update the TMR should be on guest entry through
yalin wang writes:
>> On Aug 1, 2015, at 21:32, Neil Horman wrote:
>>> strange, this is my test result:
>>>
>>> size built-in.o*
>>> text data bss dec hex filename
>>> 743937 50786 56008 850731 cfb2b built-in.o // with the patch
>>> 744069 50786 56008 850863 cfbaf
When pci_dma_mapping_error in e100_xmit_prepare is failed, the skb buffer
allocated by netdev_alloc_skb_ip_align in e100_rx_alloc_skb is not
released, which causes a possible resource leak.
This patch adds error handling code to fix it.
Signed-off-by: Jia-Ju Bai
---
When compile iio related driver the following warning shown:
include/linux/iio/trigger.h:35:34: warning: 'struct iio_trigger'
declared inside parameter list
int (*set_trigger_state)(struct iio_trigger *trig, bool state);
include/linux/iio/trigger.h:38:18: warning: 'struct iio_dev'
declared
On 2015/8/1 4:31, Arnaldo Carvalho de Melo wrote:
Em Fri, Jul 31, 2015 at 12:35:22PM -0300, Arnaldo Carvalho de Melo escreveu:
But point here is, when I see "enable passing
bpf object file to --event" I apply the patch and expect to be able to
go straight away and do:
perf record -e
Hi,
On Mon, Aug 3, 2015 at 7:35 AM, Julian Calaby wrote:
> Hi Timo,
>
> On Mon, Aug 3, 2015 at 5:23 AM, Timo Sigurdsson
> wrote:
>> sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
>> boards
>> (or all?), however, do not allow the voltage to go below 1.0V. Thus, raise
Paolo Bonzini wrote on 2015-07-31:
>
>
> On 31/07/2015 01:26, Zhang, Yang Z wrote:
Do not compute TMR in advance. Instead, set the TMR just before
the interrupt is accepted into the IRR. This limits the coupling
between IOAPIC and LAPIC.
>>
>> Uh.., it back to original way
On Mon, Jul 06, 2015 at 05:26:57PM +0200, Lukasz Majewski wrote:
> Dear Eduardo,
>
> Please find my pull request for Samsung Thermal fixes (v4.2-rc1):
>
> The following changes since commit
> efa86858e1d8970411a140fa1e0c4dd18a8f2a89:
>
> thermal: armada: Update Armada 380 thermal sensor
> On Aug 1, 2015, at 21:32, Neil Horman wrote:
>
> On Sat, Aug 01, 2015 at 03:12:42PM +0800, yalin wang wrote:
>>
>>> 在 2015年7月31日，22:14，Thomas Gleixner 写道：
>>>
>>>
>>> On Fri, 31 Jul 2015, Thomas Gleixner wrote:
>>>
On Fri, 31 Jul 2015, yalin wang wrote:
> it is optimised to 2
The driver lacks the check of nic->cbs_pool after pci_pool_create
in e100_probe. When this function is failed, a null pointer dereference
occurs when pci_pool_alloc uses nic->cbs_pool in e100_alloc_cbs.
This patch adds a check and related error handling code to fix it.
Signed-off-by: Jia-Ju Bai
On 07/31/2015 08:05 PM, Matt Fleming wrote:
On Fri, 31 Jul, at 09:22:33AM, fupan wrote:
Hi, Matt
Will you take care of this patch or I send a V2?
Could you please send a V2 with the changes to the commit message that I
suggested previously? Thanks!
NP!
Thanks!
Fupan
--
To unsubscribe
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/drm_atomic_helper.c
between commit:
27667f4744fc ("i915: temporary fix for DP MST docking station NULL pointer
dereference")
from Linus' tree and commit:
fc596660dd4e ("drm/atomic: add
We're getting up there to the later rc's, but it's looking like 4.2
might be one of the releases needing more than the usual seven rc
releases - things aren't calming down like I would wish, and we've
still had some fairly annoying issues pop up.
For example, there was a core VFS fix merged just
On 2015/8/1 7:24, Dave Hansen wrote:
> On 07/31/2015 02:30 AM, Xishi Qiu wrote:
>> __free_one_page() will judge whether the the next-highest order is free,
>> then add the block to the tail or not. So when we split large order block,
>> add the small block to the tail, it will reduce fragment.
>
From: fli
Commit 35d5134b7d5a
("x86/efi: Correct EFI boot stub use of code32_start")
imported a bug, which will cause 32bit kernel boot failed
using efi method. It should use the label's address instead
of the value stored in the label to caculate the address of
code32_start.
Signed-off-by:
If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX,
an EDSA frame is prepended with a 802.1q header once queued.
To fix this, push the VLAN tag to the payload if present, before
checking the frame protocol.
[note: we may prefer to access directly VLAN TCI from hwaccel frames,
but
On Sun, 2015-08-02 at 17:11 +0200, Andrey Konovalov wrote:
> Replace ACCESS_ONCE() macro in smp_store_release() and smp_load_acquire()
> with WRITE_ONCE() and READ_ONCE() on x86, arm, arm64, ia64, metag, mips,
> powerpc, s390, sparc and asm-generic since ACCESS_ONCE does not work
> reliably on
On 07/31/2015 08:21 PM, Luis Henriques wrote:
On Fri, Jul 31, 2015 at 01:05:19PM +0100, Matt Fleming wrote:
On Fri, 31 Jul, at 09:22:33AM, fupan wrote:
Hi, Matt
Will you take care of this patch or I send a V2?
Could you please send a V2 with the changes to the commit message that I
On Sun, 2015-08-02 at 17:11 +0200, Andrey Konovalov wrote:
> Replace ACCESS_ONCE() macro in smp_store_release() and smp_load_acquire()
> with WRITE_ONCE() and READ_ONCE() on x86, arm, arm64, ia64, metag, mips,
> powerpc, s390, sparc and asm-generic since ACCESS_ONCE does not work
> reliably on
When e1000e_setup_rx_resources is failed in e1000_open,
e1000e_free_tx_resources in "err_setup_rx" segment is executed.
"writel(0, tx_ring->head)" statement in e1000_clean_tx_ring
in e1000e_free_tx_resources will cause a null dereference(crash),
because "tx_ring->head" is only assigned in
On Wed, 2015-15-07 at 03:01:48 UTC, Sukadev Bhattiprolu wrote:
> Fix parameter alignment to be consistent with coding style.
>
> Signed-off-by: Sukadev Bhattiprolu
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/40386217cd7bc38908d6
cheers
--
To unsubscribe from this list:
On Wed, 2015-15-07 at 03:01:49 UTC, Sukadev Bhattiprolu wrote:
> Simplify code that extracts a 24x7 counter from the HCALL's result buffer.
>
> Suggested-by: Joe Perches
> Signed-off-by: Sukadev Bhattiprolu
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/465345ca387ed491c467
Fix minor typo so that can pass correct pointer variable for
container_of().
Signed-off-by: Leo Yan
---
Documentation/mailbox.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/mailbox.txt b/Documentation/mailbox.txt
index 1092ad9..f3f0ac2 100644
---
Document the new compatible for stub clock driver which is used for CPU
and DDR's dynamic frequency scaling.
Signed-off-by: Leo Yan
---
.../devicetree/bindings/clock/hi6220-clock.txt| 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git
On Hi6220, there have some clocks which can use mailbox channel to send
messages to power controller to change frequency; this includes CPU, GPU
and DDR clocks.
For dynamic frequency scaling, firstly need write the frequency value to
SRAM region, and then send message to mailbox to trigger power
Enable SRAM node and stub clock node for Hi6220; furthermore
add the CPU's clock so it will be used by cpufreq-dt driver.
Signed-off-by: Leo Yan
---
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 23 +++
1 file changed, 23 insertions(+)
diff --git
*of_iomap()* will check the device node pointer, and if the pointer is
NULL it will return error code. So refine clock's init flow by checking
the device node with this simple way; and polish a little for the print
out message.
Signed-off-by: Leo Yan
---
drivers/clk/hisilicon/clk.c | 11
Document "hisilicon,hi6220-sramctrl" for SRAM controller.
Signed-off-by: Leo Yan
---
.../devicetree/bindings/arm/hisilicon/hisilicon.txt| 18 ++
1 file changed, 18 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt
This series adds support for hisilicon stub clock driver. On hi6220,
the bootloader needs load the firmware image and set info for OPPs;
after run into kernel, the stub clock driver is used to communicate
w/t firmware for cpu dynamic frequency scaling.
In patch series v1/v2, the stub clock driver
Add Hisilicon mailbox's common driver, it registers mailbox channels
into framework; it also invokes low level callback functions for
register's related operations. Enhance rx channel's message queue,
which is based on the code in drivers/mailbox/omap-mailbox.c.
Enable Hi6220 mailbox driver as
On Hi6220, below memory regions in DDR have specific purpose:
- 0x05e0, - 0x05ef,: For MCU firmware using at runtime;
- 0x0740,f000 - 0x0740,: For MCU firmware's section;
- 0x06df,f000 - 0x06df,: For mailbox message data.
This patch reserves these memory regions and add device
Document the new compatible for Hisilicon mailbox driver.
Signed-off-by: Leo Yan
---
.../devicetree/bindings/mailbox/hisi-mailbox.txt | 57 ++
1 file changed, 57 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mailbox/hisi-mailbox.txt
diff --git
This patch series is to implement Hisilicon's mailbox driver and enable
the mailbox controller on Hi6220.
The Hisilicon mailbox supports up to 32 channels. Each channel is
unidirectional with a maximum message size of 8 words. I/O is performed
using register access (there is no DMA) and the cell
On 31/07/15 19:11, Bryan O'Donoghue wrote:
On 31/07/15 17:43, Bryan O'Donoghue wrote:
On 31/07/15 17:36, Ilia Mirkin wrote:
Do you have a reproducible way of achieving the multiple buffer on
validation list thing?
Ilia, Peter.
I've filed a bug for you here :
On 31.07.2015 17:58, Robert Baldyga wrote:
> Hello,
>
> This patch set fixes bug causing serial hang in DMA mode for FIFO sizes
> smaller than cache alignment. The first patch fixes DMA mode entering
> condition to avoid starting with buffer smaller than cache line size.
> Second patch fixes the
Hi Linus,
Please pull some more powerpc fixes for 4.2:
The following changes since commit c5dfd654d0ec0a28fe81e7bd4d4fd984a9855e09:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2015-07-22
14:45:25 -0700)
are available in the git repository at:
During unbinding the driver was dereferencing a pointer to memory
already freed by power_supply_unregister().
Driver was freeing its internal description of battery through pointers
stored in power_supply structure. However, because the core owns the
power supply instance, after calling
Hi Timo,
On Mon, Aug 3, 2015 at 5:23 AM, Timo Sigurdsson
wrote:
> sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
> boards
> (or all?), however, do not allow the voltage to go below 1.0V. Thus, raise the
> voltage for the lowest operating point to 1.0V so all boards
I see these in dmesg, but I don't think I've seen any actual issues in
using the laptop itself. Should I be worried?
lspci:
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
Integrated Graphics Controller (rev 0b) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem:
From: Colin Ian King
Trivial change, fix spelling mistake 'invaild' -> 'invalid' in
dev_err message.
Signed-off-by: Colin Ian King
---
drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
1 - 100 of 554 matches
Mail list logo
