From: Len Brown
The Intel Denverton microserver uses a 25 MHz TSC crystal,
so we can derive its exact * TSC frequency
using CPUID and some arithmetic, eg.
TSC: 1800 MHz (2500 Hz * 216 / 3 / 100)
* 'exact' is only as good as the crystal, which should be +/- 20ppm
Signed-off-by: Len Brow
Hi Sylwester,
2017-01-21 16:42 GMT+09:00 Sylwester Nawrocki :
> Hi Chanwoo,
>
> On 01/21/2017 06:08 AM, Chanwoo Choi wrote:
>> I add reveiwed-by tag from this patch. But, on you tree, this patch[1]
>> doesn’t
>> include the my reviewed-by tag.
>
> My apologies for this omission, I'll make sure I
Hi Chanwoo,
On 01/21/2017 06:08 AM, Chanwoo Choi wrote:
> I add reveiwed-by tag from this patch. But, on you tree, this patch[1] doesn’t
> include the my reviewed-by tag.
My apologies for this omission, I'll make sure I use patchwork in future
so no tags are lost. It's already pulled and that com
;
+ }
return page;
}
And I got flood of traces shown below. It seems to be consuming memory reserves
until the size passed to write() request is stored to the page cache even after
OOM-killed.
Complete log is at http://I-love.SAKURA.ne.jp/tmp/serial-201701
Hi Viresh,
For devfreq part, Looks good to me.
Reviewed-by: Chanwoo Choi
2016-12-08 13:00 GMT+09:00 Viresh Kumar :
> On 07-12-16, 22:23, Chanwoo Choi wrote:
>> I think that the dev_pm_opp_put(opp) should be called after if statement
>> If dev_pm_opp_find_freq_ceil() return error, I think the c
On Fri, 20 Jan 2017, Michael Schmitz wrote:
> Am 15.01.2017 um 17:42 schrieb Finn Thain:
>
> >> No, we can't check either FDC or SCSI interrupts (or indeed any chip
> >> registers) without touching the ST-DMA. The moment we select a FDC or
> >> SCSI register for read, DMA is terminated no ques
On 01/20/2017, 03:40 PM, tip-bot for Jiri Slaby wrote:
> Commit-ID: bf3304d996fbb993bad6be09cafde39cc2db72bb
> Gitweb: http://git.kernel.org/tip/bf3304d996fbb993bad6be09cafde39cc2db72bb
> Author: Jiri Slaby
> AuthorDate: Thu, 19 Jan 2017 12:47:30 +0100
> Committer: Ingo Molnar
> CommitD
On 2017-01-20 17:19, Steven Rostedt wrote:
On Fri, 20 Jan 2017 10:43:50 +0200
mi...@stz-bg.com wrote:
[1.] One line summary of the problem:
rcu_sched detected stalls on CPUs and few minutes server not respond.
Is this reproducible? Or was this a one time ordeal?
It's happened usual once pe
* Jason Baron wrote:
> >For example the last line could sure be written as:
> >
> > key->entries = jlm->entries;
> > key->type |= static_key_type(key);
> >
> >right?
>
> Hi,
>
> So that is going to over-write the static_key_type(key) in the first
> assig
Declare net_device_ops structure as const as it is only stored in
the netdev_ops field of a net_device structure. This field is of type
const, so net_device_ops structures having same properties can be made
const too.
Done using Coccinelle:
@r1 disable optional_qualifier@
identifier i;
position p;
Declare net_device_ops structure as const as it is only stored in
the netdev_ops field of a net_device structure. This field is of type
const, so net_device_ops structures having same properties can be made
const too.
Done using Coccinelle:
@r1 disable optional_qualifier@
identifier i;
position p;
Hi Markus,
[auto build test ERROR on next-20170119]
[also build test ERROR on v4.10-rc4]
[cannot apply to v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/SF-Markus-Elf
On Sat, Jan 21, 2017 at 01:16:56AM +0100, Jason A. Donenfeld wrote:
> On Sat, Jan 21, 2017 at 1:15 AM, Theodore Ts'o wrote:
> > But there is a shared pointer, which is used both for the dedicated
> > u32 array and the dedicated u64 array. So when you increment the
> > pointer for the get_random_u
Hi Markus,
[auto build test ERROR on next-20170119]
[also build test ERROR on v4.10-rc4]
[cannot apply to v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/SF-Markus-Elf
On Fri, 20 Jan 2017, John Stultz wrote:
> On Fri, Jan 20, 2017 at 2:46 PM, Nicolas Pitre
> wrote:
> > Just tell me if you prefer that I respin the patch and I'll do it.
>
> Yea. I'm not so finicky but I'm sure I'll probably get yelled at if I
> pass it on, so if you don't mind respinning it, I'
Declare net_device_ops structures as const as they are only stored in
the netdev_ops field of a net_device structure. This field is of type
const, so net_device_ops structures having same properties can be made
const too.
Done using Coccinelle:
@r1 disable optional_qualifier@
identifier i;
positio
Declare net_device_ops structures as const as they are only stored in
the netdev_ops field of a net_device structure. This field is of type
const, so net_device_ops structures having same properties can be made
const too.
Done using Coccinelle:
@r1 disable optional_qualifier@
identifier i;
positio
Allow power sequencing for the Marvell SD8787 Wifi/BT chip.
This can be abstracted to other chipsets if needed in the future.
Cc: Tony Lindgren
Cc: Ulf Hansson
Signed-off-by: Matt Ranostay
---
drivers/mmc/core/Kconfig | 10
drivers/mmc/core/Makefile| 1 +
drivers/mmc/co
Cc: devicet...@vger.kernel.org
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/mmc/mmc-pwrseq-sd8787.txt | 14 ++
.../devicetree/bindings/net/wireless/marvell-8xxx.txt | 7 ++-
2 files changed, 20 insertions(+), 1 deletion(-)
create mode 100644 Documentati
Changes from v1:
* split devictree docs from pwrseq changes
* rebase devicetree documents due to filename change
* rebase pwrseq patchset
Changes from v2:
* update device tree bindings to powerdown-gpios and document
active state
Matt Ranostay (2):
devicetree: document new marvell-8xxx and pw
Hi Geliang,
[auto build test ERROR on v4.9-rc8]
[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/Geliang-Tang/nilfs2-use-i_blocksize/20170121-114142
config: x86_64-randconfig-n0-01211226 (attached
Hi Sylwester,
I add reveiwed-by tag from this patch. But, on you tree, this patch[1] doesn’t
include the my reviewed-by tag.
[1]
https://git.linuxtv.org/snawrocki/samsung.git/commit/?h=for-v4.11/clk/next&id=cb4ac949ea14416a2d57b7a343bc4b571074e3bd
2017-01-16 19:32 GMT+09:00 Sylwester Nawrocki :
The issue here is that in orangefs_bufmap_alloc() we do:
bufmap->buffer_index_array =
kzalloc(DIV_ROUND_UP(bufmap->desc_count, BITS_PER_LONG),
GFP_KERNEL);
If we choose a bufmap->desc_count like -31 then it means the
DIV_ROUND_UP ends up having an integer overflow. The
max_key is a value in the 0-63 range, so on 32 bit systems the shift
could wrap.
Signed-off-by: Dan Carpenter
diff --git a/samples/bpf/lwt_len_hist_user.c b/samples/bpf/lwt_len_hist_user.c
index ec8f3bb..bd06eef 100644
--- a/samples/bpf/lwt_len_hist_user.c
+++ b/samples/bpf/lwt_len_hist_user.c
@
On Friday 13 January 2017 03:30 PM, Bartosz Golaszewski wrote:
> The aemif driver can now access struct of_dev_auxdata (using platform
> data).
>
> Add the device id to the clock lookup table for the nand clock and
> create a separate lookup table for aemif subnodes.
>
> Signed-off-by: Bartosz Go
Hi Thomas,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.10-rc4 next-20170120]
[cannot apply to tip/x86/core]
[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/Thomas
Hi Thomas,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.10-rc4 next-20170120]
[cannot apply to tip/x86/core]
[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/Thomas
Patches 1/3 look reasonable to me, though I've not run into the bugs
they aim to fix. For those:
Acked-by: Jason Gerecke
As for patch 4, I have some additional reservations about hiding the
message... We can discuss that further in its thread.
Jason
---
Now instead of four in the eights place /
Hi Thomas,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.10-rc4 next-20170120]
[cannot apply to tip/x86/core]
[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/Thomas
I'm not super comfortable with hiding this error. If the tablet reacts
appropriately, I wouldn't think we'd get an EPIPE. Although its not
fatal, it still might be a symptom of something deeper...
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That i
On Fri, Jan 20, 2017 at 09:13:17PM -0500, Steven Rostedt wrote:
> On Sat, 21 Jan 2017 09:27:06 +0900
> Namhyung Kim wrote:
>
>
> > > Note, I had to modify this patch and move this declaration outside of
> > > the #ifdef CONFIG_FUNCTION_GRAPH_TRACER, as it failed to build when
> > > function grap
In clock driver initialize phase the spinlock is missed to assignment
to struct clkgate_separated, finally there have no locking to protect
exclusive accessing for clock registers.
This bug introduces the console has no output after enable coresight
driver on 96boards Hikey; this is because consol
Hi Thomas,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.10-rc4 next-20170120]
[cannot apply to tip/x86/core]
[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/Thomas
On Fri, Jan 20, 2017 at 02:58:27PM -0800, Stephen Boyd wrote:
> On 01/18, Leo Yan wrote:
> > In clock driver initialize phase the spinlock is missed to assignment
> > to struct clkgate_separated, finally there have no locking to protect
> > exclusive accessing for clock registers.
> >
> > This bug
On Sat, 21 Jan 2017 09:27:06 +0900
Namhyung Kim wrote:
> > Note, I had to modify this patch and move this declaration outside of
> > the #ifdef CONFIG_FUNCTION_GRAPH_TRACER, as it failed to build when
> > function graph wasn't enabled. Function tracer uses this too.
>
> Oops, my bad.
>
> Did
On 01/20/2017 03:14 PM, Jarkko Sakkinen wrote:
On Fri, Jan 20, 2017 at 07:55:22PM +0200, Jarkko Sakkinen wrote:
On Fri, Jan 20, 2017 at 06:21:58PM +0200, Jarkko Sakkinen wrote:
On Fri, Jan 20, 2017 at 03:36:30PM +0200, Jarkko Sakkinen wrote:
On Thu, Jan 19, 2017 at 07:19:12AM -0500, Stefan Ber
Hey Arnaldo,
On Thu, Jan 05, 2017 at 10:23:31PM -0800, Krister Johansen wrote:
> If dso__load_kcore frees all of the existing maps, but one has already
> been attached to a callchain cursor node, then we can get a SIGSEGV in
> any function that happens to try to use this invalid cursor. Use the
>
On Fri, Jan 20, 2017 at 4:57 PM, Andy Lutomirski wrote:
> On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote:
>> Each processor holds a GDT in its per-cpu structure. The sgdt
>> instruction gives the base address of the current GDT. This address can
>> be used to bypass KASLR memory randomizat
On Fri, Jan 20, 2017 at 5:06 PM, Andy Lutomirski wrote:
> On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote:
>> This patch makes the GDT remapped pages read-only to prevent corruption.
>> This change is done only on 64 bit.
>>
>> The native_load_tr_desc function was adapted to correctly handl
On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote:
> This patch makes the GDT remapped pages read-only to prevent corruption.
> This change is done only on 64 bit.
>
> The native_load_tr_desc function was adapted to correctly handle a
> read-only GDT. The LTR instruction always writes to the G
Hi,
On Thu, Jan 12, 2017 at 5:28 PM, Maxime Ripard
wrote:
> On Fri, Dec 09, 2016 at 12:04:08PM +0100, Quentin Schulz wrote:
>> The X-Powers AXP209 and AXP20X PMICs are able to set a limit for the
>> VBUS power supply for both max current and min voltage supplied. This
>> series of patch adds the
From: Sudip Mukherjee
Modify lirc_parallel driver to use the new parallel port device model.
Signed-off-by: Sudip Mukherjee
---
Resending after more than one year.
Prevoius patch is at https://patchwork.kernel.org/patch/7883591/
drivers/staging/media/lirc/lirc_parallel.c | 93 +++
On Fri, Jan 20, 2017 at 8:41 AM, Thomas Garnier wrote:
> Each processor holds a GDT in its per-cpu structure. The sgdt
> instruction gives the base address of the current GDT. This address can
> be used to bypass KASLR memory randomization. With another bug, an
> attacker could target other per-cp
On Fri, Jan 20, 2017 at 8:33 AM, Djalal Harouni wrote:
> On Thu, Jan 19, 2017 at 8:52 PM, Andy Lutomirski wrote:
>> On Thu, Jan 19, 2017 at 5:53 AM, Djalal Harouni wrote:
> [...]
>>> Sure, the hidepid mount option is old enough, and this per-task
>>> hidepid is clearly defined only for procfs an
On 01/18, Markus Mayer wrote:
> diff --git
> a/Documentation/devicetree/bindings/clock/brcm,brcmstb-cpu-clk-div.txt
> b/Documentation/devicetree/bindings/clock/brcm,brcmstb-cpu-clk-div.txt
> new file mode 100644
> index 000..c4acb53
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/cl
On 01/13, Chris Packham wrote:
> @@ -158,6 +170,14 @@ static const struct coreclk_soc_desc axp_coreclks = {
> .num_ratios = ARRAY_SIZE(axp_coreclk_ratios),
> };
>
> +static const struct coreclk_soc_desc mv98dx3236_coreclks = {
> + .get_tclk_freq = mv98dx3236_get_tclk_freq,
> + .get
On 01/09, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> Macro to select a clock was not correct.
>
> Offset of enable register starts at 0x30, then calculation to select a bit is:
> (@enable_reg - 0x30) / 4 * 32 + bit_to_select
>
> Signed-off-by: Gabriel Fernandez
> Tested-by:
On Sat, Jan 21, 2017 at 1:15 AM, Theodore Ts'o wrote:
> But there is a shared pointer, which is used both for the dedicated
> u32 array and the dedicated u64 array. So when you increment the
> pointer for the get_random_u32, the corresponding entry in the u64
> array is wasted, no?
No, it is not
On 01/06, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch enables clocks for STM32F746 boards.
>
> Signed-off-by: Gabriel Fernandez
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Projec
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive:
* A regression fix for the multiple-pmem-namespace-per-region support
added in 4.9. Even if an existing environment is not using that
feature the act of creating and a destroy
On 01/06, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch introduces the stm32f7 clock DT bindings.
>
> Signed-off-by: Gabriel Fernandez
> ---
Applied to clk-stm32f4 because why not
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundat
On 01/20, Geert Uytterhoeven wrote:
> Add optional support for the Reset Control feature of the Renesas Clock
> Pulse Generator / Module Standby and Software Reset module on R-Car
> Gen2, R-Car Gen3, and RZ/G1 SoCs.
>
> This allows to reset SoC devices using the Reset Controller API.
>
> Signed-o
Nikolay Borisov writes:
> On 20.01.2017 20:05, Eric W. Biederman wrote:
>> Nikolay Borisov writes:
>>
>>> On 20.01.2017 15:07, Dmitry Vyukov wrote:
Hello,
I've got the following deadlock report while running syzkaller fuzzer
on eec0d3d065bfcdf9cd5f56dd2a36b94d12d32297 of lin
On 01/20, Geert Uytterhoeven wrote:
> The spinlock is used to protect Read-Modify-Write register accesses,
> which won't be limited to SMSTPCR register accesses.
>
> Signed-off-by: Geert Uytterhoeven
> ---
Acked-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora F
On 01/20, Geert Uytterhoeven wrote:
> The Renesas CPG/MSSR driver is already in active use for RZ/G1 since
> commits c0b2d75d2a4bf6a3 ("clk: renesas: cpg-mssr: Add R8A7743 support")
> and 9127d54bb8947159 ("clk: renesas: cpg-mssr: Add R8A7745 support").
>
> Signed-off-by: Geert Uytterhoeven
> ---
On 01/20, Geert Uytterhoeven wrote:
> Document properties needed to use the Reset Control feature of the
> Renesas Clock Pulse Generator / Module Standby and Software Reset
> module.
>
> Signed-off-by: Geert Uytterhoeven
Subject should be "dt-bindings: clock:" ?
--
Qualcomm Innovation Center
On 01/18, Eric Anholt wrote:
> This proved incredibly useful during debugging of the DSI driver, to
> see if our clocks were running at rate we requested. Let's leave it
> here for the next person interacting with clocks on the platform (and
> so that hopefully we can just hook it up to debugfs so
On 01/18, Eric Anholt wrote:
> The DSI pixel clocks are muxed from clocks generated in the analog phy
> by the DSI driver. In order to set them as parents, we need to do the
> same name lookup dance on them as we do for our root oscillator.
>
> Signed-off-by: Eric Anholt
> ---
Applied to clk-ne
On 01/18, Eric Anholt wrote:
> Our core PLLs are intended to be configured once and left alone. With
> the SET_RATE_PARENT, asking to set the PLLD_DSI1 clock rate would
> change PLLD just to get closer to the requested DSI clock, thus
> changing PLLD_PER, the UART and ethernet PHY clock rates down
On 01/18, Masahiro Yamada wrote:
> Do not let the entire probe function fail even if some clocks fail
> to register. Let's continue with succeeded clocks. This will give
> the system more chances to boot and allow us to investigate the
> cause of the failure.
>
> Signed-off-by: Masahiro Yamada
On Jan 20, 5:22pm, Boris Ostrovsky wrote:
} Subject: Re: [PATCH] tpm: Restore functionality to xen vtpm driver.
> On 01/20/2017 10:00 AM, Dr. Greg Wettstein wrote:
> > Functionality of the xen-tpmfront driver was lost secondary to
> > the introduction of xenbus multi-page support in the following
On Fri, Jan 20, 2017 at 02:54:20PM -0500, Steven Rostedt wrote:
> On Fri, 20 Jan 2017 11:44:46 +0900
> Namhyung Kim wrote:
>
>
> > --- a/kernel/trace/trace.h
> > +++ b/kernel/trace/trace.h
> > @@ -787,6 +787,20 @@ extern void __trace_graph_return(struct trace_array
> > *tr,
> >
Hi Steve,
On Fri, Jan 20, 2017 at 12:25:35PM -0500, Steven Rostedt wrote:
> On Fri, 20 Jan 2017 11:44:45 +0900
> Namhyung Kim wrote:
>
> > The __ftrace_hash_move() is to allocates properly-sized hash and move
> > entries in the src ftrace_hash. It will be used to set function graph
> > filters
The mm-of-the-moment snapshot 2017-01-20-16-20 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
On 01/10, Kuninori Morimoto wrote:
> From: Khiem Nguyen
>
> CS2000 needs re-setup when redume, otherwise, it can't
> handle correct clock rate.
>
> Signed-off-by: Khiem Nguyen
> [Kuninori: cleanup original patch]
> Signed-off-by: Kuninori Morimoto
> ---
Applied to clk-next
--
Qualcomm Innov
On 01/11, Gregory CLEMENT wrote:
> From: Konstantin Porotchkin
>
> Add fixed clock of 400MHz to system controller driver. This clock is
> used as SD/eMMC clock source.
>
> Signed-off-by: Konstantin Porotchkin
> Reviewed-by: Omri Itach
> Reviewed-by: Hanna Hawa
> [fixed up conflicts, added er
On Fri, Jan 20, 2017 at 04:47:42PM +0100, Jason A. Donenfeld wrote:
>
> What do you mean? Nothing is wasted right now. The u64 function only
> gets u64s from a dedicated u64 array. The u32 function only gets u32s
> from a dedicated u32 array. There are separate batched entropy arrays
> for each fu
Hi Ted,
On Sat, Jan 21, 2017 at 1:10 AM, Theodore Ts'o wrote:
> Why would there be an unaligned access? What I was suggesting was an
> array of u32, and we just do two separate u32 accesses with a shift in
> the case of get_random_u64. There's nothing illegal about that.
>
> u64 retval;
>
>
> "John" == John Garry writes:
John> This patchset introduces some misc fixes and improvements. Most
John> signifigantly this patchset includes a workaround for a SATA IO
John> issue on v2 hw (hip06/7).
John> Differences v1->v2: - Add macro for SMP TIMEOUT in ITCT struct
Applied to 4.11/sc
On Fri, Jan 20, 2017 at 04:38:59PM +0100, Jason A. Donenfeld wrote:
> I was thinking that the issue isn't merely cache line and a slow down,
> but that on some platforms, this could be an _illegal unaligned
> access_. That means we'd need to rewrite the code to use the unaligned
> access helpers or
Several of the xfrm netlink and setsockopt() interfaces are not usable
from a 32-bit binary running on a 64-bit kernel due to struct padding
differences. This has been the case for many, many years[0]. This
patch series deprecates the broken netlink messages and replaces them
with packed structs
This provides a better sense of the data flow and inputs/outputs. No
change to code size or functionality.
Signed-off-by: Kevin Cernekee
---
include/net/xfrm.h | 36 --
net/key/af_key.c | 34 +++--
net/xfrm/xfrm_policy.c | 8 +-
net/xfrm/xfrm_state.c | 2 +-
net/xfrm/xfrm_u
xfrm_user_legacy.c will need to call a few common functions. Make
sure them have an "xfrm_" prefix, and declare them in a new xfrm_user.h
header.
Signed-off-by: Kevin Cernekee
---
net/xfrm/xfrm_user.c | 147 +--
net/xfrm/xfrm_user.h | 90
Add several new message types to address longstanding 32-bit/64-bit
compatibility issues. Use xfrm_user_legacy to handle the existing
message types, which will retain the old IDs for compatibility with
existing binaries.
For user->kernel messages, the nlmsg_type will determine whether to use
the
Several xfrm_* structs are incompatible between 32bit and 64bit builds:
xfrm_usersa_info 220 bytes on i386 -> 224 bytes on amd64
xfrm_userpolicy_info 164 -> 168
xfrm_userspi_info 228 -> 232, offset mismatch on min
xfrm_user_acquire 276 -> 280, offset mismatch on aalgos
xfrm_use
On Friday 20 January 2017 13:25:06 Colin King wrote:
> From: Colin Ian King
>
> acpi_match_device can potentially return NULL, so it is prudent to
> check if acpi_id is null before it is dereferenced. Add a check
> and an error message to indicate the failure.
>
> Signed-off-by: Colin Ian King
On 01/18, Andy Shevchenko wrote:
> On Tue, 2017-01-17 at 15:57 -0600, Pierre-Louis Bossart wrote:
> > These patches specifically enable the audio MCLK required by Baytrail
> > CR devices. It is the remaining part of a bigger set of patches
> > (already merged in Mark Brown's tree) that enable sound
On 01/17, Pierre-Louis Bossart wrote:
> diff --git a/drivers/clk/x86/clk-pmc-atom.c b/drivers/clk/x86/clk-pmc-atom.c
> new file mode 100644
> index 000..312d4e9
> --- /dev/null
> +++ b/drivers/clk/x86/clk-pmc-atom.c
[...]
> +
> +static void plt_clk_reg_update(struct clk_plt *clk, u32 mask, u32
On Friday 20 January 2017 10:25 PM, Andy Shevchenko wrote:
On Fri, Jan 20, 2017 at 12:23 AM, Sudip Mukherjee
wrote:
From: Sudip Mukherjee
Add the serial driver for the Exar chips. And also register the
platform device for the GPIO provided by the Exar chips.
Thanks, this is indeed much clea
On Friday 20 January 2017 10:02 PM, Andy Shevchenko wrote:
On Fri, Jan 20, 2017 at 12:23 AM, Sudip Mukherjee
wrote:
From: Sudip Mukherjee
Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which
can be controlled using gpio interface.
Add the gpio specific code.
Looks nice a
On Fri, 20 Jan 2017, David Carrillo-Cisneros wrote:
On Fri, Jan 20, 2017 at 1:08 PM, Shivappa Vikas
wrote:
On Fri, 20 Jan 2017, David Carrillo-Cisneros wrote:
On Fri, Jan 20, 2017 at 5:29 AM Thomas Gleixner
wrote:
On Thu, 19 Jan 2017, David Carrillo-Cisneros wrote:
If resctrl grou
Some versions of ARM GCC compiler such as Android toolchain throws in a
'-fpic' flag by default. This causes the gcc-goto check script to fail
although some config would have '-fno-pic' flag in the KBUILD_CFLAGS.
This patch passes the KBUILD_CFLAGS to the check script so that the
script does not r
Sigh...
On 01/20/2017 04:07 AM, kbuild test robot wrote:
> Hi Joshua,
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v4.10-rc4 next-20170120]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
&g
> Since i_blocksize() helper has been defined in fs.h, use it instead
> of open-coding.
The i_blocksize() work hasn't landed to the staging-next tree
so this can't land just yet.
> Signed-off-by: Geliang Tang
> ---
> drivers/staging/lustre/lustre/llite/file.c| 2 +-
> drivers/staging/lust
> > > On Mon, Dec 19, 2016 at 12:06:47PM -0500, James Simmons wrote:
> > > > Not for landing. This is the purposed UAPI headers
> > > > with the removal of unlikely and debugging macros.
> > > > This is just for feedback to see if this is acceptable
> > > > for the upstream client.
> > > >
> > >
This patch fixed the error using 'git rev-parse --show-cdup' to check
that git is used as SCM to track the current directory. The return
value of this command is not null string when the .git directory is
not in kernel topdir.
Signed-off-by: Xufeng Wang
---
scripts/setlocalversion | 2 +-
1 file
Hi Andrey,
[auto build test WARNING on pci/next]
[also build test WARNING on v4.10-rc4 next-20170120]
[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/Andrey-Smirnov/PCI-imx6-Fix-a-typo-in-error
On 01/10, Stanimir Varbanov wrote:
>
> > + udelay(1);
> > +
> > + reg = sc->gds_hw_ctrl ? sc->gds_hw_ctrl : sc->gdscr;
> > + ret = gdsc_poll_status(sc, reg, 0);
>
> This should be gdsc_poll_status(sc, reg, true) because after disabling
> hw_control we expect that the
On Tue, Jan 17, 2017 at 6:50 PM, Stephen Boyd wrote:
> Platforms like 96boards have a standardized connector/expansion
> slot that exposes signals like GPIOs to expansion boards in an
> SoC agnostic way. We'd like the DT overlays for the expansion
> boards to be written once without knowledge of t
The following changes since commit 3868f132cce6abab089fd6b12d6a7333712ade83:
clk: stm32f4: Use CLK_OF_DECLARE_DRIVER initialization method (2016-12-21
16:33:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-fixes-for-linu
On Fri, Jan 20, 2017 at 12:30:16PM -0500, Vivien Didelot wrote:
> Hi Gregory,
>
> Gregory CLEMENT writes:
>
> > If there a series about to be merged I can rebase my series on it. Else
> > I propose to keep it and convert the family check to ops when you will
> > send the series for it.
>
> I am
Greg,
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Tuesday, January 17, 2017 5:34 PM
> To: Limonciello, Mario
> Cc: gre...@linuxfoundation.org; rafael.j.wyso...@intel.com;
> pmen...@molgen.mpg.de; li...@leemhuis.info; tomas.wink...@intel.com;
> j...@gondo
On 20/01/17 20:47, Darrick J. Wong wrote:
> On Fri, Jan 20, 2017 at 01:26:12PM -0600, Eric Sandeen wrote:
>> On 1/20/17 8:26 AM, Colin King wrote:
>>> From: Colin Ian King
>>>
>>> If pag cannot be allocated, the current error exit path will trip
>>> a null pointer deference error when calling xfs_
On 01/18, Leo Yan wrote:
> In clock driver initialize phase the spinlock is missed to assignment
> to struct clkgate_separated, finally there have no locking to protect
> exclusive accessing for clock registers.
>
> This bug introduces the console has no output after enable coresight
> driver on 9
The current TPM 2.0 device driver extends only the SHA1 PCR bank
but the TCG Specification[1] recommends extending all active PCR
banks, to prevent malicious users from setting unused PCR banks with
fake measurements and quoting them.
The existing in-kernel interface(tpm_pcr_extend()) expects only
On 2017-01-19 02:47, Bjorn Andersson wrote:
The error paths of the common qcom-ufs functions for registering the
phy, acquiring clocks and acquiring regulators all print specific error
messages before returning an error, so there is no value in printing
yet
another - more generic - message when
On 2017-01-19 02:47, Bjorn Andersson wrote:
The fact that a regulator is always-on is a property of the regulator,
not a specific consumer. Implementing this in the driver leads to a
system behaviour that is dependent on if the Qualcomm UFS PHY was ever
(partially) probed.
If the specific regula
init_ring() and refill_rx_ring() don't check if mapping dma memory succeed.
The patch adds the checks and failure handling.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/ethernet/adaptec/starfire.c | 12
1 file chan
On Fri, Jan 20, 2017 at 5:57 AM, Cong Wang wrote:
>> > Why do we do autobind there, anyway, and why is it conditional on
>> > SOCK_PASSCRED? Note that e.g. for SOCK_STREAM we can bloody well get
>> > to sending stuff without autobind ever done - just use socketpair()
>> > to creat
On 2017-01-19 02:47, Bjorn Andersson wrote:
When regulator_get() tries to resolve a regulator supply but fail to
find a matching property in DeviceTree it returns a dummy regulator, if
a matching supply is specified but unavailable the regulator core will
return an error.
Based on this we should
1 - 100 of 744 matches
Mail list logo
