Hi Lepton,
On Fri, 17 Feb 2017 15:37:33 -0800
Lepton Wu wrote:
Can you please add a commit message and prefix the subject with 'mtd: '.
Something like 'mtd: Fix mtdblock for >4GB MTD devices'.
> Signed-off-by: Lepton Wu
> ---
> drivers/mtd/mtdblock.c| 33 +
This patch corrects check generated by checkpatch.pl by
replacing comparison to null statements with equivalent
statements in the form of "!x".
Signed-off-by: simran singhal
---
drivers/staging/rtl8192e/rtl819x_BAProc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dr
On 17 February 2017 at 13:36, Eric Dumazet wrote:
> On Fri, 2017-02-17 at 12:36 +0800, Daniel J Blueman wrote:
>> When booting a VM in libvirt/KVM attached to a local bridge and KASAN
>> enabled on 4.9.10, we see a stream of KASAN warnings about off-slab
>> access [1].
>>
>> Let me know if you'd l
Ping !
>-Original Message-
>From: Anurag Kumar Vulisha [mailto:anurag.kumar.vuli...@xilinx.com]
>Sent: Friday, February 03, 2017 10:10 PM
>To: Laurent Pinchart ; Mauro Carvalho
>Chehab
>Cc: Punnaiah Choudary Kalluri ; Anirudha Sarangi
>; linux-me...@vger.kernel.org; linux-
>ker...@vger.ke
Hi Eddie,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.10-rc8 next-20170217]
[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/Eddie-Kovsky/provide-check-for
Hi Eddie,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc8 next-20170217]
[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/Eddie-Kovsky/provide-check-for-ro_after_init
Hi Andy,
On Fri, Feb 17, 2017 at 10:12:36PM -0800, Andy Lutomirski wrote:
On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote:
Greetings,
FYI here is an old bug, however is still active in mainline kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
[3.1
Hi Eddie,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.10-rc8 next-20170217]
[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/Eddie-Kovsky/provide-check-for
On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu wrote:
> Greetings,
>
> FYI here is an old bug, however is still active in mainline kernel.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> [3.185986] init[1] vsyscall attempted with vsyscall=none
> ip:ff
Use the new RO check functions introduced in this series to make the
vmbus register functions verify that the address of their arguments are
read-only. Addresses that fail the verification are rejected.
Signed-off-by: Eddie Kovsky
---
drivers/hv/vmbus_drv.c | 10 ++
1 file changed, 10 in
Provide a mechansim for other functions to verify that their arguments
are read-only. Use this mechansim in the vmbus register functions to
reject arguments that fail this test.
This implements a suggestion made by Kees Cook for the Kernel Self
Protection Project:
* provide mechanism to check
Implement a mechanism to check if a module's address is in
the rodata or ro_after_init sections. It mimics the exsiting functions
that test if an address is inside a module's text section.
Signed-off-by: Eddie Kovsky
---
include/linux/module.h | 7 +++
kernel/module.c| 44 ++
Provide a mechanism to check if the address of a variable is
const or ro_after_init. It mimics the existing functions that test if an
address is inside the kernel's text section.
Signed-off-by: Eddie Kovsky
---
include/linux/kernel.h | 2 ++
kernel/extable.c | 29 +
' of git://git.kernel.dk/linux-block
# extra tests on tree/branch linux-next/master
git bisect good 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 11:40121+
255 Add linux-next specific files for 20170217
---
0-DAY kernel test infrastructureOpen Source Technology Cente
Hi Kees,
It's an old patch, however the panic still happens in linux-next 20170217.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 3dc33bd30f3e1c1bcaaafa3482737694debf0f0b
Author: Kees Cook
AuthorDate: Wed Aug 12 17:55:19 2015 -0700
Commit: Ingo M
1) Fix leak in dpaa_eth error paths, from Dan Carpenter.
2) Use after free when using IPV6_RECVPKTINFO, from Andrey Konovalov.
3) fanout_release() cannot be invoked from atomic contexts, from
Anoob Soman.
4) Fix bogus attempt at lockdep annotation in IRDA.
5) dev_fill_metadata_dst() can OOP
d 6dc39c50e4aeb769c8ae06edf2b1a732f3490913 # 10:43 0-
2 Merge branch 'for-linus' of git://git.kernel.dk/linux-block
# extra tests on tree/branch linux-next/master
git bisect bad 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 11:07 0-
1 Add linux-next specific files for 2
a7b2f4dcac3fcb07ff06b0ae7396201fd6 # 04:30 0-
2 Merge tag 'powerpc-4.10-5' of
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
# extra tests on tree/branch linux-next/master
git bisect bad 4ce4a759a3e221b5265ebd03c2fb69a7cf3e # 04:35 0-
28 Add linux-
On 02/18/2017 01:22 AM, Christian König wrote:
> Am 17.02.2017 um 08:11 schrieb Joe Perches:
>> To enable eventual removal of pr_warning
>>
>> This makes pr_warn use consistent for drivers/gpu
>>
>> Prior to this patch, there were 15 uses of pr_warning and
>> 20 uses of pr_warn in drivers/gpu
>>
In the end of macro wait_event_interruptible_lock_irq_timeout(), there is
a semicolon, and at the location where this macro is referenced by macro
wait_event_interruptible_lock_irq_timeout(), there is another semicolon,
then we have two semicolon at end of a line.
Redundant semicolons here doesn'
On February 16, 2017 4:31:16 AM GMT+08:00, Dan Carpenter
wrote:
>On Wed, Feb 15, 2017 at 09:33:15AM +0100, Arnd Bergmann wrote:
>> I see the same warning was addressed very differently in 99277c1f9962
>> ("Staging: rtl8192e: Fix Sparse warning of cast to restricted __le16
>in
>> rtllib_crypt_tki
Fix following checks:
CHECK: Avoid crashing the kernel - try using WARN_ON & recovery code rather
than BUG() or BUG_ON()
+ BUG_ON((index+2) >= BCM2048_MAX_RDS_RT);
CHECK: spaces preferred around that '+' (ctx:VxV)
+ BUG_ON((index+2) >= BCM2048_MAX_RDS_RT);
^
CHE
There's no code here because the patch is trivial, but I want to run
the idea by you all first to see if there are any issues.
VMX is silly and forces the TSS limit to the minimum on VM exits. KVM
wastes lots of cycles bumping it back up to accomodate the io bitmap.
I propose that we rework this
Hi,
On Fri, Feb 17, 2017 at 12:40:41PM -0800, Dmitry Torokhov wrote:
> > AFAIK there is no mainline board using the DT except ours (and the upcoming
> > OMAP5-Pyra), so we shouldn't care too much. If you prefer, you can remove
> > this
> > compatibility property. We don't need it for our devices.
rds.h is exported to /usr/include/rds.h, so u8, u64 leads to
errors like below.
/usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before
'u8'
/usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before
'u8'
Fix it by following same types as rest of the us
From: Santosh Shilimkar
rds.h is exported to /usr/include/rds.h, so u8, u64 leads to
errors like below.
/usr/include/linux/rds.h:197: error: expected specifier-qualifier-list before
'u8'
/usr/include/linux/rds.h:202: error: expected specifier-qualifier-list before
'u8'
Fix it by following sa
On Fri, 2017-02-17 at 14:50 -0800, Joe Perches wrote:
> On Fri, 2017-02-17 at 22:41 +0100, Shiva Kerdel wrote:
> > Braces should be used on all arms of these statements (CHECK)..
>
> []
> > diff --git a/drivers/staging/ks7010/ks_hostif.c
> > b/drivers/staging/ks7010/ks_hostif.c
>
> []
> > @@ -21
On Fri, Feb 17, 2017 at 04:28:37PM -0600, Yves Vandervennet wrote:
> Moritz,
>
> whatever solution we decide to go with has to work with other OS'es. The
> last thing we want to do is to have wrappers that are Linux specific.
I do agree that we should make sure the format is reasonably well
do
Ok, I personally like that better anyhow. Also, there was mention of
the line limit even exceeding 100 characters (130ish?) and that was
being tossed around at one point (if I remember correctly).
On Fri, Feb 17, 2017 at 8:38 PM, Joe Perches wrote:
> On Fri, 2017-02-17 at 20:32 -0500, Adan Hawth
On Friday, February 17, 2017 05:26:59 PM Florian Fainelli wrote:
>
> On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote:
> > On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote:
> >> On 02/17/2017 10:30 AM, Markus Mayer wrote:
> >>> From: Markus Mayer
> >>>
> >>> Add maintainer informati
From: Rafael J. Wysocki
The user/admin documentation of cpufreq is badly outdated. It
conains stale and/or inaccurate information along with things
that are not particularly useful. Also, some of the important
pieces are missing from it.
For this reason, add a new user/admin document for cpufr
Thanks, Joe.
Is this to say that scripts/checkpatch.pl should be updated to some
higher column limit? I have made these cleanup changes before in a
like manner.
On Fri, Feb 17, 2017 at 8:17 PM, Joe Perches wrote:
> On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote:
>> Fix checkpatch.pl war
On Fri, 2017-02-17 at 20:32 -0500, Adan Hawthorn wrote:
> Thanks, Joe.
>
> Is this to say that scripts/checkpatch.pl should be updated to some
> higher column limit? I have made these cleanup changes before in a
> like manner.
Hard to say.
There could be some sensitivity to long identifier
name
On Thursday, February 16, 2017 05:21:50 PM John Keeping wrote:
> Since commit 2d984ad132a8 ("PM / QoS: Introcuce latency tolerance device
> PM QoS type") we reassign "c" to point at qos->latency_tolerance before
> freeing c->notifiers, but the notifiers field of latency_tolerance is
> never used.
>
On 02/17/2017 05:20 PM, Rafael J. Wysocki wrote:
> On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote:
>> On 02/17/2017 10:30 AM, Markus Mayer wrote:
>>> From: Markus Mayer
>>>
>>> Add maintainer information for bmips-cpufreq.c.
>>>
>>> Signed-off-by: Markus Mayer
>>
>> Looks great
On Friday, February 17, 2017 02:18:44 PM Geert Uytterhoeven wrote:
> When passing "test_suspend=mem" to the kernel:
>
> PM: can't test 'mem' suspend state
>
> and the suspend test is not run.
>
> Commit 406e79385f3223d8 ("PM / sleep: System sleep state selection
> interface rework") changed
On Friday, February 17, 2017 04:36:39 PM Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven
> Cc: Rafael J. Wysocki
> Cc: linux...@vger.kernel.org
> ---
> Documentation/power/states.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/power/state
On Friday, February 17, 2017 11:24:56 AM Florian Fainelli wrote:
> On 02/17/2017 10:30 AM, Markus Mayer wrote:
> > From: Markus Mayer
> >
> > Add maintainer information for bmips-cpufreq.c.
> >
> > Signed-off-by: Markus Mayer
>
> Looks great, thanks for adding this, one nit below:
>
> > ---
>
On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote:
> Fix checkpatch.pl warning of the form "WARNING: line over 80 characters."
[]
> diff --git a/drivers/staging/bcm2835-audio/bcm2835.h
> b/drivers/staging/bcm2835-audio/bcm2835.h
[]
> @@ -163,8 +163,10 @@ int bcm2835_audio_write(struct bcm2835
On 02/15/2017 06:19 PM, Steve Longerbeam wrote:
From: Russell King
Setting and getting frame rates is part of the negotiation mechanism
between subdevs. The lack of support means that a frame rate at the
sensor can't be negotiated through the subdev path.
Add support at MIPI CSI2 level for
On 02/15/2017 06:19 PM, Steve Longerbeam wrote:
From: Russell King
Setting and getting frame rates is part of the negotiation mechanism
between subdevs. The lack of support means that a frame rate at the
sensor can't be negotiated through the subdev path.
Add support at MIPI CSI2 level for
Thank you, Joe.
Please remove this patch at this time; it was sent in error.
On Fri, Feb 17, 2017 at 6:04 PM, Joe Perches wrote:
> On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote:
>> Fix checkpatch.pl warning of the form "WARNING: Use of volatile is
>> usually wrong: see Documentation/pro
On Fri, 2017-02-17 at 15:57 -0800, Nicolin Chen wrote:
> On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote:
> > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote:
> > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> > > > To enable eventual removal of pr_warning
On 02/17/2017 10:29 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Feb 17, 2017 at 11:33:29AM +0900, Taeung Song escreveu:
Hi, Arnaldo :)
Regarding perf annotate:
1) Problem : wrong line numbers on perf-annotate (both stdio and TUI)
2) Problem : wrong sum of overhead(percent) matching source li
Viresh Kumar writes:
> Some platforms have the capability to configure the performance state of
> their Power Domains. The performance levels are represented by positive
> integer values, a lower value represents lower performance state.
>
> This patch registers the power domain framework for PM
On Fri, Feb 17, 2017 at 10:01:59PM +0200, Krzysztof Kozlowski wrote:
> max14577 family of drivers are used only on Exynos-based ARMv7 boards
> which all were converted to DeviceTree long time ago. Remove the
> support for platform data to simplify the driver.
Acked-by: Mark Brown
signature.asc
Viresh Kumar writes:
> With runtime PM, the devices get suspended while the system is up and
> running in order to save power. At such times, it is important to
> re-evaluate the required performance state of the domain, in order to
> choose a lower state if possible.
>
> This patch updates the g
On Fri, Feb 17, 2017 at 11:48:54PM +, Mark Brown wrote:
> On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote:
> > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> > > To enable eventual removal of pr_warning
> > >
> > > This makes pr_warn use consistent for sound/soc
>
On 18.02.2017 00:44, Cong Wang wrote:
On Fri, Feb 17, 2017 at 3:38 PM, Gabriel C wrote:
My card seems to use the e1000e driver which is buit-in..
Anyway here an objdump -x :
http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/objdump-x_e1000.ko.txt
Found disable_hardirq() but not
On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote:
> On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> > To enable eventual removal of pr_warning
> >
> > This makes pr_warn use consistent for sound/soc
> >
> > Prior to this patch, there were 5 uses of pr_warning and
> > 10
On 18.02.2017 00:25, Cong Wang wrote:
On Fri, Feb 17, 2017 at 3:16 PM, Gabriel C wrote:
On 17.02.2017 23:38, Cong Wang wrote:
On Fri, Feb 17, 2017 at 1:20 PM, Gabriel C wrote:
Hi all,
while poking at a different issue I found the following on my logs :
[85362.132770] BUG: sleeping fu
On Fri, Feb 17, 2017 at 11:28:43AM -0800, kernelci.org bot wrote:
> stable-rc boot: 31 boots: 0 failed, 31 passed (v4.4.49-21-g967e7e889dce)
Better than the 4.9 number of boots, but still odd...
On Fri, Feb 17, 2017 at 11:28:44AM -0800, kernelci.org bot wrote:
> stable-rc boot: 4 boots: 0 failed, 4 passed (v4.9.10-33-gf6f9e9361112)
That's a small number of boots, really small, what went wrong here?
Do you all need more time?
thanks,
greg k-h
On Fri, Feb 17, 2017 at 3:38 PM, Gabriel C wrote:
>
> My card seems to use the e1000e driver which is buit-in..
>
> Anyway here an objdump -x :
>
> http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/objdump-x_e1000.ko.txt
>
Found disable_hardirq() but not disable_irq().
Are you sure the k
From: Andrew Lunn
Date: Fri, 17 Feb 2017 23:36:51 +0100
> Please take your time to do this right. Lots of small patches, which
> are obviously correct.
Agreed.
Signed-off-by: Lepton Wu
---
drivers/mtd/mtdblock.c| 33 +
drivers/mtd/mtdblock_ro.c | 4 ++--
2 files changed, 19 insertions(+), 18 deletions(-)
diff --git a/drivers/mtd/mtdblock.c b/drivers/mtd/mtdblock.c
index bb4c14f83c75..3d2da76287a7 100644
--- a/driver
On Fri, Feb 17, 2017 at 2:39 PM, Bjorn Helgaas wrote:
> On Thu, Feb 16, 2017 at 10:12:47PM -0800, Yinghai Lu wrote:
>
> I don't think it really makes sense to tie PDC handling with the
> attention button. It might happen to avoid the problem on your
> system, but I don't see the logical connectio
Up until now only platforms using legacy platform data were able to switch
AUX/VBAT/GPIO pin in GPIO mode and use it as regular GPIO line. Let's
allow platforms using generic device properties to do the same.
Signed-off-by: Dmitry Torokhov
---
.../devicetree/bindings/input/touchscreen/ad7879.txt
Instead of rolling our own infrastructure to provide uniform access to I2C
and SPI buses, let's switch to using regmap.
Signed-off-by: Dmitry Torokhov
---
Michael,
I am a bit (actually a lot) confused how this driver was working with SPI
and Blackfin, which is, as far as I understand, little-en
The mm-of-the-moment snapshot 2017-02-17-15-31 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
gpiochip_add now has a managed version, and we can remove sysfs attribute
group via devm_add_action_or_reset (at least until we have devm version of
sysfs_crreate_group). This allows us to get rid of ad7879_remove().
Signed-off-by: Dmitry Torokhov
---
drivers/input/touchscreen/ad7879-i2c.c | 12
On 17-02-16 09:10 PM, Jason Wang wrote:
>
>
> On 2017年02月17日 12:53, John Fastabend wrote:
>> On 17-02-15 01:08 AM, Jason Wang wrote:
>>> We set queues before reset which will cause a crash[1]. This is
>>> because is_xdp_raw_buffer_queue() depends on the old xdp queue pairs
>>> number to do the co
On Fri, Feb 17, 2017 at 3:16 PM, Gabriel C wrote:
>
>
> On 17.02.2017 23:38, Cong Wang wrote:
>>
>> On Fri, Feb 17, 2017 at 1:20 PM, Gabriel C wrote:
>>>
>>> Hi all,
>>>
>>> while poking at a different issue I found the following on my logs :
>>>
>>> [85362.132770] BUG: sleeping function called f
On 18.02.2017 00:16, Gabriel C wrote:
On 17.02.2017 23:38, Cong Wang wrote:
On Fri, Feb 17, 2017 at 1:20 PM, Gabriel C wrote:
Hi all,
while poking at a different issue I found the following on my logs :
[85362.132770] BUG: sleeping function called from invalid context at
kernel/irq/manag
Viresh Kumar writes:
> An earlier series[1] tried to implement bindings for PM domain
> performance states. Rob Herring suggested that we can actually merge the
> supporting code first instead of bindings, as that will make things
> easier to understand for all. The bindings can be decided and me
On 17.02.2017 23:38, Cong Wang wrote:
On Fri, Feb 17, 2017 at 1:20 PM, Gabriel C wrote:
Hi all,
while poking at a different issue I found the following on my logs :
[85362.132770] BUG: sleeping function called from invalid context at
kernel/irq/manage.c:110
[85362.132771] in_atomic(): 1, ir
On February 17, 2017 3:02:33 PM PST, Andy Lutomirski
wrote:
>On Fri, Feb 17, 2017 at 1:01 PM, Linus Torvalds
> wrote:
>> On Fri, Feb 17, 2017 at 12:12 PM, Andy Lutomirski
> wrote:
>>>
>>> At the very least, I'd want to see
>>> MAP_FIXED_BUT_DONT_BLOODY_UNMAP_ANYTHING. I *hate* the current
>>> in
A release candidate Git v2.12.0-rc2 is now available for testing
at the usual places. It is comprised of 487 non-merge commits
since v2.11.0, contributed by 67 people, 21 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following pu
On Fri, 2017-02-17 at 15:16 -0500, Nathan Howard wrote:
> Fix checkpatch.pl warning of the form "WARNING: Use of volatile is
> usually wrong: see Documentation/process/volatile-considered-harmful.rst."
Why are you sure the volatile use is not necessary?
> Signed-off-by: Nathan Howard
> ---
> dr
Michał Zegan writes:
> W dniu 17.02.2017 o 20:47, Kevin Hilman pisze:
>> Michał Zegan writes:
>>
>>> The mmc host was added in meson_mmc_probe, but never removed in
>>> meson_mmc_remove.
>>> Fix that by removing the host before deallocating other resources.
>>>
>>> Signed-off-by: Michał Zegan
On Fri, Feb 17, 2017 at 1:01 PM, Linus Torvalds
wrote:
> On Fri, Feb 17, 2017 at 12:12 PM, Andy Lutomirski wrote:
>>
>> At the very least, I'd want to see
>> MAP_FIXED_BUT_DONT_BLOODY_UNMAP_ANYTHING. I *hate* the current
>> interface.
>
> That's unrelated, but I guess w could add a MAP_NOUNMAP f
Do not manipulate evbit/keybit directly, use helper for that.
Signed-off-by: Dmitry Torokhov
---
drivers/input/touchscreen/tsc2007_core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/tsc2007_core.c
b/drivers/input/touchscreen/tsc2007_core.c
ind
On 02/16, Imran Khan wrote:
> diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
> index 18ec52f..4f0ccf8 100644
> --- a/drivers/soc/qcom/smem.c
> +++ b/drivers/soc/qcom/smem.c
> @@ -85,6 +85,9 @@
> /* Max number of processors/hosts in a system */
> #define SMEM_HOST_COUNT
On Fri, 2017-02-17 at 22:41 +0100, Shiva Kerdel wrote:
> Braces should be used on all arms of these statements (CHECK)..
[]
> diff --git a/drivers/staging/ks7010/ks_hostif.c
> b/drivers/staging/ks7010/ks_hostif.c
[]
> @@ -2148,8 +2148,9 @@ void hostif_sme_mode_setup(struct ks_wlan_private *priv)
>
Hi Andy,
On Fri, Feb 17, 2017 at 2:23 AM, Andy Shevchenko
wrote:
> On Fri, Feb 17, 2017 at 3:01 AM, Hoan Tran wrote:
>> Next generation of X-Gene SoC's GPIO hardware register map is very
>> similar to DW GPIO. It only differs by a few register addresses.
>> This patch modifies DW GPIO driver to
On Fri, Feb 17, 2017 at 10:05:31AM -0500, Vivien Didelot wrote:
> The 6390 family of chips use only 2 of the 3 VTU Data registers to pack
> the MemberTag and PortState VLAN data. This means that they must be
> written or read before or after each VTU/STU operations.
>
> Implement this variant to a
On Thu, Feb 16, 2017 at 10:12:47PM -0800, Yinghai Lu wrote:
> On one system during power off slot, find card get power on right away.
> # echo 0 > /sys/bus/pci/slots/1/power
> pci_hotplug: power_write_file: power = 0
> pciehp :16:00.0:pcie004: pciehp_get_power_status: SLOTCTRL a8 value read
On Fri, Feb 17, 2017 at 1:20 PM, Gabriel C wrote:
> Hi all,
>
> while poking at a different issue I found the following on my logs :
>
> [85362.132770] BUG: sleeping function called from invalid context at
> kernel/irq/manage.c:110
> [85362.132771] in_atomic(): 1, irqs_disabled(): 1, pid: 1153, na
> Note that we are very close from 4.10, so unless there is a major issue
> in the patchset, I'd prefer not to respin new versions. I'd gladly send
> cosmetics fixup later though. I'm waiting for this patchset to land in
> net-next to send the second one ready for cross-chip bridging in DSA.
I kno
On Fri, Feb 17, 2017 at 02:37:12PM +0200, Jarkko Sakkinen wrote:
Hi, I hope the week is ending well for everyone.
> On Fri, Feb 17, 2017 at 03:56:26AM -0600, Dr. Greg Wettstein wrote:
> > On Thu, Feb 16, 2017 at 10:33:04PM +0200, Jarkko Sakkinen wrote:
> >
> > Good morning to everyone.
> >
> >
On 01/10, Imran Khan wrote:
> The socinfo ABI document describes the information provided
> by socinfo driver and the corresponding attributes to access
> that information.
>
> Signed-off-by: Imran Khan
> ---
> Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147
> +
Pe
On Thu, 16 Feb 2017, Ondrej Zary wrote:
> On Tuesday 31 January 2017 02:31:45 Finn Thain wrote:
> [...]
> > Are you trying to figure out which commands are going to disconnect
> > during a transfer? This is really a function of the firmware in the
> > target; there are no good heuristics AFAICT
On Fri, Feb 17, 2017 at 12:36 PM, Dmitry Vyukov wrote:
> On Fri, Feb 17, 2017 at 7:51 PM, Cong Wang wrote:
>>
>> This code was changed a long time ago :
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ed2e923945892a8372ab70d2f61d364b0b6d9054
>>
Moritz,
whatever solution we decide to go with has to work with other OS'es. The
last thing we want to do is to have wrappers that are Linux specific.
Yves
On Wed, 15 Feb 2017, Moritz Fischer wrote:
>>Hi Jason,
>>
>>On Wed, Feb 15, 2017 at 12:37 PM, Jason Gunthorpe
>> wrote:
>>> On Wed, Feb
Hello,
I am trying to mmap a PCI device, but it fails with EINVAL.
...
fd = open("/dev/mem", O_RDWR | O_SYNC);
...
rv = mmap64(0, size, PROT_READ, MAP_SHARED, fd, pci_addr);
...
The pci_addr is the address obtained from lspci output which is a 64 bit
address.
The pci_addr has a value of 0x121f
hisi_spi_nor_probe() ignores clk_prepare_enable() error code.
The patch fixes that.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/mtd/spi-nor/hisi-sfc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers
Hi Michał,
Thanks for collecting relevant credits.
I've applied the patchset to the for-4.12 branch of linux-leds.git.
Best regards,
Jacek Anaszewski
On 02/17/2017 08:57 AM, Michał Kępień wrote:
> This patch series moves the dell-led driver from the LED subsystem to
> the x86 platform driver sub
This one is a false positive. The original code is correct.
I was looking through my mail boxes to see the history of this and why
it hadn't been fixed earlier. Someone tried to fix it in 2011:
https://www.spinics.net/lists/linux-driver-devel/msg17403.html
Then I complained about it again in 201
The following patch series adds the necessary functionality to make the BAU
on UV4 operational. The purpose of these patches is to implement the correct
message completion logic on UV4. Also included is a bug fix to add a field
to the INTD payload. This is needed to verify the source of each messag
On UV4, the destination agent verifies each message by checking the
descriptor qualifier field of the message payload. Messages without this
field set to 0x534749 will cause a hub error to assert.
Split bau_message_payload into uv1_2_3 and uv4 versions to account for the
different payload formats.
The location of the ERROR and BUSY status bits depends on the descriptor
index, i.e. the CPU, of the message. Since this index does not change,
there is no need to calculate the MMR and index location during message
processing. The less work we do in the hot path the better.
Add status_mmr and sta
UV4 does not employ a software-timeout as in previous generations so a new
wait_completion routine without this logic is required. Certain completion
statuses require the AUX status bit in addition to ERROR and BUSY.
Add the read_status routine to construct the full completion status. Use
read_sta
Move the bau_operations declaration after bau struct declarations so the
bau structs can be referenced when adding new functions to
bau_operations. That way we avoid forward declarations of the bau
structs.
Likewise, move uv*_bau_ops structs down to avoid forward declarations of
new functions defi
Remove the present wait_completion routine and add a function pointer by
the same name to the bau_operations struct. Rather than switching on the
UV hub version during message processing, set the architecture-specific
uv*_wait_completion during initialization.
The uv123_bau_ops struct must be spli
Define enumerated constants for each UV hub version and replace magic
numbers with the appropriate constant. This makes our checks against
uvhub_version more robust, and any use of unsupported archs will be
caught during compilation.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
---
arch/x
Dan Carpenter reported this:
---
The patch 9c46b8676271: "scsi: ufs-qcom: dump additional testbus
registers" from Feb 3, 2017, leads to the following static checker
warning:
drivers/scsi/ufs/ufs-qcom.c:1531 ufs_qcom_testbus_cfg_is_ok()
warn: impossible condition
'(host->te
On Fri, Feb 17, 2017 at 11:52 AM, Moritz Fischer wrote:
> Alan,
>
> small nits inline
Hi Moritz,
Thanks for the review!
Alan
>
> On Wed, Feb 15, 2017 at 8:14 AM, Alan Tull wrote:
>> Document that getting a reference to a FPGA Manager has been
>> separated from locking the FPGA Mangager for us
Hi Sean,
I've noticed some issues here, please refer below.
On 02/17/2017 07:05 AM, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> This patch adds documentation for devicetree bindings
> for LED support on MT6323 PMIC
>
> Signed-off-by: Sean Wang
> ---
> .../devicetree/bindings/leds/led
Hi Sean,
Thanks for the updated patch. I have one more comment below.
On 02/17/2017 07:05 AM, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> MT6323 PMIC is a multi-function device that includes
> LED function. It allows attaching up to 4 LEDs which
> can either be on, off or dimmed and/or
On Fri, Feb 17, 2017 at 04:44:19PM +0100, Maxime Ripard wrote:
[...]
> We already have DT bindings for out of tree drivers, there's really
> nothing new here.
We have DT bindings for *hardware*, not for drivers. As stated in
Documentation/devicetree/usage-model.txt:
"The "Open Firmware Device Tre
1 - 100 of 699 matches
Mail list logo
