From: Rasmus Villemoes
Date: Fri, 23 Jan 2015 12:06:52 +0100
> The code 'if (foo & X) foo &= ~X;' is semantically equivalent to
> simply 'foo &= ~X;', but gcc generates about four instructions for the
> former, one for the latter. Similarly, if X consists of a single bit,
> 'if (!(foo & X)) X |=
drivers/gpu/drm/nouveau/core/subdev/fuse/gm107.c:50:5-8: WARNING: end returns
can be simpified
Simplify a trivial if-return sequence. Possibly combine with a
preceding function call.
Generated by: scripts/coccinelle/misc/simple_return.cocci
CC: Martin Peres
Signed-off-by: Fengguang Wu
---
From: Hayes Wang
Date: Tue, 20 Jan 2015 03:24:52 +
> David Miller [mailto:da...@davemloft.net]
>> Sent: Tuesday, January 20, 2015 10:52 AM
> [...]
>> agg->list is not local, you have to use a spinlock to protect
>> modifications to it, some other sites which modify agg->list do take
>> the
drivers/gpu/drm/nouveau/core/subdev/bar/base.c:132:5-8: WARNING: end returns
can be simpified
Simplify a trivial if-return sequence. Possibly combine with a
preceding function call.
Generated by: scripts/coccinelle/misc/simple_return.cocci
Signed-off-by: Fengguang Wu
---
base.c |5
From: Kalle Valo
Date: Tue, 20 Jan 2015 11:03:33 +0200
> more fixes for 3.19, I hope these are still appropriate. Please let me
> know if there are any issues.
Pulled, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Are there any plans to include the smi2021 driver in the vanilla kernel
any time soon? This driver is for the EasyCap Somagic usb framegrabbers:
https://code.google.com/p/easycap-somagic-linux/wiki/BuildingKernelModule#Compile
The latest version of the driver is due to Jon Arne and can be
On Fri, Jan 23, 2015 at 09:19:46PM +0800, Greg Kroah-Hartman wrote:
> On Fri, Jan 23, 2015 at 08:28:20AM +0200, Ahmed S. Darwish wrote:
> > On Fri, Jan 16, 2015 at 11:16:05AM -0800, Greg Kroah-Hartman wrote:
> > > From: Daniel Mack
> > >
> > > kdbus is a system for low-latency, low-overhead,
Hi!
On Wed, Jan 21, 2015 at 04:20:25PM +, Andri Yngvason wrote:
> Quoting Ahmed S. Darwish (2015-01-20 21:45:37)
> > From: Ahmed S. Darwish
> >
> > Replace most of the can interface's state and error counters
> > handling with the new can-dev can_change_state() mechanism.
> >
> >
On Thu, Jan 22, 2015 at 10:14:47AM +, Andri Yngvason wrote:
> Quoting Marc Kleine-Budde (2015-01-21 22:59:23)
> > On 01/21/2015 05:20 PM, Andri Yngvason wrote:
> > > Marc, could you merge the "move bus_off++" patch before you merge this so
> > > that I
> > > won't have to incorporate this
Am 25.01.2015 um 03:13 schrieb Pádraig Brady:
On 24/01/15 12:29, Alexander Holler wrote:
Am 24.01.2015 um 13:09 schrieb Alexander Holler:
Am 24.01.2015 um 12:37 schrieb Alexander Holler:
Am 24.01.2015 um 11:45 schrieb Alexander Holler:
It uses shred, in the hope it will somedays learn how
On Fri, Jan 23, 2015 at 10:32:13AM +, Andri Yngvason wrote:
> Quoting Ahmed S. Darwish (2015-01-23 06:07:34)
> > On Wed, Jan 21, 2015 at 05:13:45PM +0100, Wolfgang Grandegger wrote:
> > > On Wed, 21 Jan 2015 10:36:47 -0500, "Ahmed S. Darwish"
> > > wrote:
> > > > On Wed, Jan 21, 2015 at
A couple of fixes - deadlock in CIFS and build breakage in cris serial
driver (resurfaced f_dentry in there). Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (1):
fix deadlock in cifs_ioctl_clone()
David Howells (1):
VFS:
On 24/01/15 12:29, Alexander Holler wrote:
> Am 24.01.2015 um 13:09 schrieb Alexander Holler:
>> Am 24.01.2015 um 12:37 schrieb Alexander Holler:
>>> Am 24.01.2015 um 11:45 schrieb Alexander Holler:
>>>
It uses shred, in the hope it will somedays learn how to shred stuff on
FLASH based
In general, the kernel should report temperature readings exactly as
reported by the hardware. The cpu / gpu thermal driver works in 5 degree
increments,but we ought to do more accurate. The temperature will do
linear interpolation between the entries in the table.
Test= $md5sum /dev/zero &
This patch is merged on chromiumos/third_party/kernel.
https://chromium-review.googlesource.com/#/c/239190/
Tested on veyron boards.
Changes in v6:
It's not really need,so delete the follows:
else if (code == TSADCV2_DATA_MASK)
Changes in v5:
Fixed some style.
Changes in v4:
"return -EAGAIN"
On Fri, Jan 23, 2015 at 11:49 PM, Caesar Wang wrote:
> In general, the kernel should report temperature readings exactly as
> reported by the hardware. The cpu / gpu thermal driver works in 5 degree
> increments,but we ought to do more accurate. The temperature will do
> linear interpolation
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c:74:26-27: Unneeded semicolon
Removes unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Signed-off-by: Fengguang Wu
---
padnv94.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
From: Romain Perier
Date: Tue, 20 Jan 2015 07:09:36 +
> This series fixes few issues in dwmac-rk:
>
> 1. Voltage settings was hardcoded into the driver for the phy regulator.
>The driver now uses the default voltage settings found in the devicetree,
>which are applied throught the
Quoting Thierry Reding (2015-01-23 01:34:10)
> On Thu, Jan 22, 2015 at 12:25:46PM -0800, Stephen Boyd wrote:
> > On 01/22, Thierry Reding wrote:
> > > On Wed, Jan 21, 2015 at 04:16:05PM -0800, Stephen Boyd wrote:
> > > > On 01/21/2015 08:13 AM, Thierry Reding wrote:
> > > > > From: Thierry Reding
Trebate li financiranje?
Trebate li poslovne i osobne kredite?
Želite li vaša tvrtka za refinanciranje?
Naše sjedište nalazi se u Sjedinjenim Americkim Državama i Europi. dajemo
kredit svaki
Pojedinca i društva kamatnoj stopi od 3% godišnje. Za više informacija
kontaktirajte e-mail:
Hi Linus,
Two small patches that should make it into 3.19:
- A fixup from me for NVMe, making the cq_vector a signed variable.
Otherwise our -1 comparison fails, and commit 2b25d981790b doesn't do
what it was supposed to.
- A fixup for the hotplug handling for blk-mq from Ming Lei, using
Hi Heikki,
On Fri, Jan 23, 2015 at 05:12:58PM +0200, Heikki Krogerus wrote:
> TUSB1210 ULPI PHY has vendor specific register for eye
> diagram tuning. On some platforms the system firmware has
> set optimized value to it. In order to not loose the
> optimized value, the driver stores it during
On Wed, 21 Jan 2015, Daniel Thompson wrote:
> @@ -307,6 +307,7 @@ static inline irq_hw_number_t irqd_to_hwirq(struct
> irq_data *d)
> * @irq_eoi: end of interrupt
> * @irq_set_affinity:set the CPU affinity on SMP machines
> * @irq_retrigger: resend an IRQ to the CPU
> + *
Hi Linus,
The following changes since commit 966903a98fd80ae5f5c4a7ca121d36ea0ba23143:
Merge tag 'samsung-fixes-3.19' of
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung into fixes
(2015-01-16 19:11:37 -0800)
are available in the git repository at:
Hi Sedat,
On Sat, 24 Jan 2015 10:03:06 +0100 Sedat Dilek wrote:
>
> AFAICS, a new linux-next will be available on Monday (2015-01-26).
> I try to retest with this.
Actually, Tuesday - Monday is a holiday here.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
On Fri, 23 Jan 2015, Daniel Thompson wrote:
> This patch fixes that problem by providing banked clock data in a
> similar manner to Thomas Gleixner's 4396e058c52e("timekeeping: Provide
> fast and NMI safe access to CLOCK_MONOTONIC").
By some definition of similar.
> -struct clock_data {
> -
Hi,
On Sat, Jan 24, 2015 at 12:12:04PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jan 23, 2015 at 04:37:45PM -0600, Felipe Balbi escreveu:
> > On Fri, Jan 23, 2015 at 05:59:59PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi escreveu:
> >
On 24/01/15 21:56, Bryan O'Donoghue wrote:
+
+ if ((imr_to_phys(imr.addr_lo) == base) &&
+ (imr_to_phys(imr.addr_hi) == max)) {
I think we need to take care of the size that has been fix-up here ...
+ found = 1;
+
On 24/01/15 11:02, Andy Shevchenko wrote:
On Sat, Jan 24, 2015 at 3:48 AM, Ong, Boon Leong
wrote:
+static int imr_enabled(struct imr_regs *imr)
Do we want to make it inline perhaps since it is 1 liner?
Since it is declared static I would even suggest the new name is_imr_enabled().
I
Fix code-formatting warnings from script/checkpatch.pl; multiple instances of
WARNING: line over 80 characters
CHECK: No space is necessary after a cast
CHECK: Alignment should match open parenthesis
WARNING: quoted string split across lines
CHECK: Blank lines aren't necessary before a close
./fs/notify/inotify/inotify.h:23:
CHECK: extern prototypes should be avoided in .h files
./fs/notify/inotify/inotify.h:25:
CHECK: extern prototypes should be avoided in .h files
Removed extrn keywords; the matter, however, seems to be an open
debate.
I just noticed that I failed in setting the right From: header. Sorry for
this, I will re-post the patches with correct meta-data set.
Am Freitag, 16. Januar 2015, 16:15:11 schrieb y...@mail.netz39.de:
> From: Stefan Haun
>
> ./fs/notify/inotify/inotify.h:23:
> CHECK: extern prototypes should
On Fri, 23 Jan 2015, Daniel Thompson wrote:
> +#ifdef CONFIG_ARCH_WANT_NMI_PRINTK
> +extern __printf(1, 0) int nmi_vprintk(const char *fmt, va_list args);
> +
> +struct cpumask;
> +extern int prepare_nmi_printk(struct cpumask *cpus);
> +extern void complete_nmi_printk(struct cpumask *cpus);
> +
>
On Saturday 24 January 2015 18:33:00 Rickard Strandqvist wrote:
> 2015-01-22 8:44 GMT+01:00 Lee Jones :
> >
> > Are you sure a struct is required at all now? It only contains a
> > single bool after all.
>
>
> Hi Lee
>
> Okay, I will gladly remove ab8500_ext_regulator_cfg completely.
> And I
On Sat, Jan 24, 2015 at 10:18:05AM +0800, Lai Jiangshan wrote:
> On 01/23/2015 05:36 PM, Paul E. McKenney wrote:
> > On Thu, Jan 22, 2015 at 10:55:42PM -0800, Paul E. McKenney wrote:
> >> On Thu, Jan 22, 2015 at 11:05:45PM -0500, Sasha Levin wrote:
> >>> On 01/22/2015 11:02 PM, Sasha Levin wrote:
On Sat, Jan 24, 2015 at 09:03:20AM -0500, Tejun Heo wrote:
> printk and friends can now formap bitmaps using '%*pb[l]'. cpumask
> and nodemask also provide cpumask_pr_args() and nodemask_pr_args()
> respectively which can be used to generate the two printf arguments
> necessary to format the
> That's news for me. I thought they are silently ignored. Do you have an
> example of such a warning?
Not really. It was just assumption. It seems you are right, they are just
ignored silently. But item 2 is still relevant and it was actually confused
me when I tried to figure out MTD
New OMAP-based architectures (like OMAP5, DRA7XX, AM572X) don't have
LIMITEDADDRESS bit in GPMC_CONFIG register (this bit marked as
RESERVED). Seems like these SoCs have new revision of GPMC IP-core
(despite of same GPMC_REVISION value as for earlier SoCs).
According to OMAP5 TRM: "Nonmultiplexed
Fix sparse warning:
warning: symbol 'gpmc_cs_get_name' was not declared. Should it be static?
Signed-off-by: Semen Protsenko
---
drivers/memory/omap-gpmc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index
Some GPMC_CONFIG7 register bits marked as "RESERVED", means they
shouldn't be overwritten. A typical approach to handle such bits called
"Read-Modify-Write". Writing procedure used in gpmc_cs_set_memconf()
utilizes RMW technique, but implemented incorrectly. Due to obvious typo
in code read
Daniel, Matt,
On Sat, Jan 24, 2015 at 12:24:55PM +0100, Daniel Vetter wrote:
> On Fri, Jan 23, 2015 at 10:57:32PM -0800, Jeremiah Mahler wrote:
> > all,
> >
> > On Tue, Jan 20, 2015 at 06:48:42AM +0100, Daniel Vetter wrote:
> > > On Mon, Jan 19, 2015 at 08:40:24AM -0800, Matt Roper wrote:
> > >
Let me abuse this thread to ask more questions.
Peter, could you help?
On 01/23, Rik van Riel wrote:
>
> Not only is this broken with my new code, but it looks like it may
> be broken with the current code, too...
As I already mentioned, at least math_error()->save_init_fpu() looks
buggy. And
This patch fixes the following checkpatch.pl warning:
fix Prefer [subsystem eg: netdev]_info([subsystem]dev, ... then
dev_info(dev, ... then pr_info(... to printk(KERN_INFO ...
netdev_info was used since it is a network subsystem
Signed-off-by: Heba Aamer
---
On 24/01/15 01:48, Ong, Boon Leong wrote:
Skipping stuff I agree with.
From V1 comment:
Suggest to add a statement on 3 different types of IMR: General IMR, Host Memory
I/O Boundary IMR & System Management Mode IMR. Then, call out that this patch
is meant to support general IMR type only.
On 01/24/2015 12:48 PM, Daniel Church wrote:
> +#define DELAYTIMER_MAX_DEFAULT 100
Why did you chose 1 million?
Have you reviewed what constant userspace, particularly glibc, is using?
Cheers,
Carlos.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On 01/24/2015 02:20 PM, Thomas Gleixner wrote:
> On Sat, 24 Jan 2015, Daniel Church wrote:
>
>> POSIX.1-2001 specification of timer_getoverrun() supports constant
>> DELAYTIMER_MAX which prevents overflow and caps overrun count. Exposes
>> delaytimer_max value to userland via
On Fri, Jan 23, 2015 at 06:55:36PM +0530, Anshul Garg wrote:
> if (((long long)tmp < LLONG_MIN) || ((long long)tmp > LLONG_MAX) )
> + return -ERANGE;
This proposed code is still wrong (-ERANGE can never be returned by this
statement). It may be best to leave the code alone, rather than propose
On Fri, 23 Jan 2015, Jiang Liu wrote:
> 38 files changed, 65 insertions(+), 268 deletions(-)
Nice cleanup. If nobody yells, I'm going to route it through tip.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sat, 24 Jan 2015, Dmitry Eremin-Solenikov wrote:
> 2015-01-24 20:48 GMT+03:00 Thomas Gleixner :
> > On Thu, 15 Jan 2015, Dmitry Eremin-Solenikov wrote:
> >> static void sa1100_mask_irq(struct irq_data *d)
> >> {
> >> - ICMR &= ~BIT(d->hwirq);
> >> + u32 reg;
> >> + unsigned long
2015-01-24 22:24 GMT+03:00 Thomas Gleixner :
> On Sat, 24 Jan 2015, Dmitry Eremin-Solenikov wrote:
>
>> 2015-01-24 20:48 GMT+03:00 Thomas Gleixner :
>> > On Thu, 15 Jan 2015, Dmitry Eremin-Solenikov wrote:
>> >> static void sa1100_mask_irq(struct irq_data *d)
>> >> {
>> >> - ICMR &=
On Sat, 24 Jan 2015, Daniel Church wrote:
> POSIX.1-2001 specification of timer_getoverrun() supports constant
> DELAYTIMER_MAX which prevents overflow and caps overrun count. Exposes
> delaytimer_max value to userland via /proc/sys/kernel/delaytimer_max such
I know that you try to match the
On Sat, 24 Jan 2015, Daniel Church wrote:
> +/*
> + * Updates a timer's overrun count while capping it to delaytimer_max
> + */
> +static void posix_timer_update_overrun_count(struct k_itimer *timer,
> + unsigned int overruns)
> +{
> + const bool
This patch gets rid of the following error when compiling r8192U_core.c
and CONFIG_WIRELESS_EXT is not defined:
drivers/staging/rtl8192u/r8192U_core.c: In function ‘rtl8192_usb_probe’:
drivers/staging/rtl8192u/r8192U_core.c:4697:5: error: ‘struct net_device’ has
no member named
This patch consists of four real fixes and three MAINTAINER updates.
Three of the fixes are obvious (the DIX and atomic allocation are bug on
and warn on fixes and the other is just trivial) and the ipr one is a
bit more involved but is required because without it, the card double
completes
On Sat, Jan 24, 2015 at 12:48:56PM -0500, Daniel Church wrote:
> +/*
> + * Updates a timer's overrun count while capping it to delaytimer_max
> + */
> +static void posix_timer_update_overrun_count(struct k_itimer *timer,
> + unsigned int overruns)
> +{
> +
From: "Steven Rostedt (Red Hat)"
As tracefs may be mounted instead of debugfs to get to the event directories,
have perf know about tracefs, and use that file system over debugfs if it
is present.
Signed-off-by: Steven Rostedt
---
tools/perf/tests/open-syscall-all-cpus.c | 7 +++-
From: "Steven Rostedt (Red Hat)"
Since tracefs will now hold the event directory for perf, and
even though by default, debugfs still mounts tracefs on the
debugfs/tracing directory, the system admin may now choose to not
mount debugfs and instead just mount tracefs instead.
Having tracefs
As I'm trying to move the tracing directory from debugfs, perf needs to
be aware of this as system admins will now be able to mount the tracing
directory without needing to mount debugfs. This patch series addresses
this and makes perf aware of tracefs.
I based this series on a recent tip
From: "Steven Rostedt (Red Hat)"
In preparation for adding tracefs for perf to use, create a findfs
helper utility that find_debugfs uses instead of hard coding the search
in the code. This will allow for a find_tracefs to be used as well.
Signed-off-by: Steven Rostedt
---
From: "Steven Rostedt (Red Hat)"
Add tracefs_configured() to return true if tracefs is configured in the
kernel (/sys/kernel/tracing exists), and debugfs_configured() if debugfs
is configured in the kernel (/sys/kernel/debug exists).
Signed-off-by: Steven Rostedt
---
From: "Steven Rostedt (Red Hat)"
Instead of hard coding "/sys/kernel/debug" everywhere, create
a macro to hold where the default path exists.
Signed-off-by: Steven Rostedt
---
tools/lib/api/fs/debugfs.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
It's only user of the video_segment variable, so move it to video.c
Signed-off-by: Alexander Kuleshov
---
arch/x86/boot/video-mode.c | 4 +---
arch/x86/boot/video.c | 2 ++
arch/x86/boot/video.h | 1 -
3 files changed, 3 insertions(+), 4 deletions(-)
diff --git
On Mon, 19 Jan 2015, Geert Uytterhoeven wrote:
> Will you still do so, or shall I forward the patch to Andrew Morton?
akpm please.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
2015-01-24 20:48 GMT+03:00 Thomas Gleixner :
> On Thu, 15 Jan 2015, Dmitry Eremin-Solenikov wrote:
>> static void sa1100_mask_irq(struct irq_data *d)
>> {
>> - ICMR &= ~BIT(d->hwirq);
>> + u32 reg;
>> + unsigned long flags;
>> +
>> + raw_spin_lock_irqsave(, flags);
>
> What's the
If a timer overruns too many times before a call to timer_getoverrun the
overrun count can overflow and go negative. Adds delaytimer_max value
to cap overrun count and prevent overflow.
Signed-off-by: Daniel Church
---
include/linux/posix-timers.h | 3 +++
kernel/time/posix-timers.c | 45
If a timer overruns too many times before a call to timer_getoverrun the
overrun count can overflow and go negative. POSIX.1-2001 specification
of timer_getoverrun() supports constant DELAYTIMER_MAX which prevents
overflow and caps overrun count. Adds delaytimer_max value, caps
overrun count,
POSIX.1-2001 specification of timer_getoverrun() supports constant
DELAYTIMER_MAX which prevents overflow and caps overrun count. Exposes
delaytimer_max value to userland via /proc/sys/kernel/delaytimer_max such
that GLIBC can support DELAYTIMER_MAX constant.
Signed-off-by: Daniel Church
---
Acked-by: Christoph Lameter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 15 Jan 2015, Dmitry Eremin-Solenikov wrote:
> static void sa1100_mask_irq(struct irq_data *d)
> {
> - ICMR &= ~BIT(d->hwirq);
> + u32 reg;
> + unsigned long flags;
> +
> + raw_spin_lock_irqsave(, flags);
What's the exact point of that lock? And how is it related to the
The fbcon cursor, when set to blink, is hardcoded to toggle display state
five times per second. Expose this setting via
/sys/class/graphics/fbcon/cursor_blink_ms
Values written to the interface set the approximate time interval in
milliseconds between cursor toggles, from 1 to 32767. Since the
The fbcon cursor, when set to blink, is hardcoded to toggle display state
five times per second. Move this setting to a the driver's fbdev_ops
structure, retaining the default blink interval.
Signed-off-by: Scot Doyle
---
drivers/video/console/fbcon.c | 5 +++--
drivers/video/console/fbcon.h |
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix reboot issues with the imx2_wdt driver and it also
drops some forgotten owner assignments from platform_drivers.
This will update the following files:
cadence_wdt.c |1 -
On Thu, Jan 22, 2015 at 04:09:21PM -0800, John Stultz wrote:
> +static inline cycle_t timekeeping_get_delta(struct tk_read_base *tkr)
> +{
> + cycle_t cycle_now, delta;
> +
> + /* read clocksource */
> + cycle_now = tkr->read(tkr->clock);
> +
> + /* calculate the delta since the
2015-01-22 8:44 GMT+01:00 Lee Jones :
>
> Are you sure a struct is required at all now? It only contains a
> single bool after all.
Hi Lee
Okay, I will gladly remove ab8500_ext_regulator_cfg completely.
And I will try to update the comments, but since I'm not so familiar
with what this code
On Thu, 22 Jan 2015, Matthias Brugger wrote:
> 2015-01-13 14:12 GMT+01:00 Matthias Brugger :
> > 2015-01-12 10:14 GMT+01:00 Eddie Huang :
> >> From: Yingjoe Chen
> >>
> >> Originally mtk-sysirq hardcoded supported irq number to 224. This
> >> was fine since all SoCs before support the same number
Hi Thomas,
On Sat, 24 Jan 2015 17:37:48 +0100 (CET)
Thomas Gleixner wrote:
> On Fri, 23 Jan 2015, Boris Brezillon wrote:
> > - change the compatible string to clearly show that this chip is purely
> >virtual
>
> So we probably want to do : s/dumb/virt/ for both DT and code to make
> it
On Thu, 22 Jan 2015, Marc Zyngier wrote:
> On Tue, Jan 20 2015 at 4:52:59 pm GMT, Liviu Dudau
> wrote:
> > During a recent cleanup of the arm64 DTs it has become clear that
> > the handling of PPIs in _set_type() is incorrect. The ARM TRMs
> > for GICv2 and later allow for "implementation
On Sat, 24 Jan 2015, Xunlei Pang wrote:
> Before this, I tried to add some code to catch such problem at the
> time of registering the clocksource, like using the
> CLOCKSOURCE_MASK(), for example 64bit counter will never wrap for
> us. But there may be other values like CLOCKSOURCE_MASK(56), I
On Sat, 2015-01-24 at 18:33 +0200, Semen Protsenko wrote:
> This patch series removes next obsolete MTD configs from all defconfig files:
> - CONFIG_MTD_CHAR
> - CONFIG_MTD_CONCAT
> - CONFIG_MTD_DEBUG
> - CONFIG_MTD_DEBUG_VERBOSE
> - CONFIG_MTD_PARTITIONS
>
> All those configs were
On Fri, Jan 23, 2015 at 05:40:02PM -0500, Jérémie Galarneau wrote:
SNIP
> > bt_ctf_clock_create() with the checked name and then free it. However, it
> > is hacky
> > and I think you won't like it.
>
> The prospect of seeing that code has convinced me to introduce
> int
On Fri, 23 Jan 2015, Boris Brezillon wrote:
> - change the compatible string to clearly show that this chip is purely
>virtual
So we probably want to do : s/dumb/virt/ for both DT and code to make
it clear from the names as well.
Thanks,
tglx
--
To unsubscribe from this list: send
CONFIG_MTD_CHAR was removed from drivers/mtd/Kconfig by commit:
660685d9d1b4 "mtd: merge mtdchar module with mtdcore".
This patch finishes job by getting rid of CONFIG_MTD_CHAR in all
defconfig files.
Since CONFIG_MTD_CHAR was merged with CONFIG_MTD (see commit above),
it is harmless to remove
CONFIG_MTD_DEBUG and CONFIG_MTD_DEBUG_VERBOSE were removed from
drivers/mtd/Kconfig by commit:
87ed114bb22b "mtd: remove CONFIG_MTD_DEBUG"
This patch finishes job by getting rid of CONFIG_MTD_DEBUG* in all
defconfig files.
This patch is harmless for all modified defconfig files.
Signed-off-by:
CONFIG_MTD_CONCAT was removed from drivers/mtd/Kconfig by commit:
f53fdebcc3e1 "mtd: drop MTD_CONCAT from Kconfig entirely".
This patch finishes job by getting rid of CONFIG_MTD_CONCAT in all
defconfig files.
This patch is harmless for all modified defconfig files, because
MTD_CONCAT code is now
CONFIG_MTD_PARTITIONS was removed from drivers/mtd/Kconfig by commit:
6a8a98b22b10 "mtd: kill CONFIG_MTD_PARTITIONS".
This patch finishes job by getting rid of CONFIG_MTD_PARTITIONS in all
defconfig files.
This patch is harmless for all modified defconfig files, because
MTD_PARTITIONS code is
This patch series removes next obsolete MTD configs from all defconfig files:
- CONFIG_MTD_CHAR
- CONFIG_MTD_CONCAT
- CONFIG_MTD_DEBUG
- CONFIG_MTD_DEBUG_VERBOSE
- CONFIG_MTD_PARTITIONS
All those configs were removed from drivers/mtd/Kconfig earlier, but their usage
in defconfig files
On Fri, 23 Jan 2015, Daniel Church wrote:
> + overruns = (unsigned int) hrtimer_forward(timer,
> + timer->base->get_time(),
> + timr->it.real.interval);
> + if (overruns >= delaytimer_max ||
> +
On Sat, 24 Jan 2015, Torvald Riegel wrote:
> On Sat, 2015-01-24 at 11:05 +0100, Thomas Gleixner wrote:
> > On Fri, 23 Jan 2015, Torvald Riegel wrote:
> >
> > > On Fri, 2015-01-16 at 16:46 -0800, Darren Hart wrote:
> > > > On 1/16/15, 12:54 PM, "Michael Kerrisk (man-pages)"
> > > > wrote:
> > > >
On Fri, 23 Jan 2015, Sören Brinkmann wrote:
> On Mon, 2015-01-12 at 04:14PM +, Lorenzo Pieralisi wrote:
> > I thought that a shutdown clock event device explicitly disables IRQ
> > assertion, that's why I am inquiring, I do not understand how this
> > can happen - how can you have a pending
2015-01-23 1:47 GMT+09:00 Sylwester Nawrocki :
> Hi Chanwoo,
>
> On 21/01/15 07:26, Chanwoo Choi wrote:
>> This patch adds the support for CMU (Clock Management Units) of Exynos5433
>> which is 64bit SoC and has Octa-cores. This patch supports necessary clocks
>> (PLL/MMC/UART/MCT/I2C/SPI) for
Signed-off-by: Martin Kepplinger
---
Despite it's name, sign_extend32() is safe to use for 8 bit types
too. (see https://lkml.org/lkml/2015/1/18/289 if interested)
drivers/rtc/rtc-x1205.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-x1205.c
On Sat, 2015-01-24 at 15:39 +0100, Maxime Ripard wrote:
> Hi,
>
> On Fri, Jan 23, 2015 at 11:59:35PM +0200, Priit Laes wrote:
> >
> > On Fri, 2015-01-23 at 22:22 +0100, Maxime Ripard wrote:
> > > On Fri, Jan 23, 2015 at 10:36:49PM +0200, Priit Laes wrote:
> > > > Gemei G9 is an A10 based
On Sat, 24 Jan 2015, Alexey Khoroshilov wrote:
> oxu_qh_alloc() acquires oxu->mem_lock spinlock, finds free qh slot
> and calls ehci_qtd_alloc() to initialize qh->dummy, but
> ehci_qtd_alloc() acquires oxu->mem_lock as well.
> That means an unavoidable deadlock in oxu_qh_alloc().
>
> The patch
On Sat, Jan 24, 2015 at 2:19 AM, Scot Doyle wrote:
> +static ssize_t store_cursor_blink_ms(struct device *device,
> +struct device_attribute *attr,
> +const char *buf, size_t count)
> +{
...
> + unsigned long ms;
...
On Fri, 23 Jan 2015, Julius Werner wrote:
> The EHCI controller on the RK3288 SoC is violating basic parts of the
> USB spec and thereby unable to properly resume a suspended port. It does
> not start SOF generation within 3ms of finishing resume signaling, so
> the attached device will drop off
This patch aims to improve THP collapse rates, by allowing
THP collapse in the presence of read-only ptes, like those
left in place by do_swap_page after a read fault.
Currently THP can collapse 4kB pages into a THP when
there are up to khugepaged_max_ptes_none pte_none ptes
in a 2MB range. This
Am Donnerstag, 22. Januar 2015, 18:29:55 schrieb Mark Yao:
> drm dpms have many power modes, ON,OFF,SUSPEND,STANDBY, etc.
> but vop only have enable/disable mode, maybe case such bug:
> --> DRM_DPMS_ON: power on vop
> --> DRM_DPMS_SUSPEND: power off vop
> --> DRM_DPMS_OFF: already power off at
Am Donnerstag, 22. Januar 2015, 11:15:02 schrieb Mark Yao:
> Vop set wrong vsync/hsync polarity, it may cause some
> display problem. known problem is that caused HDMI hdcp
> authenticate failed, caused pixel offset with hdmi display.
> the polarity description at RK3288 TRM doc:
> dsp_vsync_pol
Em Fri, Jan 23, 2015 at 04:37:45PM -0600, Felipe Balbi escreveu:
> On Fri, Jan 23, 2015 at 05:59:59PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi escreveu:
> > > I'm using v3.19-rc5 on an ARM Cortex A9 board. Unfortunately, perf is
> > > not
Add entry Lubbock cplds driver into the pxa platform scope.
Signed-off-by: Robert Jarzmik
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddb9ac8..8c6a49d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7681,6 +7681,7 @@ T:git
1 - 100 of 368 matches
Mail list logo
