On Mon, 9 Jun 2014, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> This can then be used by other virtual configs.
>
> Signed-off-by: Luis R. Rodriguez
Suggested-by: David Rientjes
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
We check the CPU ID during driver init. There is no need
to do it again per logical CPU initialization.
So, remove the duplicate check.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/cpufreq/intel_pstate.c b/d
Add stats file in debugfs under driver's parent directory
(pstate_snb) which counts the time in nsecs per requested
P state and the number of times the specific state
was requested.
The file presents the statistics per logical CPU in the
following format. The time is displayed in msecs:
CPU0
P-st
Since we never remove sysfs entry, we can make the intel_pstate_kobject
local.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index fa44f0f..95
Remove unnecessary blank lines.
Remove unnecessary parentheses.
Remove unnecessary braces.
Put the code in one line where possible.
Add blank lines after variable declarations.
Alignment to open parenthesis.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 96 +++
Also put them in alphabetical order.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index 26a0262..d4f0518 100644
--- a/driv
Store busy_scaled value to avoid to duplicate call of
intel_pstate_get_scaled_busy on every sampling interval.
Also, rename the function to intel_pstate_calc_scaled_busy.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 12 ++--
1 file changed, 6 insertions(+), 6 de
Simplify the code by removing the inline functions
pstate_increase and pstate_decrease and use directly the
intel_pstate_set_pstate.
Signed-off-by: Stratos Karafotis
---
drivers/cpufreq/intel_pstate.c | 26 +++---
1 file changed, 3 insertions(+), 23 deletions(-)
diff --git a
On Mon, 09 Jun 2014 20:28:06 -
Thomas Gleixner wrote:
> There is no point to keep the task ref across the check for lock
> owner. Drop the ref before that, so the protection context is clear.
>
> Found while documenting the chain walk.
This looks fine, I just hate the subject. I don't see h
Hi all,
Below some work on intel_pstate driver.
Mostly a cleanup (patches 1/7, 5/7, 6/7, 7/7), some code simplification
(patch 4/7) and the addition of stats file in debugfs that presents
driver's statistics (patch 3/7).
Please note that patch 3/7 depends on 2/7 (which also simplifies calculation
On Mon, 9 Jun 2014, Kevin Hilman wrote:
> On Mon, Jun 9, 2014 at 1:22 PM, Nicolas Pitre
> wrote:
> > On Mon, 9 Jun 2014, Andrew Bresticker wrote:
> >
> >> > [1] While waiting for the forth-coming patch from Andrew to enable the
> >> > CCI port for the boot cluster), I do this from u-boot bef
Laba diena,
Mēs esam DIAMOND ŠVEICES aizdevumu uzņēmumam sniedzot aizdevumus ar pasta
reklāma. Mēs piedāvājam dažāda veida aizdevumu (īstermiņa un ilgtermiņa
aizdevumi, individuālie aizņēmumi, aizdevumi uzņēmumiem uc), par 3% procentu
likmi. Mēs izsniegt aizdevumus cilvēkiem, kam
pci_assign_unassigned_bridge_resources is used to assign resources below
a hotplug bridge. If the first attempt fails it will release some
resources and try again. If a resource allocation on the hotplug bridge
itself fails then pci_assign_unassigned_bridge_resources will invoke
pci_bus_release_bri
On Mon, Jun 9, 2014 at 1:22 PM, Nicolas Pitre wrote:
> On Mon, 9 Jun 2014, Andrew Bresticker wrote:
>
>> > [1] While waiting for the forth-coming patch from Andrew to enable the
>> > CCI port for the boot cluster), I do this from u-boot before starting
>> > the kernel (based on earlier ema
On Sat, 07 Jun 2014 23:41:21 -0400
Sasha Levin wrote:
> Hi Steven,
>
> Yup, it took me *that* long to reproduce it again, but I can confirm that that
> BUG() gets hit (the printk shows cpu 30 like the BUG):
>
> [ 2410.677199] kernel BUG at kernel/trace/ring_buffer.c:563!
> [ 2410.679445] can: r
Thanks Pete for the patch.
Patch looks good for me.
Acked-by: Srinivas Kandagatla
On 09/06/14 21:22, Peter Griffin wrote:
This patch fixes two problems: -
1) The device tree isn't currently providing sti-ethclk which is
required by the dwmac glue code to correctly configure the ethernet
PHY
The conditions under which deadlock detection is conducted are unclear
and undocumented.
Add constants instead of using 0/1 and provide a selection function
which hides the additional debug dependency from the calling code.
Add comments where needed.
Signed-off-by: Thomas Gleixner
---
kernel/l
The deadlock logic is only required for futexes.
Remove the extra arguments for the public functions and also for the
futex specific ones which get always called with deadlock detection
enabled.
Signed-off-by: Thomas Gleixner
---
include/linux/rtmutex.h |6 +---
kernel/futex.c
In case the dead lock detector is enabled we follow the lock chain to
the end in rt_mutex_adjust_prio_chain, even if we could stop earlier
due to the priority/waiter constellation.
But once we are not longer the top priority waiter in a certain step
or the task holding the lock has already the sam
Add a separate local variable for the boost/deboost logic to make the
code more readable. Add comments where appropriate.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c | 58 ++-
1 file changed, 48 insertions(+), 10 deletions(-)
Index:
Add commentry to document the chain walk and the protection mechanisms
and their scope.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c | 52 +++
1 file changed, 52 insertions(+)
Index: tip/kernel/locking/rtmutex.c
==
Exit right away, when the removed waiter was not the top prioriy
waiter on the lock. Get rid of the extra indent level.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c | 26 ++
1 file changed, 10 insertions(+), 16 deletions(-)
Index: tip/kernel/locking/rtmu
This is another round of clarification and optimization patches for
the rtmutex code.
When I looked last week into the dead lock detector I spent some time
to figure out how the various arguments and local variables are
protected and whats the scope of the various protection algorithms, so
I added
There is no point to keep the task ref across the check for lock
owner. Drop the ref before that, so the protection context is clear.
Found while documenting the chain walk.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
On Mon, 9 Jun 2014, Andrzej Zaborowski wrote:
> [resend]
> In generic_id the long int timestamp is multiplied by 10 and needs
> an explicit cast to u64.
>
> Without that the id in the resulting pstore filename is wrong and
> userspace may have problems parsing it, but more importantly files i
On Mon, 9 Jun 2014, Andrew Bresticker wrote:
> > [1] While waiting for the forth-coming patch from Andrew to enable the
> > CCI port for the boot cluster), I do this from u-boot before starting
> > the kernel (based on earlier email from Doug):
> >
> > mw.l 10d25000 3 # Enable CCI fro
This patch fixes two problems: -
1) The device tree isn't currently providing sti-ethclk which is
required by the dwmac glue code to correctly configure the ethernet
PHY clock speed.
This means depending on what the bootloader/jtag has
configured this clock to, and what switch/hub the board is pl
> diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> index 9ffecd5..453d89e 100644
> --- a/drivers/usb/host/xhci.h
> +++ b/drivers/usb/host/xhci.h
> @@ -1582,6 +1582,9 @@ struct xhci_hcd {
> u32 port_status_u0;
> /* Compliance Mode Timer Triggered every 2
Hi Paul,
Thanks for the patch.
On Thu, May 22, 2014 at 8:42 PM, Paul Bolle wrote:
> A check for CONFIG_DM644X_VIDEO_PORT_ENABLE was added in v2.6.32. The
> related Kconfig symbol was never added so this check has always
> evaluated to false. Remove that check.
>
Applied.
Thanks,
--Prabhakar Lad
From: Don Zickus
The next patch needs to sort on cpumode, so add it to hist_entry to be tracked.
Signed-off-by: Don Zickus
Link:
http://lkml.kernel.org/r/1401208087-181977-6-git-send-email-dzic...@redhat.com
Signed-off-by: Jiri Olsa
---
tools/perf/util/hist.c | 7 ---
tools/perf/util/sor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/7/14, 7:52 PM, Linus Torvalds wrote:
> On Wed, Jun 4, 2014 at 1:27 PM, Jan Kara wrote:
>> Hello Linus,
>>
>> could you please pull from
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git
>> for_linus
>>
>> to get big reiser
From: "Steven Rostedt (Red Hat)"
Coming in v3.16, trace events will be able to save bitmasks in raw
format in the ring buffer and output it with the __get_bitmask() macro.
In order for userspace tools to parse this, it must be able to handle
the __get_bitmask() call and be able to convert the da
From: "Steven Rostedt (Red Hat)"
Add a flag to pevent that will let the callers be able to set it and
keep the system, and perhaps even normal plugins from being loaded.
This is useful when plugins might hide certain information and seeing
the raw events shows what may be going on.
Signed-off-b
hi Ingo,
please consider pulling
thanks,
jirka
The following changes since commit 82b897782d10fcc4930c9d4a15b175348fdd2871:
perf: Differentiate exec() and non-exec() comm events (2014-06-06 07:56:22
+0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel
From: Namhyung Kim
With the Sebastian's change of handling num array argument (of raw
syscall enter), the script still failed to work like this:
$ perf record -e raw_syscalls:* sleep 1
$ perf script -g python
$ perf script -s perf-script.py
...
Traceback (most recent call last):
Fi
From: Don Zickus
The kernel piece passes more info now. Update the perf tool to reflect
that and adjust the synthesized maps to play along.
Signed-off-by: Don Zickus
Link:
http://lkml.kernel.org/r/1400526833-141779-4-git-send-email-dzic...@redhat.com
Signed-off-by: Jiri Olsa
---
tools/perf/
From: Don Zickus
Different arches may have different cacheline sizes. Look it up and set
a global variable for reference.
Signed-off-by: Don Zickus
Link:
http://lkml.kernel.org/r/1401480605-97442-1-git-send-email-dzic...@redhat.com
Signed-off-by: Jiri Olsa
---
tools/perf/perf.c | 1 +
> [1] While waiting for the forth-coming patch from Andrew to enable the
> CCI port for the boot cluster), I do this from u-boot before starting
> the kernel (based on earlier email from Doug):
>
> mw.l 10d25000 3 # Enable CCI from U-Boot
>From the other thread, it sounds like Nicolas
On Mon, Jun 9, 2014 at 12:43 PM, Alex Williamson
wrote:
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=73551
> Reported-by: rwar...@gmx.de
> Tested-by: rwar...@gmx.de
> Signed-off-by: Alex Williamson
Added to pci/iommu for v3.16, thanks!
> ---
>
> One more for the pci/iommu branch
>
> dri
From: Don Zickus
This reverts commit 3090ffb5a2515990182f3f55b0688a7817325488.
Re-enable the mmap2 interface as we will have a user soon.
Since things have changed since perf disabled mmap2, small tweaks
to the revert had to be done:
o commit 9d4ecc88 forced (n!=8) to become (n<7)
o a new libu
Add tags/TAGS/cscope targets to the quiet family.
$ make tags cscope
BUILD: Doing 'make -j4' parallel build
GEN tags
$ make cscope
BUILD: Doing 'make -j4' parallel build
GEN cscope
Reviewed-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Aher
On 06/06/2014 03:58 PM, Naoya Horiguchi wrote:
> @@ -6723,14 +6723,9 @@ static int mem_cgroup_count_precharge_pmd(pmd_t *pmd,
> struct mm_walk *walk)
> {
> struct vm_area_struct *vma = walk->vma;
> - spinlock_t *ptl;
>
> - if (pmd_trans_huge_lo
From: Andi Kleen
perf stat -rX prints the stddev for multiple measurements.
Just looking at the stddev for judging the quality of the data
is a bit dangerous The simplest sanity check is to just look
at a simple plot. This patchs add a sparkline to the end
of the measurements to make it simple to
From: Don Zickus
Add mem-mode sorting types and mem-mode itself to perf-report documentation.
Signed-off-by: Don Zickus
Link:
http://lkml.kernel.org/r/1400526833-141779-5-git-send-email-dzic...@redhat.com
Signed-off-by: Jiri Olsa
---
tools/perf/Documentation/perf-report.txt | 22
From: Peter Zijlstra
The mmap2 interface was missing the protection and flags bits needed to
accurately determine if a mmap memory area was shared or private and
if it was readable or not.
Signed-off-by: Peter Zijlstra
[tweaked patch to compile and wrote changelog]
Signed-off-by: Don Zickus
Li
From: "Steven Rostedt (Red Hat)"
Add the options "parent" and "indent" to the function plugin.
When parent is set, the output looks like this:
function: fsnotify_modify <-- vfs_write
function: zone_statistics <-- get_page_from_freelist
function:__inc_zone
From: Don Zickus
In perf's 'mem-mode', one can get access to a whole bunch of details specific
to a
particular sample instruction. A bunch of those details relate to the data
address.
One interesting thing you can do with data addresses is to convert them into a
unique
cacheline they belong t
The file factoring in builtin-inject.c object introduced regression
in attr event callback. The commit is:
3406912 perf inject: Handle output file via perf_data_file object
Following hunk reversed the logic:
- if (!inject->pipe_output)
+ if (&inject->output.is_pipe)
putting it b
From: Steven Rostedt
The traceevent plugins allows developers to have their events print out
information that is more advanced than what can be achieved by the
trace event format files.
As these plugins are used on the userspace side of the tracing tools, it
is only logical that the tools should
On 06/06/2014 03:58 PM, Naoya Horiguchi wrote:
> +enum mm_walk_control {
> + PTWALK_NEXT = 0,/* Go to the next entry in the same level or
> + * the next vma. This is default behavior. */
> + PTWALK_DOWN,/* Go down to lower level */
> + PT
Hi guys,
We recently ran into/corrected a bug in our BIOS that was exposed by the
recent updates to the way that the EFI code maps in memory during boot.
Discussion here:
http://comments.gmane.org/gmane.linux.kernel/1638074
Anyways, we now need to find a way to determine the BIOS version before
On Mon, Jun 09, 2014 at 06:09:52PM +0300, Dan Carpenter wrote:
> The PM800_BUCK3 define is cut and pasted twice so we can remove the
> second instance.
Applied, thanks.
signature.asc
Description: Digital signature
Remove two redundant casts from char * to char *.
Signed-off-by: Nick Black
---
drivers/scsi/scsi_transport_iscsi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/scsi_transport_iscsi.c
b/drivers/scsi/scsi_transport_iscsi.c
index 0102a2d..38a1de3 100644
---
On Mon, Jun 09, 2014 at 03:15:47PM +0900, Chanwoo Choi wrote:
> This patch add S2MPU02 regulator device to existing S2MPS11 device driver
> because of little difference between S2MPS1x and S2MPU02. The S2MPU02
> regulator device includes LDO[1-28] and BUCK[1-7].
Acked-by: Mark Brown
but a few ni
On 03/06/14 00:14, Reyad Attiyat wrote:
Updated magn_3d_channel enum for all possible north channels
Added functions to setup iio_chan_spec array depending on which hid usage
reports are found
Renamed magn_val to iio_val to differentiate the index being used
Updated magn_3d_state struct to ho
On Sun, Jun 08, 2014 at 03:26:29PM +0400, Alexander Shiyan wrote:
> Read-modify-write sequence is already protected by regmap, so no
> additional locks need. This patch remove such locks from mc13xxx
> regulator driver.
Applied, thanks.
signature.asc
Description: Digital signature
On Sun, Jun 08, 2014 at 03:26:28PM +0400, Alexander Shiyan wrote:
> Field "hi_bit" is not used anywhere in the driver.
> This patch removes this excess field.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Jun 09, 2014 at 11:37:46AM +0200, Javier Martinez Canillas wrote:
> +Optional node:
> +- voltage-regulators : The regulators of max77802 have to be instantiated
> + under subnode named "voltage-regulators" using the following format.
Every other PMIC calls this node regulators...
> +
On Wed, Jun 4, 2014 at 8:06 PM, Roland Dreier wrote:
> On Wed, Jun 4, 2014 at 9:37 AM, Steve Wise
> wrote:
>> Seems like the subject lines in each patch are getting truncated?
> Yes, truncated in patchwork too -- for example:
> https://patchwork.kernel.org/patch/4292461/
>
> Please fix and resen
On Mon, 9 Jun 2014 11:51:09 -0700
Linus Torvalds wrote:
> On Mon, Jun 9, 2014 at 11:29 AM, Steven Rostedt wrote:
> >>
> >> And once again, note that the normal mutex is already unsafe (unless I
> >> missed
> >> something).
> >
> > Is it unsafe?
> >
> > This thread was started because of a bug w
On Mon, Jun 09, 2014 at 11:37:47AM +0200, Javier Martinez Canillas wrote:
> + case REGULATOR_MODE_STANDBY:/* switch off */
> + if (id != MAX77802_LDO1 && id != MAX77802_LDO20 &&
> + id != MAX77802_LDO21 && id != MAX77802_LDO3) {
> +
On Mon, 9 Jun 2014, Geert Uytterhoeven wrote:
> JFYI, when comparing v3.15-rc8[1] to v3.15-rc7[3], the summaries are:
> - build errors: +4/-4
+ /scratch/kisskb/src/kernel/bounds.c: error: -mcall-aixdesc must be big
endian: => 1:0
+ /scratch/kisskb/src/scripts/mod/devicetable-offsets.c: er
Below is the list of build error/warning regressions/improvements in
v3.15-rc8[1] compared to v3.14[2].
Summarized:
- build errors: +9/-3
- build warnings: +99/-117
JFYI, when comparing v3.15-rc8[1] to v3.15-rc7[3], the summaries are:
- build errors: +4/-4
- build warnings: +8/-33
Note
On Mon, Jun 09, 2014 at 03:15:51PM -0400, Dave Jones wrote:
> On Mon, Jun 09, 2014 at 12:07:07PM -0700, gre...@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > sched: Disallow sched_attr::sched_policy < 0
> >
> > to the 3.1
Will test the new feature soon, looks useful, thanks for working on
this!
Some coments about the patch below.
- Arnaldo
Em Mon, Jun 09, 2014 at 01:21:12PM +0400, Stanislav Fomichev escreveu:
> @@ -213,7 +245,7 @@ static void pid_fork(struct timechart *tchart, int pid,
> int ppid, u64 timestamp
On Mon, Jun 09, 2014 at 11:36:24AM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> This lets you build a kernel which can support xen dom0
> or xen guests by just using:
>
>make xenconfig
>
> Technically xen supports a dom0 kernel and also a guest
> kernel configuration but
On Mon, Jun 09, 2014 at 07:29:39PM +0900, Chanwoo Choi wrote:
> + ret = of_property_read_u32(suspend_np, "regulator-mode", &pval);
> + if (!ret)
> + suspend_state->mode = pval;
If we're going to do that we'd need to define what modes mean in the DT
bind
unsigned long value is never < 0
Cc: Doug Thompson
Cc: Borislav Petkov
Signed-off-by: Fabian Frederick
---
drivers/edac/edac_module.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/edac/edac_module.c b/drivers/edac/edac_module.c
index a66941f..e6d1691 100644
--- a/
On Mon, Jun 09, 2014 at 07:29:40PM +0900, Chanwoo Choi wrote:
> +- regulator-initial-state: initial state for suspend state
> +- regulator-state-[standby/mem/disk] sub-root node for suspend state
> + regulator-volt: voltage consumers may set in suspend state
> + regulator-mode: voltage mod
On Mon, Jun 09, 2014 at 12:07:07PM -0700, gre...@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> sched: Disallow sched_attr::sched_policy < 0
>
> to the 3.14-stable tree which can be found at:
>
> http://www.kernel.org/git/
This 'bug' feels very theoretical to me. There were about 3 kernel
releases back when inotify was rewriten onto fsnotify where it was
intentionally reusing wd's. So instead of a MAX_INT wrap all you have
to do was a single create/destroy/create to get reuse. Almost every
utility survived... Bu
On Mon, Jun 2, 2014 at 11:40 PM, Dave Jones wrote:
> On Sun, Jun 01, 2014 at 07:37:20PM -0700, Linus Torvalds wrote:
> > So let's try to see how well that works - the last weeks of the
> > release tends to be me just waiting around to make sure nothing bad is
> > happening, so doing this kind o
On 06/09, Steven Rostedt wrote:
>
> On Mon, 9 Jun 2014 20:15:53 +0200
> Oleg Nesterov wrote:
>
> > > That would indeed be a bad thing, as it could potentially lead to
> > > use-after-free bugs. Though one could argue that any code that resulted
> > > in use-after-free would be quite aggressive.
size_t and unsigned long values are never < 0
Cc: David Howells
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
fs/cachefiles/daemon.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/cachefiles/daemon.c b/fs/cachefiles/daemon.c
index b078d30..ff43e5a 100644
-
On Sun, 8 Jun 2014 18:29:11 -0700
Yinghai Lu wrote:
> On Sun, Jun 8, 2014 at 3:14 PM, Luiz Capitulino
> wrote:
> > In short, I believe this is just dead code for the upstream kernel but this
> > causes a bug for 2.6.32 based kernels.
> >
> > The setup_node_data() function is used to initialize
On Sun, 8 Jun 2014 15:25:50 -0700 (PDT)
David Rientjes wrote:
> On Sun, 8 Jun 2014, Luiz Capitulino wrote:
>
> > diff --git a/arch/x86/include/asm/numa.h b/arch/x86/include/asm/numa.h
> > index 4064aca..01b493e 100644
> > --- a/arch/x86/include/asm/numa.h
> > +++ b/arch/x86/include/asm/numa.h
>
This typedef is unnecessary and should just be removed.
Remove the last actual use of typedef ctl_table.
Signed-off-by: Joe Perches
---
On Mon, 2014-06-09 at 10:51 -0700, Joe Perches wrote:
> All the uses have been removed so remove the typedef.
Not so fast buckwheat.
I was showing off my obvio
Tomasz,
On Fri, Jun 6, 2014 at 4:41 PM, Mike Turquette wrote:
> Quoting Tomasz Figa (2014-06-05 15:26:31)
>> On 05.06.2014 22:35, Doug Anderson wrote:
>> > The "aclk66_peric" clock is a gate clock with a whole bunch of gates
>> > underneath it. This big gate isn't very useful to include in our
>
On Mon, Jun 9, 2014 at 11:29 AM, Steven Rostedt wrote:
>>
>> And once again, note that the normal mutex is already unsafe (unless I missed
>> something).
>
> Is it unsafe?
>
> This thread was started because of a bug we triggered in -rt, which
> ended up being a change specific to -rt that modifie
This is a patch to add i2c algorith support for nxp sc18im700
master i2c bus controller with uart interface
Signed-off-by: Raghavendra Chandra Ganiga
---
drivers/i2c/algos/Kconfig | 2 +
drivers/i2c/algos/Makefile | 1 +
drivers/i2c/algos/i2c-algo-sc18im700.c | 274
On 06/09/2014 09:33 PM, Stephen Warren wrote:
On 06/06/2014 12:27 AM, Mikko Perttunen wrote:
The only compile-time dependencies here should be that:
- patch 8 of 9 which contains the actual driver depends on patch 6 of 9
(though only when building as a module) and the efuse series
- patch 2 o
Link: https://bugzilla.kernel.org/show_bug.cgi?id=73551
Reported-by: rwar...@gmx.de
Tested-by: rwar...@gmx.de
Signed-off-by: Alex Williamson
---
One more for the pci/iommu branch
drivers/pci/quirks.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/quirks.c b/drivers/pci/qui
On Mon, Jun 09, 2014 at 04:04:35PM +0100, Richard Fitzgerald wrote:
> Using the driver for the internal regulator to also control
> the clock frequency of blocks inside the codec is an
> unexpected side-effect for a regulator, and also means that
> the core clocks won't be changed as expected if an
Paolo Bonzini writes:
> Even on a store the optimization saves about 50 clock cycles,
> mostly because the jump in write_memory_operand becomes much more
> predictable.
>
> Reviewed-by: Paolo Bonzini
> Signed-off-by: Paolo Bonzini
Isn't the reviewed-by automatically implied ? :)
> ---
> arch/
From: "Luis R. Rodriguez"
This lets you build a kernel which can support xen dom0
or xen guests by just using:
make xenconfig
Technically xen supports a dom0 kernel and also a guest
kernel configuration but upon review with the xen team
since we don't have many dom0 options its best to just
On 06/05/2014 10:38 PM, Viresh Kumar wrote:
> Tegra's driver got updated a bit (00917dd cpufreq: Tegra: implement
> intermediate
> frequency callbacks) and implements new 'intermediate freq' infrastructure of
> core. Above commit updated comments about when to call
> clk_prepare_enable(pll_x_clk)
Hello.
On 06/09/2014 06:23 PM, One Thousand Gnomes wrote:
#include
#include
+#ifdef CONFIG_GPIOLIB
+#include
+#endif
Please create a new struct, a new file and put all the GPIO stuff in
there rather than #if bombing the driver.
You can then declare blank methods for the gpio stuff
From: "Luis R. Rodriguez"
We'll be adding options for xen as well.
Cc: Borislav Petkov
Cc: Pekka Enberg
Cc: David Rientjes
Cc: Michal Marek
Cc: Randy Dunlap
Cc: penb...@kernel.org
Cc: levinsasha...@gmail.com
Cc: mtosa...@redhat.com
Cc: fengguang...@intel.com
Cc: David Vrabel
Cc: Ian Campbe
From: "Luis R. Rodriguez"
This can then be used by other virtual configs.
Signed-off-by: Luis R. Rodriguez
---
arch/x86/Makefile | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 33f71b0..c78747b 100644
--- a/arch/x86/Mak
On 06/06/2014 12:27 AM, Mikko Perttunen wrote:
> The only compile-time dependencies here should be that:
> - patch 8 of 9 which contains the actual driver depends on patch 6 of 9
> (though only when building as a module) and the efuse series
> - patch 2 of 9 refers to the DT node called "padctl",
On Mon, 9 Jun 2014 20:15:53 +0200
Oleg Nesterov wrote:
> > That would indeed be a bad thing, as it could potentially lead to
> > use-after-free bugs. Though one could argue that any code that resulted
> > in use-after-free would be quite aggressive. But still...
>
> And once again, note that
On 06/06/2014 01:35 AM, Peter De Schrijver wrote:
> On Fri, Jun 06, 2014 at 12:54:00AM +0200, Stephen Warren wrote:
...
>>> No. It's only used to populate /sys/devices/soc0/revision. I don't think
>>> that's particularly important.
>>
>> But it's a feature that works today. Why should we break it?
On Mon, Jun 09, 2014 at 01:47:08PM -0400, Vivek Goyal wrote:
> On Sun, Jun 08, 2014 at 06:22:00PM -0400, Joe Lawrence wrote:
>
> [..]
> > Summary thus far:
> >
> > R12: 88103c17a130 = struct rcu_head *rcu_head
> > R13: 88103c17a080 = struct blkcg_gq *blkg
> > 88103fc7df90 = stru
Hello, Linus.
A lot of activities on cgroup side. Heavy restructuring including
locking simplification took place to improve the code base and enable
implementation of the unified hierarchy, which currently exists behind
a __DEVEL__ mount option. The core support is mostly complete but
individua
On 06/09, Paul E. McKenney wrote:
>
> On Sun, Jun 08, 2014 at 03:07:18PM +0200, Oleg Nesterov wrote:
> >
> > I only meant that afaics rcu_read_unlock_special() equally depends on the
> > fact that rt_mutex_unlock() does nothing with "struct rt_mutex" after it
> > makes another rt_mutex_lock() + rt_
On Mon, Jun 9, 2014 at 1:56 PM, Stephen Boyd wrote:
> On 06/06/14 07:03, Stephane Viau wrote:
>> The clock driver usually complains when a clock is being prepared
>> before setting its rate. It is the case here for "core_clk" which
>> needs to be set at 19.2 MHz before we attempt a prepare_enable(
Doug Anderson writes:
> On exynos mcpm systems the firmware is hardcoded to jump to an address
> in SRAM (0x02073000) when secondary CPUs come up. By default the
> firmware puts a bunch of code at that location. That code expects the
> kernel to fill in a few slots with addresses that it uses t
[ I'm currently running my tests on it now, and so far, after a few
hours it has yet to blow up. I'll run it for 24 hours which it never
succeeded in the past. ]
The tracing code has a way to make directories within the debugfs file
system as well as deleting them using mkdir/rmdir in the instan
The driver was configuring the interrupt handler for the Level-2
interrupts to be "level" triggered while they are in fact "edge"
triggered. Fix this by using the correct handler.
Reported-by: Brian Norris
Signed-off-by: Florian Fainelli
---
drivers/irqchip/irq-brcmstb-l2.c | 2 +-
1 file chang
On Thu, 2014-05-22 at 17:07 -0600, Alex Williamson wrote:
> Alex Williamson (16):
> PCI: Add DMA alias iterator
> PCI: define pci_dev_flags as bit shifts
> PCI: quirk pci_for_each_dma_alias()
> PCI: quirk dma_alias_devfn for Ricoh devices
> PCI: quirk dma_alias_devfn f
401 - 500 of 1018 matches
Mail list logo
