From: Yash Omer
---
drivers/staging/dgnc/dgnc_neo.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c
index 1943e66..0034ebe 100644
--- a/drivers/staging/dgnc/dgnc_neo.c
+++ b/drivers/staging/dgnc/dgnc
On 06/07/2017 at 07:54:58 +0200, Heiner Kallweit wrote:
> Am 06.07.2017 um 06:24 schrieb Stephen Rothwell:
> > Hi Alexandre,
> >
> > After merging the rtc tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced this warning:
> >
> > drivers/rtc/rtc-ds1307.c: In function 'ds1307_get_
On Thu 06-07-17 07:16:49, Wei Yang wrote:
> On Fri, Jun 30, 2017 at 01:01:18PM +0200, Michal Hocko wrote:
> >On Fri 30-06-17 11:55:45, Michal Hocko wrote:
> >> On Fri 30-06-17 17:39:56, Wei Yang wrote:
> >> > On Fri, Jun 30, 2017 at 4:39 PM, Michal Hocko wrote:
> >> [...]
> >> > > yes and to be ho
On 07/03, Kiran Gunda wrote:
> From: Fenglin Wu
>
> The opc parameter in pmic_arb_write_cmd() function is defined with type
> u8 and it's always greater than or equal to 0. Checking that it's not
> less than 0 is redundant and it can cause a forbidden warning during
> compilation. Remove the chec
On 07/03, Kiran Gunda wrote:
> From: Fenglin Wu
>
> The opc parameter in pmic_arb_write_cmd() function is defined with type
> u8 and it's always greater than or equal to 0. Checking that it's not
> less than 0 is redundant and it can cause a forbidden warning during
> compilation. Remove the chec
On Wed, 5 Jul 2017, Tony Luck wrote:
> > In case that a RMID was never used on a particular package, the state check
> > forces an IPI on all packages unconditionally. That's suboptimal at least.
> >
> > We know on which package a given RMID was used, so we could restrict the
> > checks to exactly
On 07/03, Kiran Gunda wrote:
> Modify the pmic_arb version ops to return an __iomem pointer
> to the address instead of an offset. That way we do not need to
> care about the base address changes in the new HW version.
>
> Signed-off-by: Kiran Gunda
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm
On 07/03, Kiran Gunda wrote:
> If "core" memory resource is not specified, then the driver could
> end up dereferencing a null pointer. Fix this issue.
>
> Signed-off-by: Kiran Gunda
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux
On Wed 05-07-17 16:00:55, Andrew Morton wrote:
> On Tue, 4 Jul 2017 09:58:03 +0200 Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > early_pfn_to_nid will return node 0 if both HAVE_ARCH_EARLY_PFN_TO_NID
> > and HAVE_MEMBLOCK_NODE_MAP are disabled. It seems we are safe now
> > because all a
On Tue, May 30, 2017 at 09:32:06PM +0200, Alexandre Belloni wrote:
> Switch to atomic PWM. The main goal is to properly wait for a period before
> disabling a channel to ensure the correct level is set on the output.
>
> Changes in v2:
> - fixed remaining checkpatch warnings
> - split the series
On 07/03, Kiran Gunda wrote:
> This patch cleans up the following.
>
> - Rename the "pa" to "pmic_arb".
> - Rename the spmi_pmic_arb *dev to spmi_pmic_arb *pmic_arb.
> - Rename the pa_{read,write}_data() functions to
> pmic_arb_{read,write}_data().
> - Rename channel to APID.
> - Rename the HWIR
Hi David,
[auto build test ERROR on rockchip/for-next]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Frank-Wang/ARM-dts-rockchip-add-regulator-nodes-for-rk3229-evb/20170
On 07/03, Kiran Gunda wrote:
> The access mode checks for peripheral ownership for read/write
> permissions should not be required. Every peripheral enabled for
> this master is expected to have a read/write permissions. If there
> is any such invalid access due to wrong configuration in boot loade
On 07/03, Kiran Gunda wrote:
> diff --git a/drivers/spmi/spmi-pmic-arb.c b/drivers/spmi/spmi-pmic-arb.c
> index 5285245..2d2e39c 100644
> --- a/drivers/spmi/spmi-pmic-arb.c
> +++ b/drivers/spmi/spmi-pmic-arb.c
> @@ -621,6 +621,19 @@ static int qpnpint_irq_set_type(struct irq_data *d,
> unsigned in
On Wed 05-07-17 14:18:49, Andrew Morton wrote:
> On Wed, 5 Jul 2017 20:28:49 +0200 Michal Hocko wrote:
>
> > "mm: enlarge stack guard gap" has introduced a regression in some rust
> > and Java environments which are trying to implement their own stack
> > guard page. They are punching a new MAP_
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.13-rc1-tag
xen: features and fixes for 4.13-rc1
Other than fixes and cleanups it contains:
- Support > 32 VCPUs at domain restore
- Support for new sysfs nodes related to Xen
- Some
On Thu, Jul 6, 2017 at 1:13 PM, Jaehoon Chung wrote:
> Hi,
>
> To Guodong, if you can forward this to Li Wei, plz do it. Sorry.
>
Sure. Put Li Wei in cc.
And add my response.
> On 07/03/2017 10:06 AM, liwei wrote:
>>
>> Add sd card support for hi3660 soc
>
> Need the patch for adding "hi3660-dw-
On 07/03, Kiran Gunda wrote:
> Returning the output value from a function, when it is possible, is the
> better and cleaner way than passing it by the pointer. Hence, modify
> the ppid_to_apid mapping function to return apid instead of passing
> it by a pointer. While at it, pass the ppid as functi
On Mon, May 22, 2017 at 12:02:10AM +0200, Wolfram Sang wrote:
> include/linux/i2c is not for client devices. Move the header file to a
> more appropriate location.
>
> Signed-off-by: Wolfram Sang
> ---
> arch/arm/mach-omap2/common.h| 2 +-
> arch/arm/mach-omap2/omap_twl.c |
On 07/03, Kiran Gunda wrote:
> Replace the writel_relaxed with __raw_writel to avoid byte swapping
> in pmic_arb_write_data() function. That way the code is independent
> of the CPU endianness.
>
> Signed-off-by: Kiran Gunda
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc.
On Thu, 2017-07-06 at 14:16 +0800, Zhi Mao wrote:
> On Wed, 2017-07-05 at 13:09 +0200, Matthias Brugger wrote:
> >
> > On 06/30/2017 08:05 AM, Zhi Mao wrote:
> > > In original code, the pwm output frequency is not correct
> > > when set bit<3>=1 to PWMCON register.
> > >
> > > Signed-off-by: Zhi
On Tue, Jun 20, 2017 at 01:22:15PM +0530, Arvind Yadav wrote:
> of_device_ids are not supposed to change at runtime. All functions
> working with of_device_ids provided by work with const
> of_device_ids. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/vi
On Tue, Jun 13, 2017 at 03:26:41PM +0530, Arvind Yadav wrote:
> File size before:
>text data bss dec hex filename
>1510 296 01806 70e drivers/pwm/pwm-hibvt.o
> File size After adding 'const':
>text data bss dec hex filena
On Tue, May 30, 2017 at 11:50:41PM +0200, Alexandre Belloni wrote:
> Hi,
>
> This series reworks the Atmel Timer counter Block drivers. Those blocks
> each have 3 counters with 2 channels each and can be used for
> multiple functions:
> - timers
> - PWMs
> - Quadrature decoders
> - Stepper mot
On Wed, 5 Jul 2017, Andrew Morton wrote:
> On Tue, 04 Jul 2017 11:32:32 +0200 Thomas Gleixner wrote:
>
> > Andrey reported a potential deadlock with the memory hotplug lock and the
> > cpu hotplug lock.
> >
> > The following series addresses this by reworking the memory hotplug locking
> > and f
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
* The fixup for the blk-mq clash with the scm driver
* An improvement for the driver in regard to raw I/O
* Bug fixes and clean
On Tue, May 23, 2017 at 06:05:03PM +0200, Jerome Brunet wrote:
> In of_pwm_chip, if we fail to get the pwm chip due to probe defer, we
> shouldn't print an error message. Just be silent in this case.
>
> Signed-off-by: Jerome Brunet
> ---
> drivers/pwm/core.c | 4 +++-
> 1 file changed, 3 insert
On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla wrote:
>
> I have posted the SCMI patches now[1],
>
I wish I was CC'ed on that. Now LKML seems too busy to forward it.
> please let me know how to get
> both SCPI and SCMI working together with different doorbell bits on the
> same channel.
>
You say
* Sebastian Reichel [170705 01:29]:
> Hi,
>
> On Wed, Jul 05, 2017 at 01:06:54AM -0700, Tony Lindgren wrote:
> > > > Not sure if this really is a regression as we've always had a bogus
> > > > wl1271-nvs.bin in linux-firmware.git. Sure would be nice to fix it,
> > > > but going back to using a ge
On Sat, Jun 17, 2017 at 12:26:44PM -0300, Mauro Carvalho Chehab wrote:
> Each text file under Documentation follows a different
> format. Some doesn't even have titles!
>
> Change its representation to follow the adopted standard,
> using ReST markups for it to be parseable by Sphinx:
>
> - mark
Hi Ethan,
On 2017/7/6 13:46, Ethan Zhao wrote:
> Hanjun，
>
> What branch is this patch for ? Check v4.12, failed to apply.
I prepared patches based on master branch of linux-next git tree,
but they can be applied cleanly on top of latest Linus tree.
This patch set is for latest merged 4.13 m
On 2017-07-06 07:55, Daniel Vetter wrote:
> On Wed, Jul 5, 2017 at 7:50 PM, Peter Rosin wrote:
+retry:
+ret = drm_modeset_lock_all_ctx(dev, &ctx);
>>>
>>> With atomic you don't need to grab locks, this is done behind the scenes
>>> (as long as you handle the retry/backoff correctly).
On Wed, 2017-07-05 at 13:09 +0200, Matthias Brugger wrote:
>
> On 06/30/2017 08:05 AM, Zhi Mao wrote:
> > In original code, the pwm output frequency is not correct
> > when set bit<3>=1 to PWMCON register.
> >
> > Signed-off-by: Zhi Mao
> > ---
> > drivers/pwm/pwm-mediatek.c |2 +-
> > 1
Hi Masahiro,
[auto build test ERROR on next-20170705]
[cannot apply to gpio/for-next tegra/for-next xlnx/master v4.12 v4.12-rc7
v4.12-rc6 v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
Hi Masahiro,
[auto build test ERROR on next-20170705]
[cannot apply to gpio/for-next tegra/for-next xlnx/master v4.12 v4.12-rc7
v4.12-rc6 v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
Hi all,
Please do not add any v4.14 material to you linux-next included branches
until after v4.13-rc1 has been released.
Changes since 20170705:
Non-merge commits (relative to Linus' tree): 5487
4539 files changed, 548263 insertions(+), 90579 dele
On 06/10/2017 04:06 AM, David Rientjes wrote:
> A few hugetlb allocators loop while calling the page allocator and can
> potentially prevent rescheduling if the page allocator slowpath is not
> utilized.
>
> Conditionally schedule when large numbers of hugepages can be allocated.
>
> Signed-off-b
On Wed, 5 Jul 2017 12:29:17 -0400
Steven Rostedt wrote:
> On Wed, 5 Jul 2017 12:25:06 -0400
> Steven Rostedt wrote:
>
>
> > > @@ -255,12 +262,18 @@ __run_test() { # testfile
> > > # Run one test case
> > > run_test() { # testfile
> > >local testname=`basename $1`
> > > - local testlog=
On 05-07-17, 14:41, Patrick Bellasi wrote:
> On 05-Jul 11:31, Viresh Kumar wrote:
> Just had a fast check but I think something like that can work.
> We had an internal discussion with Brendan (in CC now) which had a
> similar proposal.
>
> Main counter arguments for me was:
> 1. we wanna to redu
On Wed, Jul 5, 2017 at 7:50 PM, Peter Rosin wrote:
>>> +retry:
>>> +ret = drm_modeset_lock_all_ctx(dev, &ctx);
>>
>> With atomic you don't need to grab locks, this is done behind the scenes
>> (as long as you handle the retry/backoff correctly). See the kerneldoc for
>> the various drm_atomic_
Am 06.07.2017 um 06:24 schrieb Stephen Rothwell:
> Hi Alexandre,
>
> After merging the rtc tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/rtc/rtc-ds1307.c: In function 'ds1307_get_time':
> drivers/rtc/rtc-ds1307.c:342:26: warning: unused variable 'ch
On Wed, Jun 14, 2017 at 05:13:16PM +0200, Fabrice Gasnier wrote:
> Clock name has been updated during driver/DT binding review:
> https://lkml.org/lkml/2016/12/13/718
> Update DT binding doc to reflect this.
>
> Fixes: cd9a99c2f8e8 (dt-bindings: pwm: Add STM32 bindings)
> Signed-off-by: Fabrice Ga
On Wed, Jul 05, 2017 at 09:32:35PM -0700, Kees Cook wrote:
> In an attempt to provide sensible rlimit defaults for setuid execs, this
> inherits the namespace's init rlimits:
>
> $ ulimit -s
> 8192
> $ ulimit -s unlimited
> $ /bin/sh -c 'ulimit -s'
> unlimited
> $ sudo /bin/sh -c 'ulimit -s'
> 819
On 05-07-17, 14:04, Patrick Bellasi wrote:
> On 05-Jul 10:20, Viresh Kumar wrote:
> > And also why is it important to write 0 to sg_cpu->flags ? What wouldn't
> > work if
> > we set sg_cpu->flags to SCHED_CPUFREQ_IDLE in this case ? i.e. Just the
> > below
> > statement should be good for us.
>
Hanjun，
What branch is this patch for ? Check v4.12, failed to apply.
Thanks,
Ethan
On Thu, Jul 6, 2017 at 12:35 PM, Hanjun Guo wrote:
> From: Hanjun Guo
>
> is_fwnode_irqchip() already check fwnode is NULL or not,
> just use is_fwnode_irqchip() directly.
>
> Signed-off-by: Hanjun Guo
> -
On Wed, Jul 05, 2017 at 04:23:56PM +0200, Michal Hocko wrote:
> On Wed 05-07-17 13:19:40, Ben Hutchings wrote:
> > On Tue, 2017-07-04 at 16:31 -0700, Linus Torvalds wrote:
> > > On Tue, Jul 4, 2017 at 4:01 PM, Ben Hutchings
> > > wrote:
> > > >
> > > > We have:
> > > >
> > > > bottom = 0xff803ff
Hey folks,
I updated my HiKey kernel tree to linus/master today and it stopped
booting (hitting errors at init and reseting immediately into
bootloader mode):
[5.289827] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
[5.296709] init: Loading SELinux policy
[5.334521]
On Wed, Jul 5, 2017 at 4:14 PM, Jerry Hoemann wrote:
> On Wed, Jul 05, 2017 at 09:35:48AM -0700, Dan Williams wrote:
[..]
>> It was a mistake to use _DSM for common root-level functionality, and
>> we shouldn't double down on that mistake by allowing unfettered
>
> As to the moral aspects of ACPI'
On Wed, Jul 05, 2017 at 05:19:47PM -0700, Andy Lutomirski wrote:
> I think it's ridiculous that you can change rlimits and then
> exec a setuid thing. It's not so easy to fix, though. Maybe track,
> per-task, inherited by clone and exec, what the rlimits were the last
> time the process had privi
On (07/02/17 20:28), Seth Jennings wrote:
> On Sun, Jul 2, 2017 at 9:19 AM, Srividya Desireddy
> > Zswap is a cache which compresses the pages that are being swapped out
> > and stores them into a dynamically allocated RAM-based memory pool.
> > Experiments have shown that around 10-20% of pages st
Hi,
To Guodong, if you can forward this to Li Wei, plz do it. Sorry.
On 07/03/2017 10:06 AM, liwei wrote:
>
> Add sd card support for hi3660 soc
Need the patch for adding "hi3660-dw-mshc" compatible
Documentation/devicetree/bindings/k3-dw-mshc.txt
And added the minor comments.
>
> Major cha
On Tue, Jul 4, 2017 at 3:21 AM, Mark Rutland wrote:
> Should any of those be moved into the "should be dropped" pile?
Why not be conservative and clear every sample you're not sure about?
We'd appreciate a fix sooner rather than later here, since rr is
currently broken on every stable Linux kern
Hi Masahiro,
[auto build test ERROR on gpio/for-next]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Masahiro-Yamada/gpio-add-COMPILE_TEST-to-several-drivers/20170706-070
On Wed 05 Jul 16:51 PDT 2017, Fenglin Wu wrote:
> Hi Bjorn and Ivan,
>
> Could you help to take some time to look at these spmi-gpio pinctrl
> patches?
> Thanks.
Hi Fenglin,
Sorry for not getting to this earlier, I'll try to finalize my review of
this tomorrow.
Regards,
Bjorn
On Wed, Jul 5, 2017 at 9:55 PM, Stafford Horne wrote:
> On Wed, Jul 05, 2017 at 09:06:11PM -0700, John Stultz wrote:
>> On Wed, Jul 5, 2017 at 8:58 PM, Stafford Horne wrote:
>> > Hi tglx,
>> >
>> > Sorry, to bother you, I thought maybe this you missed this one? Let me
>> > know if you want a res
On Wed, Jul 5, 2017 at 9:32 PM, Kees Cook wrote:
> In an attempt to provide sensible rlimit defaults for setuid execs, this
> inherits the namespace's init rlimits:
>
> $ ulimit -s
> 8192
> $ ulimit -s unlimited
> $ /bin/sh -c 'ulimit -s'
> unlimited
> $ sudo /bin/sh -c 'ulimit -s'
> 8192
>
> This
On Wed, Jul 05, 2017 at 09:06:11PM -0700, John Stultz wrote:
> On Wed, Jul 5, 2017 at 8:58 PM, Stafford Horne wrote:
> > Hi tglx,
> >
> > Sorry, to bother you, I thought maybe this you missed this one? Let me
> > know if you want a resend.
>
> No. Sorry, I've already got this queued. Apologies f
Hi,
On Wednesday 05 July 2017 09:33 PM, Suzuki K Poulose wrote:
On 03/07/17 08:46, Arvind Yadav wrote:
attribute_groups are not supposed to change at runtime. All functions
working with attribute_groups provided by work with
const
attribute_group. So mark the non-const structs as const.
Si
On 05-07-17, 12:38, Patrick Bellasi wrote:
> On 05-Jul 10:30, Viresh Kumar wrote:
> > Yes we discussed this last time as well (I looked again at those
> > discussions and
> > am still confused a bit), but wanted to clarify one more time.
> >
> > After the 2nd patch of this series is applied, why
From: Hanjun Guo
is_fwnode_irqchip() already check fwnode is NULL or not,
just use is_fwnode_irqchip() directly.
Signed-off-by: Hanjun Guo
---
kernel/irq/irqdomain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index 1bc38f
From: Hanjun Guo
commit d59f6617eef0 (genirq: Allow fwnode to carry name information only)
forgot to do "domain->fwnode = fwnode;" for irqchips being probed via
ACPI namesapce (DSDT/SSDT), that will break platforms with irqchip such
as mbigen or qcom irq combiner, set the fwnode back to fix the i
In an attempt to provide sensible rlimit defaults for setuid execs, this
inherits the namespace's init rlimits:
$ ulimit -s
8192
$ ulimit -s unlimited
$ /bin/sh -c 'ulimit -s'
unlimited
$ sudo /bin/sh -c 'ulimit -s'
8192
This is modified from Brad Spengler/PaX Team's hard-coded setuid exec
stack
Hi Alexandre,
After merging the rtc tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/rtc/rtc-ds1307.c: In function 'ds1307_get_time':
drivers/rtc/rtc-ds1307.c:342:26: warning: unused variable 'chip'
[-Wunused-variable]
const struct chip_desc *chip = &chip
Export the cached pid / tgid mappings added by Joel Fernandes' patch [1]
in debugfs tracing saved_tgids file. This allows user apps to translate
the pids from a trace to their respective thread group.
Example saved_tgids file with pid / tgid values separated by ' ':
# cat saved_tgids
1048 104
On Wed, Jul 05, 2017 at 10:43:21AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 04, 2017 at 12:50:55PM -0700, Palmer Dabbelt wrote:
> > +/*
> > + * FIXME: I could only find documentation that atomic_{add,sub,inc,dec} are
> > + * barrier-free. I'm assuming that and/or/xor have the same constraints
>
On Wed, Jul 5, 2017 at 8:58 PM, Stafford Horne wrote:
> Hi tglx,
>
> Sorry, to bother you, I thought maybe this you missed this one? Let me
> know if you want a resend.
No. Sorry, I've already got this queued. Apologies for not sending notice.
thanks
-john
Hi Guenter and Yamada-san,
I am grateful for your support.
Thank you.
--
Best Regards,
Keiji Hayashibara
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Thursday, July 06, 2017 12:26 AM
> Subject: Re: [PATCH V4 0/3] add UniPhier watchdog support
>
> On 07/05/2017 03:26 AM, Ma
Hi tglx,
Sorry, to bother you, I thought maybe this you missed this one? Let me
know if you want a resend.
-Stafford
On Wed, Jun 28, 2017 at 10:39:21AM -0700, John Stultz wrote:
> On Wed, Jun 28, 2017 at 6:21 AM, Stafford Horne wrote:
> > When CONFIG_DEBUG_TIMEKEEPING is enabled the timekeepin
Hi Kees,
Problem is my ARM machine don't have clang and iproute2 which is
keeping me from testing the bpf tail calls.
You should do the following to test it,.
1. tools/testing/selftests/bpf/
2. make
3. sudo ./test_progs
And, before testing, you have to do "make headers_install".
These tests are
Hi Claudio,
[auto build test ERROR on tip/auto-latest]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Claudio-Scordino/sched-deadline-add-GRUB-bw-change-tracepoints/20170
On Wed, Jul 05, 2017 at 11:59:33PM +0200, Mason wrote:
> On 05/07/2017 23:34, Bjorn Helgaas wrote:
>
> > On Wed, Jul 05, 2017 at 10:39:19PM +0200, Mason wrote:
> >
> >> On 05/07/2017 20:03, Bjorn Helgaas wrote:
> > If you confirm that
> > https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pc
Dave Airlie writes:
> I think this needs a pad ^.
> And this.
Yup. Thanks!
>> +struct drm_mode_revoke_lease {
>> + /** Unique ID of lessee
>> +*/
>> + __u32 lessee_id;
>
> And this.
None of the other bare 32-bit ioctl structures are padded; I think
that's probably fine as
On Tue, Jul 04, 2017 at 12:50:55PM -0700, Palmer Dabbelt wrote:
[...]
> diff --git a/arch/riscv/include/asm/cmpxchg.h
> b/arch/riscv/include/asm/cmpxchg.h
> new file mode 100644
> index ..81025c056412
> --- /dev/null
> +++ b/arch/riscv/include/asm/cmpxchg.h
> @@ -0,0 +1,138 @@
> +/*
>
On Thu, Jul 06, 2017 at 08:18:02AM +0800, Liang Chen wrote:
> But as you pointed out, explicit casting is still bad too (was hoping it can
> be
> considered less bad at this situation). I will think of a better idea
> to handle this
> issue unless people agree that the current behaviour is safe.
PERST must be asserted around ~500ms before the reboot is applied.
During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs
LCPLL clock and PERST both goes off simultaneously.
This will cause certain Endpoints Intel NVMe not get detected, upon
next boot sequence.
This is specificall
For Configuration Requests only, following reset it is possible for a
device to terminate the request but indicate that it is temporarily unable
to process the Request, but will be able to process the Request in the
future – in this case, the Configuration Request Retry Status 100 (CRS)
Completion
PCI: iproc: Retry request when CRS returned from EP
Above patch adds support for CRS in PCI RC driver, otherwise if not
handled at lower level, the user space PMD (poll mode drivers) can
timeout.
PCI: iproc: add device shutdown for PCI RC
This fixes the issue where certian PCI endpoints are not ge
On Thu, Jul 06, 2017 at 12:53:13PM +1000, Oliver wrote:
> The main use case is provisioning install media for bare metal
> servers. Traditionally that's been handled by having the BMC emulate a
> USB CD drive. Unfortunately, most BMCs have limited CPU, limited
> memory and a wet-string network conn
Hi, Ming Lei
On 07/06, Ming Lei wrote:
>Hi Xiaolong,
>
>On Mon, Jul 3, 2017 at 10:57 AM, kernel test robot
> wrote:
>>
>> Greeting,
>>
>> FYI, we noticed a -10.0% regression of blogbench.read_score due to commit:
>
>Looks like related with mq scheduler, could you test the following patch to see
>i
On Thu, Jul 6, 2017 at 12:11 PM, h...@lst.de wrote:
> On Wed, Jul 05, 2017 at 07:08:54PM -0700, Dan Williams wrote:
>> [ adding Jeff, and Johannes ]
>>
>> On Wed, Jul 5, 2017 at 6:17 PM, Kani, Toshimitsu wrote:
>> > On Wed, 2017-07-05 at 17:07 -0700, Dan Williams wrote:
>> [..]
>> >> We have syml
On Wed, Jul 5, 2017 at 5:19 PM, Andy Lutomirski wrote:
> On Wed, Jul 5, 2017 at 4:50 PM, Kees Cook wrote:
>> As part of that should we put restrictions on the environment of
>> set*id exec too? Part of the risks demonstrated by Qualys was that
>> allowing a privilege-elevating binary to inherit r
On Thu, Jul 06, 2017 at 11:08:27AM +1000, NeilBrown wrote:
> On Wed, Jul 05 2017, J. Bruce Fields wrote:
>
> > On Wed, Jul 05, 2017 at 12:19:33PM -0700, Darrick J. Wong wrote:
> >> So, what's the probability that there are clients out there that started
> >> talking to a 2.2-based knfsd and will n
Hi Steven,
Thanks a lot for detailed review. Every suggestion were token except one need
extra review: the 'Waking up in loop'. Is this OK or need more further change?
BTW, I didn't add you on Reviewers, since you are author already. :)
Best regards
Alex
On 07/04/2017 02:49 AM, Steven Rostedt
ea_inode feature allows creating extended attributes that are up to
64k in size. Update __ext4_new_inode() to pick increased credit limits.
To avoid overallocating too many journal credits, update
__ext4_xattr_set_credits() to make a distinction between xattr create
vs update. This helps __ext4_ne
Extended attribute inodes are internal to ext4. Adding encryption/security
related attributes on them would mean dealing with nested calls into ea code.
Since they have no direct exposure to user mode, just avoid creating ea
entries for them.
Signed-off-by: Tahsin Erdogan
---
fs/ext4/ialloc.c |
IRTE[GALogIntr] bit should set when enabling guest_mode, which enables
IOMMU to generate entry in GALog when IRTE[IsRun] is not set, and send
an interrupt to notify IOMMU driver.
Signed-off-by: Suravee Suthikulpanit
Cc: Joerg Roedel
Fixes: d98de49a53e48 ('iommu/amd: Enable vAPIC interrupt remapp
On Thu, Jul 6, 2017 at 1:22 AM, Robin Murphy wrote:
> On 05/07/17 08:12, Tomasz Figa wrote:
>> There is nothing wrong in having a loadable module implementing DMA API,
>> for example to be used for sub-devices registered by the module. However,
>> most of the functions from dma-iommu do not have t
This patch allows atomic/volatile ioctls for sqlite under sdcardfs.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 15 ---
1 file changed, 15 deletions(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index f5d6357e8360..dd8f5d2caa48 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
On Wed, Jul 05, 2017 at 01:02:59PM -0700, Linus Torvalds wrote:
>
> That stupid CNN55XX driver was added with a default of "m"?
>
> WTF? Hell no. We don't add random new drivers and default them on -
> and we do so even less when they are for very unusual hardware.
Sorry, I'll make sure the defau
On Thu, Jul 6, 2017 at 1:49 AM, Code Kipper wrote:
> On 5 July 2017 at 18:20, Maxime Ripard
> wrote:
>> On Wed, Jul 05, 2017 at 05:43:24PM +0200, codekip...@gmail.com wrote:
>>> From: Marcus Cooper
>>>
>>> There are a lot of changes to the sun8i-h3 i2s block but not enough
>>> to warrant to a n
On Wed, Jul 05, 2017 at 07:08:54PM -0700, Dan Williams wrote:
> [ adding Jeff, and Johannes ]
>
> On Wed, Jul 5, 2017 at 6:17 PM, Kani, Toshimitsu wrote:
> > On Wed, 2017-07-05 at 17:07 -0700, Dan Williams wrote:
> [..]
> >> We have symlinks in /dev/disk/by* to make it easier to identify
> >> sto
The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)
are available in the git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.13
for you to fetch changes up to 1655cf8829d82d367d8fdb5cb58e
[ adding Jeff, and Johannes ]
On Wed, Jul 5, 2017 at 6:17 PM, Kani, Toshimitsu wrote:
> On Wed, 2017-07-05 at 17:07 -0700, Dan Williams wrote:
[..]
>> We have symlinks in /dev/disk/by* to make it easier to identify
>> storage devices, I think it makes sense to add udev rules for
>> identifying vo
I'm a bit concerned about these cmpxchg syscalls, and I'd like to
understand if my concerns are justified.
For a new instruction set that starts out in the 201x years we really
should have cmpxchg as a mandatory instruction - if not in the CPU
it should be in the Linux ABI so that we don't have to
From: Yunsheng Lin
As the user manual described, the second step to write to C45 phy
by mdio should be data, but not address. Here we should fix this
issue.
Fixes: 5b904d39406a ("net: add Hisilicon Network Subsystem MDIO support")
Signed-off-by: Yunsheng Lin
Reviewed-by: lipeng
---
drivers/ne
This patchset fix skb used after free and C45 op code issues
in hns driver.
Patch V2:
1. Remove ndev->feature checking in TX description patch.
2. Add Fixes: Tag in patch description.
Patch V1:
Initial Submit
Yunsheng Lin (2):
net: hns: Fix a wrong op phy C45 code
net
From: Yunsheng Lin
skb maybe freed in hns_nic_net_xmit_hw() and return NETDEV_TX_OK,
which cause hns_nic_net_xmit to use a freed skb.
BUG: KASAN: use-after-free in hns_nic_net_xmit_hw+0x62c/0x940...
[17659.112635] alloc_debug_processing+0x18c/0x1a0
[17659.117208] __slab
On Wed, Jul 05, 2017 at 04:45:49PM -0700, Linus Torvalds wrote:
> Ouch, yeah, that was annoying. And yes, I ended up with several
> whitespace differences but other than that it looks the same. Oh well.
>
> Jens, Christoph, let's not do that stupid thing with status-vs-error
> ever again, ok?
It
Teach buildid-cache how to add, remove, and update binary objects from
other mount namespaces. Allow probe events tracing binaries in
different namespaces to add their objects to the probe and build-id
caches too. As a handy side effect, this also lets us access SDT probes
in binaries from altern
Hi Andy and all,
Thanks for your patience.
> >
> > Main points (some I already told in an answer to Sakari's mail):
> > 1. Consider 2 GPIO chips over 1.
>
> I am looking into this.
>
For the second GPIO chip, the call to acpi_attach_data() fails with
AE_ALREADY_EXISTS, as below with 4.12 rc3
1 - 100 of 817 matches
Mail list logo
