vzalloc combines vmalloc and memset 0.
The Coccinelle semantic patch used to make this change is as follows:
@@
type T;
T *d;
expression e;
statement S;
@@
d =
-vmalloc
+vzalloc
(...);
if (!d) S
- memset(d, 0, sizeof(T));
Signed-off-by:
acpi_os_allocate_zeroed combines acpi_os_allocate and memset 0.
The Coccinelle semantic patch used to make this change is as follows:
@@
type T;
T *d;
expression e;
statement S;
@@
d =
-acpi_os_allocate
+acpi_os_allocate_zeroed
(...);
if (!d) S
On Thu, Jun 16, 2016 at 07:06:52PM +0100, Ben Hutchings wrote:
> On Thu, 2016-06-16 at 10:55 -0700, Benjamin Poirier wrote:
> > On 2016/06/13 11:46, Netanel Belgazal wrote:
> [...]
> > > +static ssize_t ena_show_small_copy_len(struct device *dev,
> > > + struct device
From: 神田 尚
Date: Fri, 17 Jun 2016 01:49:11 +
> This bug may occur in the following.
>
> user_rtt_fill_64bit <= If mna trap occurred, call do_mna
> +-> do_mna <= Mistake storing registers for fault code and
> address
> +-> winfix_mna
> +-> user_rtt_fill_
On Sat, 18 Jun 2016, Luis R. Rodriguez wrote:
> On Fri, Jun 17, 2016 at 05:35:26PM +0200, Julia Lawall wrote:
> > On Fri, 17 Jun 2016, Luis R. Rodriguez wrote:
> >
> > > On Fri, Jun 17, 2016 at 11:44:26AM +0200, Julia Lawall wrote:
> > > > I'm not sure that this is worth it. It adds a dependen
Function graph tracer currently ignores filters if tracing_thresh is set.
For example, even if set_ftrace_pid is set, then its ignored if tracing_thresh
set, resulting in all processes being traced.
To fix this, we reuse the same entry function as when tracing_thresh is not
set and do everything a
From: Philippe Reynes
Date: Fri, 17 Jun 2016 23:32:15 +0200
> There are two generics functions phy_ethtool_{get|set}_link_ksettings,
> so we can use them instead of defining the same code in the driver.
>
> Signed-off-by: Philippe Reynes
Applied.
From: Philippe Reynes
Date: Fri, 17 Jun 2016 23:32:14 +0200
> The private structure contain a pointer to phydev, but the structure
> net_device already contain such pointer. So we can remove the pointer
> phydev in the private structure, and update the driver to use the
> one contained in struct
Hi Greg,
On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote:
> Hi,
>
> I've finally gotten off my butt and made my quilt trees of patches into
> a "semi-proper" git tree to make it easier for people to test them.
>
> I'm now pushing the patches I accept into the stable queues into the git
>
From: Arnd Bergmann
Date: Fri, 17 Jun 2016 18:15:30 +0200
> The conversion to the 64-bit time based ptp methods left two instances
> of 'struct timespec' in place. This is harmless because 64-bit
> architectures define timespec64 as timespec, and this driver is
> not used on 32-bit machines.
>
>
Hi,
Sorry to be late. In this weekday, I have little time for this thread
because working for alsa-lib[1]. Besides, I'm not full-time developer
for this kind of work. In short, I use my limited private time for this
discussion.
On Jun 15 2016 17:06, Richard Cochran wrote:
> On Wed, Jun 15, 2016 a
Hi Greg,
On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote:
> Hi,
>
> I've finally gotten off my butt and made my quilt trees of patches into
> a "semi-proper" git tree to make it easier for people to test them.
>
> I'm now pushing the patches I accept into the stable queues into the git
>
On 2016/6/17 23:39, Mike Kravetz wrote:
> On 06/17/2016 05:25 AM, Kirill A. Shutemov wrote:
>> From fd22922e7b4664e83653a84331f0a95b985bff0c Mon Sep 17 00:00:00 2001
>> From: "Kirill A. Shutemov"
>> Date: Fri, 17 Jun 2016 15:07:03 +0300
>> Subject: [PATCH] hugetlb: fix nr_pmds accounting with shar
Hi,
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.7-rc3 next-20160617]
[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/Neil-Armstrong/usb-phy-Add-support-for-the
On 2016-06-13 15:40, Naveen N. Rao wrote:
On 2016/06/10 10:47PM, David Miller wrote:
From: "Naveen N. Rao"
Date: Tue, 7 Jun 2016 19:02:17 +0530
> Please note that patch [2] is a pre-requisite for this patchset, and is
> not yet upstream.
...
> [1] http://thread.gmane.org/gmane.linux.kernel/2
On Fri, Jun 17, 2016 at 5:15 PM, Dave Hansen wrote:
>
> Now sending with actual stable@ address...
>
> --
>
> From: Dave Hansen
>
> cpufeatures.h currently defines X86_BUG(9) twice on 32-bit:
Acked-by: Andy Lutomirski # who is suitably embarrassed
That being said, you or Ingo should consider f
From: Ivan Khoronzhuk
Date: Fri, 17 Jun 2016 13:25:38 +0300
> There is no reason in rx_descs property because davinici_cpdma
> driver splits pool of descriptors equally between tx and rx channels.
> So, this patch series makes driver to use available number of
> descriptors for rx channels.
>
>
Hi Greg,
On 06/17/2016 08:16 PM, Greg KH wrote:
Hi,
I've finally gotten off my butt and made my quilt trees of patches into
a "semi-proper" git tree to make it easier for people to test them.
I'm now pushing the patches I accept into the stable queues into the git
tree here:
git://git.
On 06/17/2016 06:08 PM, Brian Norris wrote:
On Fri, Jun 17, 2016 at 02:41:51PM -0700, Guenter Roeck wrote:
On Fri, Jun 17, 2016 at 12:58:12PM -0700, Brian Norris wrote:
+int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev,
+ struct cros_ec_command *msg)
+{
+
On Sun, Jun 05, 2016 at 08:10:50PM -0700, Andy Eleftherion wrote:
> Replaced ACCESS_ONCE calls with READ/WRITE_ONCE calls.
Why?
On Wed, Jun 01, 2016 at 10:35:57AM +0100, Ian Abbott wrote:
> On 01/06/16 10:19, Ashwin Ravichandran wrote:
> > Fixed a coding style issue.
> >
> > Signed-off-by: Ashwin Ravichandran
> > ---
> > drivers/staging/comedi/drivers/addi-data/hwdrv_apci3501.c | 2 +-
> > drivers/staging/comedi/driver
On Wed, Jun 01, 2016 at 02:19:35AM -0700, Ashwin Ravichandran wrote:
> Fixed a coding style issue.
Which one?
And where are the 2648 previous patches in this series?
thanks,
greg k-h
On Tue, May 31, 2016 at 09:00:59PM -0300, Pedro Nieto wrote:
> From: PedroNieto
No space?
>
> Fixed a coding style issue.
Which one?
Please be specific.
On Thu, May 26, 2016 at 06:35:48PM -0500, Steven Laabs wrote:
> Fixed coding style issues.
That's very vague, please be specific and exact.
thanks,
greg k-h
On Tue, May 17, 2016 at 10:23:44PM +0530, Amit Ghadge wrote:
> This is a patch to the quatech_daqp_cs.c file that fixes by using
> unsigned int instead of unsigned, following warning found by checkpatch.
> * WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
>
> Signed-off-by: Amit Ghadge
>
On Mon, May 16, 2016 at 11:04:31PM +0530, Amit Ghadge wrote:
> Fixed a warning issue to use 'unsigned int'.
>
> Signed-off-by: Amit Ghadge
> ---
> drivers/staging/comedi/drivers/quatech_daqp_cs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Doesn't apply to my tree :(
From: Sudip Mukherjee
Date: Thu, 16 Jun 2016 22:19:31 +0100
> The variable i was declared but was never used and we were getting a
> build warning for that.
>
> Signed-off-by: Sudip Mukherjee
Applied, thanks.
On Sat, May 28, 2016 at 10:56:48AM +0530, Ravishankar Karkala Mallikarjunayya
wrote:
> This is a patch to the s626.c file that fixes up a type issues like
> i.e Prefer kernel type 'u8' over 'uint8_t'
> Prefer kernel type 'u16' over 'uint16_t'
> Prefer kernel type 'u32' over 'uint32_t'
>
On Mon, May 30, 2016 at 03:21:27PM +0100, Luis de Bethencourt wrote:
> On 28/05/16 06:26, Ravishankar Karkala Mallikarjunayya wrote:
> > This is a patch to the s626.c file that fixes up a line over 80
> > characters issues found by the checkpatch.pl tool.
> >
> > Signed-off-by: Ravishankar Karkal
On Fri, Jun 17, 2016 at 11:39:04PM -0400, William Breathitt Gray wrote:
> On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote:
> >On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote:
> >> The PC/104 drivers were changed to utilize the ISA bus driver as part of
> >> the origin
On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote:
>On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote:
>> The PC/104 drivers were changed to utilize the ISA bus driver as part of
>> the original patchset which attempted to decouple the X86_32 dependency
>> from the ISA Kc
Use regmap instead of open-coding IO access and caching
Signed-off-by: Lars-Peter Clausen
[koike: port for upstream]
Signed-off-by: Helen Koike
---
sound/soc/codecs/tpa6130a2.c | 166 ---
sound/soc/codecs/tpa6130a2.h | 2 -
2 files changed, 46 insertion
Add tpa6130a2 controls by the component API and update rx51 accordingly
Signed-off-by: Lars-Peter Clausen
[koike: port for upstream]
Signed-off-by: Helen Koike
---
sound/soc/codecs/tpa6130a2.c | 26 +-
sound/soc/codecs/tpa6130a2.h | 1 -
sound/soc/omap/rx51.c| 2
Add DAPM support and updated rx51 accordingly.
As a consequence:
- the exported function tpa6130a2_stereo_enable is not needed anymore
- the mutex is dealt in the DAPM
- the power state is tracked by the DAPM
Signed-off-by: Lars-Peter Clausen
[koike: port for upstream]
Signed-off-by: Helen Koike
The current tpa6130a2 driver supports only a single instance.
This patch series add support for multiple instances by removing the global
variable that holds the instance.
This is performed by using the component API, regmap, the
snd_soc_{info,put,get}_volsw API and DAPM.
This patch series also to
Use snd_soc_{info,get,put}_volsw instead of custom volume functions
Signed-off-by: Lars-Peter Clausen
[koike: port for upstream]
Signed-off-by: Helen Koike
---
sound/soc/codecs/tpa6130a2.c | 64 ++--
1 file changed, 2 insertions(+), 62 deletions(-)
diff
On Wed, Jun 15, 2016 at 04:02:40AM +0100, James Simmons wrote:
>
> > > This may also possibly help to save cycles due to high usage and
> > > contention when using a generic kmem_cache (when they stay separate
> > > from others, thanks for the precision!).
> >
> > Have you measured this?
> >
> >
Greg,
I checkout your staging tree[1].
Not find this patch. Can you take it thanks!
[1]git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
On 2016/6/5 23:02, Greg KH wrote:
> On Sun, Jun 05, 2016 at 04:51:23PM +0800, Chen Feng wrote:
>> Hi Greg,
>>
>> Can you take this patch?
>
On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote:
> On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote:
> >On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote:
> >> On 31.05.2016 17:25, Greg KH wrote:
> >> > On Tue, May 31, 2016 at 07:23:06AM -0400, William
Hey Ingo,
Please pull a bunch of fixes for liblockdep from Ben and Vishal.
Mostly build failures as a result of kernel changes.
Thanks,
Sasha
===
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git
Hi,
I've finally gotten off my butt and made my quilt trees of patches into
a "semi-proper" git tree to make it easier for people to test them.
I'm now pushing the patches I accept into the stable queues into the git
tree here:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-st
Hi Sebastian:
On 2016年06月16日 22:36, Sebastian Reichel wrote:
Hi,
On Mon, Apr 25, 2016 at 02:55:36PM +0800, Andy Yan wrote:
This driver parses the reboot commands like "reboot bootloader"
and "reboot recovery" to get a boot mode described in the
device tree , then call the write interfae to sto
On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote:
>On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote:
>> On 31.05.2016 17:25, Greg KH wrote:
>> > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote:
>> >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Wall
On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote:
> On 31.05.2016 17:25, Greg KH wrote:
> > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote:
> >> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote:
> >>> On Sat, May 28, 2016 at 12:08 AM, William Br
On one system found bunch of claim resource fail from pci device.
pci_sun4v f02b894c: PCI host bridge to bus :00
pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus
address [0x-0xfff])
pci_bus :00: root bus resource [mem 0x2-0x27eff] (b
If host bridge does not have mmio64 above 4G, We don't need to
treat device non-pref mmio64 as as pref mmio64.
Signed-off-by: Yinghai Lu
Tested-by: Khalid Aziz
---
drivers/pci/setup-bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/s
If any bridge up to root only have 32bit pref mmio, We don't need to
treat device non-pref mmio64 as as pref mmio64.
We need to move pci_bridge_check_ranges calling early.
For parent bridges pref mmio BAR may not allocated by BIOS, res flags
is still 0, we need to have it correct set before we che
Same as sparc version.
Make resource with consistent sequence
like other arch or directly from pci_read_bridge_bases(),
even when non-pref mmio is missing, or out of ordering in firmware reporting.
Just hold i = 1 for non pref mmio, and i = 2 for pref mmio.
Signed-off-by: Yinghai Lu
Cc: linuxpp
>From 5b2854155 (PCI: Restrict 64-bit prefetchable bridge windows to 64-bit
resources), we change the logic for pref mmio allocation:
When bridge pref support mmio64, we will only put children pref
that support mmio64 into it, and will put children pref mmio32
into bridge's non-pref mmio32.
That c
Add has_mem64 for struct host_bridge, on root bus that does not support
mmio64 above 4g, will not set that.
We will use that info next two following patches:
1. Don't treat non-pref mmio64 as pref mmio, so will not put
it under bridge's pref range when rescan the devices
2. will keep pref mmio6
Add pci_find_bus_resource() to return bus resource for input resource.
In some case, we may only have bus instead of dev.
It is same as pci_find_parent_resource, but take bus as input.
Signed-off-by: Yinghai Lu
---
drivers/pci/pci.c | 27 ---
include/linux/pci.h | 2 +
Hi Bjorn,
After 5b28541552ef (PCI: Restrict 64-bit prefetchable bridge windows
to 64-bit resources), we have several reports on resource allocation
failure, and we try to fix the problem with resource clip, and find
more problems.
One is from sparc that have problem with clip as we don't parse
me
We still get "no compatible bridge window" warning on sparc T5-8
after we add support for 64bit resource parsing for root bus.
PCI: scan_bus[/pci@300/pci@1/pci@0/pci@6] bus no 8
PCI: Claiming :00:01.0: Resource 15: 8001..8004afff
[220c]
PCI: Claiming :01:00.0: Resou
After we added 64bit mmio parsing, we got some "no compatible bridge window"
warning on anther new model that support 64bit resource.
It turns out that we can not use mem_space.start as 64bit mem space
offset, aka there is mem_space.start != offset.
Use child_phys_addr to calculate exact offset a
In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try
to check exposed value with resource start/end in proc mmap path.
|start = vma->vm_pgoff;
|size = ((pci_resource_len(pdev, resno) - 1) >> PAGE_SHIFT) + 1;
|pci_start = (mmap_api == PCI_MMAP_PROCFS) ?
|
On Fri, Jun 17, 2016 at 12:52 PM, Bjorn Helgaas wrote:
>>
>> and respin the whole patchset today.
>
> I added your acks and pushed the result to pci/resource. I'll also
> post these formally on the list so they're easier to find.
Please review patchset v13 that is against your new pci/resource b
After
PCI: Let pci_mmap_page_range() take resource address
No user for __pci_mmap_make_offset in those arch.
Remove them.
Signed-off-by: Yinghai Lu
Cc: linuxppc-...@lists.ozlabs.org
Cc: sparcli...@vger.kernel.org
Cc: linux-xte...@linux-xtensa.org
---
arch/microblaze/pci/pci-common.c | 63 ---
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource
flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://bugzilla
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
This patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource
flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://bugzilla
On one system found strange "no compatible bridge window" warning
even we already had pref_compat support that add extra pref bit for device
resource.
PCI: Claiming :00:01.0: Resource 14: 00020001..000200010fff
[10220c]
PCI: Claiming :01:00.0: Resource 1: 00020001..000
For device resource with PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource.
so this patch set IORESOUCE_MEM_64 for 64bit resource during OF device resource
flags parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link: https://
When user access /sys/.../resourceX with pci_mmap_resource(),
pci_mmap_resource():
...
pci_resource_to_user(pdev, i, res, &start, &end);
vma->vm_pgoff += start >> PAGE_SHIFT;
mmap_type = res->flags & IORESOURCE_MEM ? pci_mmap_mem : pci_mmap_io;
return pci_mm
The driver is using the set_bias_level to control the power on and
off so it should get SND_SOC_BIAS_OFF in order to proceed normal
powering sequences. This patch enables the idle_bias_off option so
the DAPM core will set the bias level to SND_SOC_BIAS_OFF instead
of stopping at SND_SOC_BIAS_STANDB
Thanks!
On 2016/6/18 2:29, weiyj...@163.com wrote:
> From: Wei Yongjun
>
> In case of error, the function devm_clk_get() returns ERR_PTR()
> and never returns NULL. The NULL test in the return value check
> should be replaced with IS_ERR().
>
> Signed-off-by: Wei Yongjun
Reviewed-by: Chen Fen
On Fri, Jun 17, 2016 at 05:35:26PM +0200, Julia Lawall wrote:
> On Fri, 17 Jun 2016, Luis R. Rodriguez wrote:
>
> > On Fri, Jun 17, 2016 at 11:44:26AM +0200, Julia Lawall wrote:
> > > I'm not sure that this is worth it. It adds a dependency on a tool that
> > > seems not to be well maintained. I
On Fri, Jun 17, 2016 at 11:03 PM, Rafael J. Wysocki wrote:
> On Fri, Jun 17, 2016 at 6:12 PM, Borislav Petkov wrote:
>> On Fri, Jun 17, 2016 at 05:28:10PM +0200, Rafael J. Wysocki wrote:
>>> A couple of questions:
>>> - I guess this is reproducible 100% of the time?
>>
>> Yap.
>>
>> I took latest
On Fri, Jun 17, 2016 at 02:41:51PM -0700, Guenter Roeck wrote:
> On Fri, Jun 17, 2016 at 12:58:12PM -0700, Brian Norris wrote:
> > +int cros_ec_cmd_xfer_status(struct cros_ec_device *ec_dev,
> > + struct cros_ec_command *msg)
> > +{
> > + int ret;
> > +
> > + ret = cros_ec
The f2fs_map_blocks is very related to the performance, so let's avoid any
latency to read ahead node pages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 2 +-
fs/f2fs/file.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 0832528..
The readahead nat pages are more likely to be reclaimed quickly, so it'd better
to gather more free nids in advance.
And, let's keep some free nids as much as possible.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 2 ++
fs/f2fs/f2fs.h | 1 +
fs/f2fs/node.c | 9 ++---
fs
Let's keep more node/meta pages in run time.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/segment.h b/fs/f2fs/segment.h
index d74cc33..57d450f 100644
--- a/fs/f2fs/segment.h
+++ b/fs/f2fs/segment.h
@@ -715,9 +7
On Thu, Jun 16, 2016 at 08:27:41AM +0800, Lu Baolu wrote:
> Hi Greg,
>
> On 06/09/2016 10:39 AM, Lu Baolu wrote:
> > Hi Greg,
> >
> > On 06/08/2016 11:45 PM, Greg Kroah-Hartman wrote:
> >> On Wed, Jun 08, 2016 at 03:56:04PM +0800, Lu Baolu wrote:
> >>> Hi Greg,
> >>>
> >>> On 06/08/2016 12:45 PM,
On Fri, 2016-06-17 at 17:00 -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 17, 2016 at 12:16:47PM -0400, Daniel Micay escreveu:
> > On Fri, 2016-06-17 at 08:54 +0200, Peter Zijlstra wrote:
> > > This Changelog is completely devoid of information. _WHY_ are you
> > > doing this?
>
> > Attack
On Sat, Jun 18, 2016 at 01:40:43AM +0200, Luis R. Rodriguez wrote:
> On Thu, Jun 16, 2016 at 04:59:11PM -0700, Luis R. Rodriguez wrote:
> > FWIW running it against linux-next next-20160616 on a 32-core system takes
> > about 3 minutes using glimpse, also ~3 minutes with gitgrep and produces the
> >
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-4.7-rc4
to receive an ACPI update for v4.7-rc4 with top-most commit
46577e6a052ff5add7577ac748fb8628b3c3c7c9
Merge branch 'acpica-fixes'
on top of commit 5edb56491d4812c42175980759da53388e5d8
Hi Vinay,
On 17 June 2016 at 19:23, Vinay Simha BN wrote:
> v6:
> * emil review comments incorporated
>PANEL_NUM_REGULATORS dropped, return ret added at necessary
>places, if checks dropped for backlight and gpios
Looks like some of my suggestions went below the radar. Did you miss
the
On Fri, Jun 17, 2016 at 09:53:50AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > Nothing in the control-dependencies section of memory-barriers.txt
> > says that control dependencies don't extend beyond the end of the
> > if-statement containing the control dependency. Worse yet
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.7-rc4
to receive power management fixes for v4.7-rc4 with top-most commit
9d066a252786e1a18484a6283f82614d42a9f4ac
Merge branches 'pm-opp' and 'pm-cpufreq-fixes'
on top of commit 5edb56491d48
Add regression test scripts open_loop_test.sh, and bind_unbind_sample.sh.
Also add regression_test.txt that describes the regression test procedure.
Signed-off-by: Shuah Khan
---
.../selftests/media_tests/bind_unbind_sample.sh| 13 +++
.../selftests/media_tests/open_loop_test.sh|
This patch series changes an exixtsing test to randomize the loop count,
adds a new test, and regression test scripts, and regression test how to.
Shuah Khan (4):
selftests: media_device_test change it to randomize loop count
selftests: add media_device_open test
selftests: add media control
Change it to randomize the loop count instead of hardcoded number of times
ioctl is called.
Signed-off-by: Shuah Khan
---
.../testing/selftests/media_tests/media_device_test.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/tools/testing/selftests/media_t
Add media_device_open to .gitignore
Signed-off-by: Shuah Khan
---
tools/testing/selftests/media_tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/media_tests/.gitignore
b/tools/testing/selftests/media_tests/.gitignore
index 1c07117..faf5891 100644
---
Add a new media test to open, run ioctl, and close the media device file.
Signed-off-by: Shuah Khan
---
tools/testing/selftests/media_tests/Makefile | 4 +-
.../selftests/media_tests/media_device_open.c | 81 ++
2 files changed, 83 insertions(+), 2 deletions(-)
c
Now sending with actual stable@ address...
--
From: Dave Hansen
cpufeatures.h currently defines X86_BUG(9) twice on 32-bit:
#define X86_BUG_NULL_SEGX86_BUG(9) /* Nulling a selector
preserves the base */
...
#ifdef CONFIG_X86_32
#define X86_BUG_ESPFIX
The chip->ds and ds->slave_mii_bus assignments are common to both legacy
and new MDIO probing and are already done in the later setup code.
Remove the duplicated assignments from the MDIO probing code.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx.c | 3 -
The chip smi_mutex mutex is used to protect the access to the internal
switch registers, not only the Multi-chip Addressing Mode, as commented.
Other registers access (like management frames) may use this mutex.
Since we will isolate SMI-specific pieces of code, avoid the confusion
now by renamin
This patch fixes 5 style problems reported by checkpatch:
WARNING: suspect code indent for conditional statements (8, 24)
#492: FILE: drivers/net/dsa/mv88e6xxx.c:492:
+ if (phydev->link)
+ reg |= PORT_PCS_CTRL_LINK_UP;
CHECK: Logical continuations should be
The switch ID is located at address 0x3 of every Port Registers bank.
But not all Marvell switches have their Port Registers SMI Addresses
starting at 0x10. 88E6060 starts at 0x8 and 88E6390 starts at 0x0.
Add this data in the info structure and use it in the detection code.
Signed-off-by: Vivie
The mv88e6xxx_table array and the mv88e6xxx_lookup_info function are
static, so remove the table and size arguments from the lookup function.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/driver
Add an helper function to isolate SMI specific assignations and checks.
This function will later help choosing the different SMI accesses based
of the compatible info.
Since the chip structure is already allocated in the legacy probe, use
the mv88e6xxx_reg_read access routine instead of __mv88e6x
Use the optional variant to get the reset GPIO line, instead of checking
for the -ENOENT error.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/net/dsa/mv88e6xxx.c b/drivers/net/dsa/mv88e6xxx
This patchset factorizes the legacy DSA probing and the new MDIO probing
functions with a few helpers.
This will allow us to use a compatible chip info to describe how to access the
SMI device and its switch ID register at probe time.
For the legacy probe, we fix the compatible info to 88E6085. F
From: Dave Hansen
cpufeatures.h currently defines X86_BUG(9) twice on 32-bit:
#define X86_BUG_NULL_SEGX86_BUG(9) /* Nulling a selector
preserves the base */
...
#ifdef CONFIG_X86_32
#define X86_BUG_ESPFIX X86_BUG(9) /* "" IRET to 16-bit SS
corr
The MDIO device probe and remove functions are respectively incrementing
and decrementing the bus refcount themselves. Since these bus level
actions are out of the device scope, remove them.
Signed-off-by: Vivien Didelot
Acked-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx.c | 3 ---
1 file chan
On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> vhost driver relies on copy_from_user/get_user from a kernel thread.
> This makes it impossible to reap the memory of an oom victim which
> shares mm with the vhost kernel thread because it could see a zero
> p
When the SMI address of the switch chip is zero, the chip assumes to be
the only one on the SMI master bus and thus responds to all its known
SMI devices addresses (port registers, Global2, etc.)
When its SMI address is not zero, some chips (e.g. 88E6352) use an
indirect access through two SMI Com
The mixed assignments, allocations and registrations in the probe code
make it hard to follow the logic and figure out what is DSA or chip
specific.
Extract the struct dsa_switch related code in a simple
mv88e6xxx_register_switch helper function.
For symmetry in the code, add a mv88e6xxx_unregist
This series enables aarch64 with ilp32 mode, and as supporting work,
introduces ARCH_32BIT_OFF_T configuration option that is enabled for
existing 32-bit architectures but disabled for new arches (so 64-bit
off_t is is used by new userspace).
This version is based on kernel v4.7-rc3.
It works with
Add an helper function to allocate the chip structure at the beginning
of the probe functions. It will be used to initialize the SMI access.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx.c | 39 +++
1 file changed, 27 insertions(+), 12 deletions(
Extract the common detection code which assigns the info structure to
the chip given the read switch ID.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6xxx.c | 64 +
1 file changed, 30 insertions(+), 34 deletions(-)
diff --git a/drivers/net/d
In the MDIO probing function, dev is already assigned to &mdiodev->dev
and np is already assigned to mdiodev->dev.of_node, so use them.
Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
1 - 100 of 981 matches
Mail list logo
