Changed 'Medfile' to 'Medfield' in Kconfig
Signed-off-by: Joseph Kogut
---
drivers/tty/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index d2501f0..7baf98c 100644
--- a/drivers/tty/serial/Kconfig
+++
Refer to 'r' later.
So don't put in clk_add_alias.
Signed-off-by: Yoshinori Sato
---
drivers/clk/clkdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clkdev.c b/drivers/clk/clkdev.c
index 043fd36..fddb999 100644
--- a/drivers/clk/clkdev.c
+++
My apologies, please disregard this patch. It seems my tree wasn't
clean, and another change snuck its way in.
On Sun, Mar 1, 2015 at 12:39 AM, Joseph Kogut wrote:
> Change 'Medfile' to 'Medfield'
>
> Signed-off-by: Joseph Kogut
> ---
> drivers/tty/serial/Kconfig | 2 +-
>
Change 'Medfile' to 'Medfield'
Signed-off-by: Joseph Kogut
---
drivers/tty/serial/Kconfig | 2 +-
drivers/tty/serial/mfd.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index d2501f0..7baf98c 100644
---
Now that QEmu reuses linux virtio headers, we noticed
a typo in the exported virtio block header. Fix it up.
I'd like these merged for 4.0 so that Qemu 2.3 can
alredy get it right.
Michael S. Tsirkin (2):
virtio_blk: typo fix
virtio_blk: fix comment for virtio 1.0
Fix up comment to match virtio 1.0 logic:
virtio_blk_outhdr isn't the first elements anymore,
the only requirement is that it comes first in
the s/g list.
Signed-off-by: Michael S. Tsirkin
---
include/uapi/linux/virtio_blk.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Now that QEmu reuses linux virtio headers, we noticed
a typo in the exported virtio block header. Fix it up.
Signed-off-by: Michael S. Tsirkin
---
include/uapi/linux/virtio_blk.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/virtio_blk.h
Hi Heiko:
On 2015年03月01日 01:57, Heiko Stübner wrote:
Hi Andy,
Am Freitag, 27. Februar 2015, 19:03:03 schrieb Andy Yan:
PopMetal is a rockchip rk3288 based board made by ChipSpark,
which has many interface such as VGA,HDMI,usb,ir,sdcad and
lots of sensors such as
On Sat, Feb 28, 2015 at 10:08 PM, Linus Torvalds
wrote:
>
> I'll see how painful it is to bisect it,
Not surprisingly, it went right for the drm merge.
Commit 8c334ce8f0fe ("Merge branch 'timers-core-for-linus'..") is
good, while the next merge commit 796e1c55717e ("Merge branch
'drm-next' ..")
Hi Heiko:
On 2015年03月01日 01:43, Heiko Stübner wrote:
Hi Andy,
Am Freitag, 27. Februar 2015, 18:59:01 schrieb Andy Yan:
PopMetal board is a rk3288 based board made by ChipSpark,
this patch add root compatible property for it
Signed-off-by: Andy Yan
---
Assalamualaikum w.r.t
Azmin punyalah ingat, selepas dia terjun longkang, tangkap lori hantu, buat
gotong royong, cuci
pakaian orang - dia sudah boleh lonjak diri sebagai Ketua Pembangkang.
Rupa-rupanya, DAP
masih tak percaya dengan Azmin.
Apa punca DAP benci dan tak percaya kepada Azmin? Sebab
Program management descriptor's access mode according to the
dynamically detected CPU endianness.
Signed-off-by: Arun Chandran
Acked-by: Nicolas Ferre
Tested-by: Michal Simek
---
* Adding CPU endianness detection according to Michal Simek
* Added Acked-by: Nicolas Ferre
* Added Tested-by:
Add *_SIZE macros for the bits ENDIA_DESC and
ENDIA_PKT
Signed-off-by: Arun Chandran
Acked-by: Nicolas Ferre
---
* Correct these macros according to comments from Nicolas Ferre. Also add his
Acked-by
---
---
drivers/net/ethernet/cadence/macb.h | 3 ++-
1 file changed, 2 insertions(+), 1
On Sat, Feb 28, 2015 at 9:40 PM, Linus Torvalds
wrote:
>
> I'm not sure how new these problems are, I think the previous kernel I
> booted on this machine was 3.16.
Hmm. 3.19 works fine, even if it ends up spewing
WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/drm_irq.c:1121
This patch fix following warning while make xmldocs.
Warning(.//include/drm/drm_crtc.h:1016): Excess struct/union/enum/typedef
member 'num_bridges' description in 'drm_mode_group'
Signed-off-by: Masanari Iida
---
include/drm/drm_crtc.h | 1 -
1 file changed, 1 deletion(-)
diff --git
Hmm. I haven't updated the old Mac Mini I have in a *long* time, but
today I decided to try.
And it causes problems in drm.
I'm not sure how new these problems are, I think the previous kernel I
booted on this machine was 3.16. But I thought I'd better report them
as-is, because bisection on
On Fri, 2015-02-27 at 17:57 +0100, Sebastian Andrzej Siewior wrote:
> The "usual" path is:
> - rt_mutex_slowlock()
> - set_current_state()
> - task_blocks_on_rt_mutex() (ret 0)
> - __rt_mutex_slowlock()
>- sleep or not but do return with __set_current_state(TASK_RUNNING)
> - back to
From: Jaedon Shin
Date: Sat, 28 Feb 2015 11:48:26 +0900
> This patch adds bcmgenet_tx_poll for the tx_rings. This can reduce the
> interrupt load and send xmit in network stack on time. This also
> separated for the completion of tx_ring16 from bcmgenet_poll.
>
> The bcmgenet_tx_reclaim of
From: Geert Uytterhoeven
Date: Fri, 27 Feb 2015 17:16:26 +0100
> Commit 740c7f31c094703c ("sh_eth: Ensure DMA engines are stopped before
> freeing buffers") added a call to sh_eth_reset() to the
> sh_eth_set_ringparam() and sh_eth_close() paths.
>
> However, setting the software reset bit(s) in
On Feb 28, 2015 2:50 PM, "Tejun Heo" wrote:
>
> On Sat, Feb 28, 2015 at 02:26:58PM -0800, Tim Hockin wrote:
> > Wow, so much anger. I'm not even sure how to respond, so I'll just
> > say this and sign off. All I want is a better, friendlier, more
> > useful system overall. We clearly have
On Thu, Feb 26, 2015 at 04:14:33PM -0600, Christoph Lameter wrote:
>
> V1->V2:
> - Fix up the processing of the caps bits after discussions
>with Any and Serge. Make patch less intrusive.
>
> Ambient caps are something like restricted root privileges.
> A process has a set of additional
Allows for packet parsing to be done by the fast path. This performance
optimization already exists for IPv4. Add similar logic for IPv6.
Signed-off-by: Amitabha Banerjee
Signed-off-by: Shrikrishna Khare
---
drivers/net/vmxnet3/vmxnet3_drv.c | 29 -
On Sat, Feb 28, 2015 at 02:53:30PM -0500, Mike Frysinger wrote:
> This file is largely UTF-8 except for this one entry which is ISO-8859-1.
> By mixing the encodings, grep thinks the file is binary.
>
> Signed-off-by: Mike Frysinger
Acked-by: Greg Kroah-Hartman
--
To unsubscribe from this
On Sat, 2015-02-28 at 16:41 -0800, Linus Torvalds wrote:
> On Sat, Feb 28, 2015 at 3:02 PM, Benjamin Herrenschmidt
> wrote:
> >
> > Anyway, here's the current patch:
>
> Ok, I think I like this approach better.
>
> Your FAULT_FLAG_EXEC handling is wrong, though. It shouldn't check
> VM_WRITE,
According to [1], Windows Precision Touchpad devices must supply
a button type usage in the device capabilities feature report. A
value of 0 indicates that the device contains a depressible
button (i.e. it's a click-pad) whereas a value of 1 indicates
a non-depressible button. Add support for this
On Sat, 28 Feb 2015, Sergei Shtylyov wrote:
> Hello.
>
> On 02/28/2015 10:58 PM, Shrikrishna Khare wrote:
>
> > Allows for packet parsing to be done by the fast path. This performance
> > optimization already exists for IPv4. Add similar logic for IPv6.
>
> > Signed-off-by: Amitabha Banerjee
Required properties:
- compatible: platform specific
- i2s-controller: the i2s controller device node
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3:
- modify cpu-of-node to i2s-controller
Changes in v2:
- remove codec-name and codec-dai-name
- rename
Add a sound driver that combines rockchip-i2s cpu_dai and dw-hdmi-codec
as codec_dai to provide hdmi audio output on rk3288 platforms.
Signed-off-by: Yakir Yang
---
Changes in v4:
- Add ".pm = _soc_pm_ops,"
Changes in v3:
- Delete the operation of jack in rockchip-hdmi-audio driver,
get ready
codec driver creat an standard alsa device, than config audio
and report jack status through some callback interfaces that
dw_hdmi driver support.
Signed-off-by: Yakir Yang
---
Changes in v4:
- Replace delaywork with irq thread, and add suspend/resume interfaces,
Replace "dw-hdmi-audio" with
creat dw-hdmi-audio device dynamically in probe function,
and transfer some interfaces to dw-hdmi-audio driver for
setting hdmi audio format & control hdmi audio clock.
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3:
- Remove audio_config & get_connect_status callback functions
Add enable and disable callbacks to dw_hdmi_audio interface so that
dw_hdmi_audio can enable and disable the dw_hdmi audio.
Signed-off-by: Yakir Yang
---
Changes in v4:
- Rename "hdmi_audio_*" to "dw_hdmi_audio_*"
Changes in v3:
- Delete hdmi_audio_config interface and modify audio clock
From: Daniel Kurtz
When transmitting IEC60985 linear PCM audio, we configure the
Audio Sample Channel Status information of all the channel
status bits in the IEC60958 frame.
Signed-off-by: Yakir Yang
---
Changes in v4:
- Give HDMI_FC_AUD_SCHNL8 an readable value
Changes in v3:
- Determine
If the monitor support audio, so we should support audio for it, even if
the display resolution is No-CEA mode.
Signed-off-by: Yakir Yang
---
Changes in v4:
- Add hdmi audio support when monitor support audio
Changes in v3: None
Changes in v2:
- Enable audio support for No-CEA display mode
Add more n/cts values, in that case we can support audio for more
display resolutions (128 * SampleRate = PixelClock * N / CTS).
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- add more n/cts combinations for more display resolutions
From: Daniel Kurtz
The ncts_atomic_write & cts_manual bits are present when design id
equal to 0x20.
After setting ncts_atomic_write, new N and CTS values are only used when
aud_n1 register is updated.
After setting cts_manual, new CTS value can set by AUD_CTS registers.
Signed-off-by: Yakir
From: Daniel Kurtz
This patch changes the order to:
- write CTS3 CTS_manual (if supported) | N_shift | CTS[19:16]
- write CTS2 CTS[15:8]
- write CTS1 CTS[7:0]
- write N3 N[19:16]
- write N2 N[15:8]
- write N1 N[7:0]
Signed-off-by: Yakir Yang
Signed-off-by: Daniel Kurtz
---
Changes in v4:
-
On Sat, Feb 28, 2015 at 6:17 PM, Yinghai Lu wrote:
> We should access variable with referrence instead of using physical
> address as value.
>
> Cc: Matt Fleming
> Cc: Borislav Petkov
> Signed-off-by: Yinghai Lu
> ---
> arch/x86/kernel/setup.c | 8 +++-
> 1 file changed, 7 insertions(+),
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3:
- Combine hdmi_set_clock_regenerator_n() and hdmi_regenerate_cts()
Changes in v2: None
drivers/gpu/drm/bridge/dw_hdmi.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git
By parsing the identification registers we can know what functions
are present on the hdmi ip.
Signed-off-by: Yakir Yang
---
Changes in v4:
-Correct phy_type assignment bug
Changes in v3:
- Add ID registers parse and record
Changes in v2: None
drivers/gpu/drm/bridge/dw_hdmi.c | 59
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3:
- Setting the .pm member instead of suspend/resume
Changes in v2:
- Add suspend/resume support for dw_hdmi_rockchip driver
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 16
1 file changed, 16 insertions(+)
diff
Hi Suzuki,
On 27.02.2015 12:40, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose"
>
> With FAN_ONDIR set, the user can end up getting events, which
> it hasn't marked. This was revealed with fanotify04 testcase
> failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
> with commit
Wrap irq control in functions, and then we can call in
dw_hdmi_bind/dw_hdmi_unbind/dw_hdmi_resume/dw_hdmi_suspend
functions.
Signed-off-by: Yakir Yang
---
Changes in v4: None
Changes in v3:
- Wrap irq control in fucntions
Changes in v2: None
drivers/gpu/drm/bridge/dw_hdmi.c | 75
the copy will be in __initdata, and it is small.
We can use pointer to access the setup_data instead of keeping on
early_memmap and early_memunmap everywhere.
Cc: Matt Fleming
Cc: linux-...@vger.kernel.org
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/efi.h | 2 +-
when kernel enter into suspend, cpus will shutdown, hdmi registers
will reset invisibly. After kernel resume, drm core will call the
bridge enable function. All of hdmi registers will be setup again
except the interrupt registers. In that case we should mute all the
interrupt in suspend stage, and
So we could avoid ioremap every time later.
Cc: Bjorn Helgaas
Cc: linux-...@vger.kernel.org
Signed-off-by: Yinghai Lu
---
arch/x86/pci/common.c | 77 +--
1 file changed, 63 insertions(+), 14 deletions(-)
diff --git a/arch/x86/pci/common.c
So we could let kexec-tools to rebuild SETUP_PCI and pass it to
second kernel.
Now kexec-tools only can build SETUP_EFI and SETUP_E820EXT.
Cc: Bjorn Helgaas
Cc: linux-...@vger.kernel.org
Signed-off-by: Yinghai Lu
---
arch/x86/pci/common.c | 188
Let it reserve setup_data, and keep it's own list.
Also clear the hdr.setup_data, as all handler will handle or
reserve setup_data locally already.
Cc: Bjorn Helgaas
Cc: Matt Fleming
Cc: linux-...@vger.kernel.org
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/pci.h | 2 ++
We will not reserve setup_data in general code. Every handler
need to reserve and copy.
Current dtd handling already have code copying, just add reserve code ...
also simplify code a bit with storing real dtb size.
Cc: Rob Herring
Cc: David Vrabel
Signed-off-by: Yinghai Lu
---
Now we are using memblock to do early resource reserver/allocation
instead of using e820 map directly, and setup_data is reserved in
memblock early already.
Also kexec will generate setup_data and pass pointer to second kernel,
so second kernel will reserve setup_data by their own.
We can kill
Cc: Matt Fleming
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/kdebugfs.c | 142 -
arch/x86/kernel/setup.c| 17 --
2 files changed, 159 deletions(-)
diff --git a/arch/x86/kernel/kdebugfs.c b/arch/x86/kernel/kdebugfs.c
index dc1404b..c8ca86c
Now we setup_data is reserved via memblock and e820 and different
handlers have different ways, and it is confusing.
1. SETUP_E820_EXT: is consumed early and will not copy or access again.
have memory wasted.
2. SETUP_EFI: is accessed via ioremap every time at early stage.
have
We should access variable with referrence instead of using physical
address as value.
Cc: Matt Fleming
Cc: Borislav Petkov
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/setup.c
On Sun, Mar 01, 2015 at 04:48:22AM +0300, ??? ??? wrote:
> Hi everyone
>
> 28.02.2015, 23:18, "David Fries" :
> > Thanks for preparing the patch, it looks like it will go another
> > round, but that happens to everyone.
>
> Patch itself doesn't solve the problem, it only adds a
We found Designware hdmi driver only support audio clock config, we can not
play sound through it.
To add Designware HDMI Audio support, we make those patch set:
1): fixed dw_hdmi irq bug, add irq control to suspend/resume interfaces.
2): add suspend/resume callback for dw_hdmi rockchip driver.
Hi Dan
20.02.2015, 13:53, "Dan Carpenter" :
> "sl->family->fops" and "fops" are the same thing, but it's nicer to use
> "fops" everywhere.
>
> Signed-off-by: Dan Carpenter
Looks good to me, thank you
Acked-by: Evgeniy Polyakov
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
> index
On Sat, Feb 28, 2015 at 3:02 PM, Benjamin Herrenschmidt
wrote:
>
> Anyway, here's the current patch:
Ok, I think I like this approach better.
Your FAULT_FLAG_EXEC handling is wrong, though. It shouldn't check
VM_WRITE, it should check VM_EXEC. A bit too much copy-paste ;)
Btw, it's quite
Enhances driver to use an MSI interrupt when available.
Adds the module option 'enable_msi' (type bool) which by default is
enabled. Can be set to 'N' to disable.
Fixes (or can reduce the occurrence of) a crash which is most commonly
reported when multiple saa7164 chips are in use. A reported
On Saturday, February 28, 2015 10:35:21 AM Prakash Punnoor wrote:
> This is a multi-part message in MIME format.
> --080704070901080904040008
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 7bit
>
> Hallo,
>
> my system won't boot with current GIT kernel (see
On Saturday, February 28, 2015 11:54:23 AM Lorenzo Pieralisi wrote:
> On Fri, Feb 27, 2015 at 10:11:54PM +, Rafael J. Wysocki wrote:
> > On Friday, February 27, 2015 10:00:00 AM Lorenzo Pieralisi wrote:
> > > [CC'ed Preeti]
> > >
> > > On Thu, Feb 26, 2015 at 11:37:54PM +, Rafael J.
On Sat, Feb 28, 2015 at 10:45:33PM +0100, Peter Zijlstra wrote:
> On Sat, Feb 28, 2015 at 09:36:15PM +0100, Manfred Spraul wrote:
> > +/*
> > + * Place this after a control barrier (such as e.g. a spin_unlock_wait())
> > + * to ensure that reads cannot be moved ahead of the control_barrier.
> > +
On Sat, Feb 28, 2015 at 05:56:54PM +0100, Peter Zijlstra wrote:
> On Sat, Feb 28, 2015 at 05:41:12PM +0100, Peter Zijlstra wrote:
> > > > > + rb_link_node(>node, parent, link);
> > > >
> > > > This makes the new module visible to readers, if I understand correctly.
> > >
> > > You do.
> >
>
On Fri, Feb 27, 2015 at 11:01:14AM +0100, Peter Zijlstra wrote:
> On Thu, Feb 26, 2015 at 11:41:44AM -0800, Paul E. McKenney wrote:
> > > As per the above argument; without doing the whole READ/WRITE_ONCE for
> > > the rb tree primitives, I think we're fine. We don't actually need the
> > >
On Sat, Feb 28, 2015 at 02:26:58PM -0800, Tim Hockin wrote:
> On Sat, Feb 28, 2015 at 8:57 AM, Tejun Heo wrote:
> >
> > On Sat, Feb 28, 2015 at 08:48:12AM -0800, Tim Hockin wrote:
> > > I am sorry that real-user problems are not perceived as substantial. This
> > > was/is a real issue for us.
Hello.
On 02/28/2015 10:58 PM, Shrikrishna Khare wrote:
Allows for packet parsing to be done by the fast path. This performance
optimization already exists for IPv4. Add similar logic for IPv6.
Signed-off-by: Amitabha Banerjee
Signed-off-by: Shrikrishna Khare
---
On 28/02/2015 at 13:22:54 -0800, Joe Perches wrote :
> My thought was that it might be better to
> use a local struct rtc_time r like
>
> r.tm_sec = bcd2bin(date[AB08XX_REG_SC] & 0x7F);
> r.tm_min = bcd2bin(date[AB08XX_REG_MN] & 0x7F);
> r.tm_hour = bcd2bin(date[AB08XX_REG_HR] &
On Sun, 2015-03-01 at 09:16 +1100, Benjamin Herrenschmidt wrote:
> So for error handling, I'm trying to simply return the VM_FAULT_* flags
> from generic_page_fault see where that takes us. That's a way to avoid
> passing an arch specific struct around. It also allows my hack to
> account major
On Sat, Feb 28, 2015 at 08:49:27AM +0100, Ingo Molnar wrote:
SNIP
>
> 0695e57b9a6a perf tools: Factor features display code
>
> Firstly, 'factor' isn't a verb we use for code, 'factor out' is. But
> it's not really factoring out - it separates the code. Did this title
> want to say:
>
>
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:19 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > -Original Message-
> > From:
On Sat, Feb 28, 2015 at 02:26:58PM -0800, Tim Hockin wrote:
> Wow, so much anger. I'm not even sure how to respond, so I'll just
> say this and sign off. All I want is a better, friendlier, more
> useful system overall. We clearly have different ways of looking at
> the problem.
Can you
On Sun, 2015-03-01 at 09:16 +1100, Benjamin Herrenschmidt wrote:
> So for error handling, I'm trying to simply return the VM_FAULT_* flags
> from generic_page_fault see where that takes us. That's a way to avoid
> passing an arch specific struct around. It also allows my hack to
> account major
On Sat, 2015-02-28 at 13:49 -0800, Linus Torvalds wrote:
.../...
> - we handle write faults separately (see the first part of access_error()
>
> - so now we know it was a read or an instruction fetch
>
> - if PF_PROT is set, that means that the present bit was set in the
> page tables, so
On Sat, Feb 28, 2015 at 8:57 AM, Tejun Heo wrote:
>
> On Sat, Feb 28, 2015 at 08:48:12AM -0800, Tim Hockin wrote:
> > I am sorry that real-user problems are not perceived as substantial. This
> > was/is a real issue for us. Being in limbo for years on end might not be a
> > technical point, but
On Thu, Feb 12, 2015 at 12:33:09AM -0500, Vince Weaver wrote:
>
> This manpage patch relates to the addition of PERF_SAMPLE_REGS_INTR
> support added in the following commit:
hi,
sorry for late response..
>
> perf_sample_regs_intr; Linux 3.19
> commit
From: Colin Ian King
Fix spelling mistake, "aquire" -> "acquire" and missing newline (as
spotted by Joe Perches.
Signed-off-by: Colin Ian King
---
drivers/dma/s3c24xx-dma.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/s3c24xx-dma.c
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 10:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > -Original Message-
> > From:
So for error handling, I'm trying to simply return the VM_FAULT_* flags
from generic_page_fault see where that takes us. That's a way to avoid
passing an arch specific struct around. It also allows my hack to
account major faults with the hypervisor to be done outside the generic
code completely
On Sat, Feb 28, 2015 at 02:10:22PM -0800, Dmitry Torokhov wrote:
> Hi Scott,
>
> On Sat, Feb 28, 2015 at 08:35:57AM -0800, Scott Branden wrote:
> > + /* Enable clock */
> > +
> > + kp->clk = devm_clk_get(>dev, "peri_clk");
> > + if (IS_ERR(kp->clk)) {
> > + dev_info(>dev,
> > +
Hi Scott,
On Sat, Feb 28, 2015 at 08:35:57AM -0800, Scott Branden wrote:
> + /* Enable clock */
> +
> + kp->clk = devm_clk_get(>dev, "peri_clk");
> + if (IS_ERR(kp->clk)) {
> + dev_info(>dev,
> + "No clock specified. Assuming it's enabled\n");
I was
On 28 Feb, Chris Wilson wrote:
> On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote:
> > Unfortunately this is not the last bug, that breaks i915/drm working
> > on my laptop. Sometimes system successfully loads with couple warnings
> > mentioned in
> > previous mail:
> >
> > [
From: Andrew Schwartzmeyer
Date: Thu, 26 Feb 2015 16:27:14 -0800
> This adds support for reporting the actual and maximum combined channels
> count of the hv_netvsc driver via 'ethtool --show-channels'.
>
> This required adding 'max_chn' to 'struct netvsc_device', and assigning
> it
On Sat, Feb 28, 2015 at 1:14 PM, Benjamin Herrenschmidt
wrote:
>
> BTW. I fail to see how x86 checks PF_INSTR vs. VM_NOEXEC ... or it doesn't ?
It doesn't. x86 traditionally doesn't have an execute bit, so
traditionally "read == exec".
So PF_INSTR really wasn't historically very useful, in that
On Sat, Feb 28, 2015 at 09:36:15PM +0100, Manfred Spraul wrote:
> +/*
> + * Place this after a control barrier (such as e.g. a spin_unlock_wait())
> + * to ensure that reads cannot be moved ahead of the control_barrier.
> + * Writes do not need a barrier, they are not speculated and thus cannot
>
Change the insert and erase code such that lockless searches are
non-fatal.
In and of itself an rbtree cannot be correctly searched while
in-modification, we can however provide weaker guarantees that will
allow the rbtree to be used in conjunction with other techniques, such
as latches; see
Use the generic __module_address() addr to struct module lookup
instead of open coding it once more.
Cc: Rusty Russell
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/module.c | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
--- a/kernel/module.c
+++
Implement a latched RB-tree in order to get RCU style lookups.
Cc: Michel Lespinasse
Cc: Andrea Arcangeli
Cc: David Woodhouse
Cc: Rik van Riel
Cc: Mathieu Desnoyers
Cc: "Paul E. McKenney"
Cc: Oleg Nesterov
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/rbtree_latch.h | 140
This series is aimed at making __module_address() go fast(er).
On the way there it:
- annotates and sanitizes module locking
- introduces the latched RB-tree
- employs it to make __module_address() go fast
I've build and boot tested this on x86_64 with modules and lockdep enabled.
--
To
While one must hold RCU-sched (aka. preempt_disable) for find_symbol()
one must equally hold it over the use of the object returned.
The moment you release the RCU-sched read lock, the object can be dead
and gone.
Cc: Seth Jennings
Cc: Josh Poimboeuf
Cc: Masami Hiramatsu
Cc: Miroslav Benes
Improve the documentation of the latch technique as used in the
current timekeeping code, such that it can be readily employed
elsewhere.
Borrow from the comments in timekeeping and replace those with a
reference to this more generic comment.
Cc: Oleg Nesterov
Cc: Michel Lespinasse
Cc: Andrea
Currently __module_address() is using a linear search through all
modules in order to find the module corresponding to the provided
address. With a lot of modules this can take a lot of time.
One of the users of this is kernel_text_address() which is employed
in many stack unwinders; which in
As per the module core lockdep annotations:
[ 18.034047] ---[ end trace 9294429076a9c673 ]---
[ 18.047760] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS
SE5C600.86B.02.02.0002.122320131210 12/23/2013
[ 18.059228] 817d8676 880036683c38 8157e98b
Due to the new lockdep checks we go:
[9.759380] [ cut here ]
[9.759389] WARNING: CPU: 31 PID: 597 at ../kernel/module.c:216
each_symbol_section+0x121/0x130()
[9.759391] Modules linked in:
[9.759393] CPU: 31 PID: 597 Comm: modprobe Not tainted 4.0.0-rc1+
Currently the RCU usage in module is an inconsistent mess of RCU and
RCU-sched, this is broken for CONFIG_PREEMPT where synchronize_rcu()
does not imply synchronize_sched().
Convert everything over to RCU-sched.
Furthermore add lockdep asserts to all sites, because its not at all
clear to me the
On Sat, Feb 28, 2015 at 05:25:57PM +0300, Alexey Dobriyan wrote:
> Freezing and thawing are separate system calls, task which is supposed
> to thaw filesystem/superblock can disappear due to crash or not thaw
> due to a bug. At least record task name (we can't take task_struct
> reference) to make
On Sat, 2015-02-28 at 20:14 +, Colin King wrote:
> Fix spelling mistake, "aquire" -> "acquire"
trivia:
> diff --git a/drivers/dma/s3c24xx-dma.c b/drivers/dma/s3c24xx-dma.c
[]
> @@ -1266,7 +1266,7 @@ static int s3c24xx_dma_probe(struct platform_device
> *pdev)
>
On Sat, 2015-02-28 at 21:52 +0100, Alexandre Belloni wrote:
> > > diff --git a/drivers/rtc/rtc-abx80x.c b/drivers/rtc/rtc-abx80x.c
> > []
> > > +static int ab08xx_get_datetime(struct i2c_client *client, struct
> > > rtc_time *tm)
[]
> > > + tm->tm_sec = bcd2bin(date[AB08XX_REG_SC] & 0x7F);
> > >
On Sat, 2015-02-28 at 11:56 -0800, Linus Torvalds wrote:
> On Fri, Feb 27, 2015 at 11:12 PM, Benjamin Herrenschmidt
> wrote:
> >
> > Let me know what you think of the approach.
>
> Hmm. I'm not happy with just how many of those arch wrapper/helper
> functions there are, and some of it looks a
On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote:
> Unfortunately this is not the last bug, that breaks i915/drm working
> on my laptop. Sometimes system successfully loads with couple warnings
> mentioned in
> previous mail:
>
> [ 26.922953] WARNING: CPU: 1 PID: 767 at
>
Without this change file name for hmc5843 is empty in
/sys/bus/iio/devices/iio\:device*/name
With this change name is reported correctly:
cat /sys/bus/iio/devices/iio\:device*/name
hmc5843
Signed-off-by: Marek Belisko
---
drivers/staging/iio/magnetometer/hmc5843_core.c | 1 +
1 file changed, 1
On 28/02/2015 at 11:32:15 -0800, Joe Perches wrote :
> On Sat, 2015-02-28 at 20:14 +0100, Alexandre Belloni wrote:
> > Add support for the i2c RTC from Abracon.
>
> Perhaps you can run this through
> $ ./scripts/checkpatch.pl --strict --fix-inplace
>
Right, I'll fix those
> Is there going to
From: Colin Ian King
Fix typo, "flaged" -> "flagged"
Signed-off-by: Colin Ian King
---
drivers/pinctrl/sirf/pinctrl-sirf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/sirf/pinctrl-sirf.c
b/drivers/pinctrl/sirf/pinctrl-sirf.c
index 2a1f072..abc5c47
1 - 100 of 608 matches
Mail list logo
