Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/arm/include/asm/Kbuild between commit 8a87411b649c ("ARM: 8047/1:
rwsem: use asm-generic rwsem implementation") from the arm tree and
commit bca74b3faf68 ("lib/scatterlist: make ARCH_HAS_SG_CHAIN an actual
Dear Email User,
This message is from the Database Information Technology Service Messaging
Center, to all our e-mail account users. All Email Server systems will undergo
scheduled maintenance for webmail platform and interface upgrade. Access to
your mailbox via our EMail Portal will be
On Sun, Jun 01, 2014 at 10:00:16AM +0200, Yann Droneaud wrote:
> Hi Dan,
>
> Le samedi 31 mai 2014 à 15:05 +0300, Dan Carpenter a écrit :
> > On Sat, May 31, 2014 at 10:01:39AM +0200, Yann Droneaud wrote:
> > > Le vendredi 30 mai 2014 à 23:10 +0300, Dan Carpenter a écrit :
> > > > This changelog
Hi all,
After merging the net-next tree, today's linux-next build (sparc64
defconfig) failed like this:
ERROR: "of_mdiobus_link_phydev" [drivers/net/phy/libphy.ko] undefined!
Caused by commit 86f6cf41272d ("net: of_mdio: add
of_mdiobus_link_phydev()") from te net-next tree.
CONFIG_PHYLIB=m for
Hi Linus,
I guess this can go into your desired "next" branch for v3.16 where
we start landing changes for the v3.16 merge window this week if
I understand your message correctly.
There is a lot of action in the GPIO subsystem doing refactorings
and cleanups, almost as many deletions as
On the 1st of June 2014 23:41, Daniel Phillips wrote:
Hi,
This is the first of four core changes we would like for Tux3. We
start with a hard one and suggest a simple solution.
The first patch in this series adds a new super operation to write
back multiple inodes in a single call. The second
On Mon, Jun 02, 2014 at 11:04:35AM +0300, Jani Nikula wrote:
> On Fri, 30 May 2014, Jet Chen wrote:
> > Hi Jesse,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://people.freedesktop.org/~jbarnes/linux async-fb-probe
>
> Do I understand correctly
On 06/02/2014 01:03 PM, Gautham R Shenoy wrote:
> Hi,
>
> On Tue, May 27, 2014 at 02:23:38AM +0530, Srivatsa S. Bhat wrote:
>
> [..snip..]
>>
>> Experimental results:
>>
>>
>> I ran a modified version of ebizzy (called 'sleeping-ebizzy') that sleeps in
>> between its
On Fri, May 30, 2014 at 06:17:49PM +0200, Stephen Warren wrote:
> On 05/30/2014 02:23 AM, Peter De Schrijver wrote:
> > On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
> >> On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
> >>> This driver allows userspace to read the raw efuse
Hi Bjorn,
Thanks for the patches.
> Lately I've been working on rpm, rpm-smd, smem, smd, smsm, smp2p
> patches for mainline.
> It could be argued that smd is a bus and should go in drivers/bus, but
> for the rest I fear that we just created drivers/soc/qcom as another
> dumping ground for
On Wednesday, May 28, 2014 5:26 AM, Christoffer Dall wrote:
> On Mon, May 12, 2014 at 06:40:44PM +0900, Jungseok Lee wrote:
> > This patch adds memory layout and translation lookup information about
> > 48-bit address space with 4K pages. The description is based on 4
> > levels of translation
On Tuesday, May 27, 2014 11:03 PM, Christoffer Dall wrote:
> On Tue, May 27, 2014 at 03:53:49PM +0200, Christoffer Dall wrote:
> > On Mon, May 12, 2014 at 06:40:54PM +0900, Jungseok Lee wrote:
> > > This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
> > > not compile time.
On Mon, Jun 02, 2014 at 02:14:47PM +0900, Daeseok Youn wrote:
> Adds a label for "kfree(brd)". And also remove
> a state value as BOARD_FAILED in brd when dgap_do_remap() is failed.
> Because "brd" will free after failure.
>
> Signed-off-by: Daeseok Youn
> Reviewed-by: Dan Carpenter
> ---
>
On Mon, Jun 02, 2014 at 02:08:24PM +0900, Daeseok Youn wrote:
> @@ -4177,12 +4183,46 @@ static int dgap_tty_register_ports(struct board_t
> *brd)
> brd->print_driver,
> brd->firstminor + i, NULL);
Btw, the
On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote:
> ubifs uses 64-bit integers for inode timestamps, which will work
> practicall forever, but the VFS uses struct timespec for timestamps,
> which is only good until 2038 on 32-bit CPUs.
>
> This gets us one small step closer to lifting the
On Tuesday, May 27, 2014 10:54 PM, Christoffer Dall wrote:
> On Mon, May 12, 2014 at 06:40:54PM +0900, Jungseok Lee wrote:
> > This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
> > not compile time.
> >
> > In ARMv8, EL2 physical address size (TCR_EL2.PS) and stage2 input
Am 01.06.2014 01:10, schrieb Rickard Strandqvist:
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
On the one hand it looks like a valid fix to me, but
Hi,
Johan Hovold:
> > > -USB OPTION-CARD DRIVER
> > > -M: Matthias Urlichs
> > > -L: linux-...@vger.kernel.org
> > > -S: Maintained
> > > -F: drivers/usb/serial/option.c
> >
> > Why are we taking away the maintainership of these individual drivers
> > from these
On Sun, Jun 01, 2014 at 11:05:39PM +0200, Rickard Strandqvist wrote:
> Hi Dan
>
> I agree, this looks strange.
> Have been looking for a while in history with, to see if the code has
> been removed. I start my search using cppcheck for over three months
> ago.
> But could not find anything. Sorry
Hi,
On Tue, May 27, 2014 at 02:23:38AM +0530, Srivatsa S. Bhat wrote:
[..snip..]
>
> Experimental results:
>
>
> I ran a modified version of ebizzy (called 'sleeping-ebizzy') that sleeps in
> between its execution such that its total utilization can be a user-defined
>
I have a battery operated android device. for charging I have a docking
station. to copy the images USB stick is attached to the docking station
while device is also inserted in docking station.
I have the following issue
when I power off the docking station my USB stick is not detected even
On Mon, Jun 02, 2014 at 02:03:58PM +0900, Daeseok Youn wrote:
> The dgap_probe1() function is just calling dgap_found_board().
> So it is removed and dgap_found_board() is called directly.
>
> Signed-off-by: Daeseok Youn
> ---
> RESEND : this patch is included into newly serise of patches
> so
We already have dummy implementation for most of the regulators APIs for
!CONFIG_REGULATOR case and were missing it for regulator_set_voltage_time().
Found this issue while compiling cpufreq-cpu0 driver without regulators support
in kernel.
drivers/cpufreq/cpufreq-cpu0.c: In function
This patch enables irqfd and irq routing on ARM.
It turns on CONFIG_HAVE_KVM_EVENTFD and CONFIG_HAVE_KVM_IRQ_ROUTING
irqfd framework enables to assign physical IRQs to guests.
1) user-side uses KVM_IRQFD VM ioctl to pass KVM a kvm_irqfd struct that
associates a VM, an eventfd, an IRQ number
cpufreq-cpu0 uses thermal framework to register a cooling device, but doesn't
depend on it as there are dummy calls provided by thermal layer when
CONFIG_THERMAL=n. And when these calls fail, the driver is still usable.
Similar explanation is valid for regulators as well. We do have dummy calls
Currently regulator_set_voltage() returns zero when support for regulators isn't
present in kernel, i.e. CONFIG_REGULATOR=n.
Make it return -EINVAL to propagate error instead of success here.
Audit of all users of this routine is done to make sure nothing breaks due to
this change.
Rickard Strandqvist wrote:
> From what I know, AND is faster then modulo.
Which is why the compiler does this optimization automatically,
if it can prove that it is correct.
> - if (i != 0 && (i%64) == 0)
> + if (i != 0 && (i&63) == 0)
Did you prove that i cannot be
On 28 May 2014 23:08, Mark Brown wrote:
> Whatever - I don't think the particular code makes any practical
> difference. We would need to audit existing users who don't have a
> REGULATOR dependency for breakage though.
I tried auditing all 29 files which had this symbol: regulator_set_voltage
On Sun, Jun 01, 2014 at 10:45:59AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Jun 01, 2014 at 11:32:17AM +0200, Johan Hovold wrote:
> > Remove the remaining two obsolete usb-serial subdriver entries from
> > MAINTAINERS, which were missed in the recent purge by commit
> > f896b7968b62 ("USB:
On Wed, May 28, 2014 at 06:52:56AM -0700, Guenter Roeck wrote:
> On 05/28/2014 06:29 AM, Guenter Roeck wrote:
> >On 05/28/2014 04:51 AM, Andreas Werner wrote:
> >>aOn Wed, May 28, 2014 at 09:24:05AM +0100, Lee Jones wrote:
> >>The MEN 14F021P00 Board Management Controller provides an
>
I'm not sure what I'm doing wrong.
These are my code.
770 #ifdef CONFIG_CMA
771 void adjust_managed_cma_page_count(struct zone *zone, long count)
772 {
773 unsigned long flags;
774 long total, cma, movable;
775
776 spin_lock_irqsave(>lock, flags);
777
778
Thanks Russell,
On 31/05/14 13:35, Russell King - ARM Linux wrote:
because allegedly it makes it more "readable". I don't see much benefit
to this patch.
Ok, I will drop this patch in next version.
thanks,
srini
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Sun, Jun 1, 2014 at 11:27 PM, Jingoo Han wrote:
> The site-specific OOM messages are unnecessary, because they
> duplicate the MM subsystem generic OOM message.
>
> Signed-off-by: Jingoo Han
> ---
> drivers/regulator/bcm590xx-regulator.c | 16
> 1 file changed, 4
From: Eric Dumazet
Date: Sun, 01 Jun 2014 22:13:12 -0700
> On Sun, 2014-06-01 at 21:56 -0700, David Miller wrote:
>
>> Indeed you have to provide a dummy version for a non-SMP build etc.
>>
>> I'm reverting.
>>
>
> Hi David. I think your revert took one wrong commit.
Thanks I'll fix it up.
On Mon, Jun 2, 2014 at 4:22 AM, Dave Chinner wrote:
> Filesystems place all sorts of userspace visible limits on storage -
> ever tried to create a file >16TB on ext4? The on-disk format
> doesn't support it, so it returns an out of range error (E2BIG, I
> think) if you try. XFS, OTOH, handles
Hello Naoya,
As Christoph noted, it would be best to provide some good user
documentation for this proposed system call, to aid design review.
Also, as per Documentation/SubmitChecklist, patches that change the
kernel-userspace API/ABI should CC
linux-...@vger.kernel.org (see
seccomp selects BPF only instead of whole NET
Other BPF users (like tracing filters) will select BPF only too
Signed-off-by: Alexei Starovoitov
---
arch/Kconfig |6 +-
kernel/Makefile |2 +-
kernel/bpf/core.c | 21 +
net/Kconfig |1 +
4 files
This patch set splits BPF out of core networking into generic component
patch #1 splits filter.c into two logical pieces: generic BPF core and socket
filters. It only moves functions around. No real changes.
patch #2 adds hidden CONFIG_BPF that seccomp/tracing can select
The main value of the
Enhance print messages for debugging purposes. Add a dev_err() whenever we fail
to initialize OPP table due to some error in the table present in dts and add a
dev_dbg() for success case.
Signed-off-by: Viresh Kumar
---
V4->V5: Fix rebase conflict as 2/8 has changed a bit
All callers of of_init_opp_table() are required to take reference of
dev->of_node, by initiating calls to of_node_{get|put}(), before and after
calling of_init_opp_table().
Its better to call these from within of_init_opp_table(), no fun adding
redundant code to every caller.
Signed-off-by:
On Monday, June 02, 2014 3:17 PM, Kishon Vijay Abraham I wrote:
> On Thursday 15 May 2014 09:31 PM, Murali Karicheri wrote:
> > This phy driver is used by keystone PCI driver. The hw vendor that
> > provides the phy hw published only registers and their values. So
> > this driver uses these hard
On Fri, May 30, 2014 at 02:50:11PM +0200, Jan Kasprzak wrote:
> Not sure whether I should ack my own patch, though. But you may apply
> it to the original one, which is identical to what I did.
> http://marc.info/?l=linux-scsi=139277202005675=2
Yes, that's what I will do.
Thanks a lot!
--
To
Please also provide a man page for the system call.
I'm also very unhappy about the crazy different interpretation of the
return value depending on flags, which probably becomes more obvious if
you try to document it.
That being said I think fincore is useful, but why not stick to the
same
On Thu, Apr 24, 2014 at 11:30:00AM -0400, Santosh Shilimkar wrote:
> Here is an updated v3 of the series. Series introduces support for setting up
> dma parameters based on device tree properties like 'dma-ranges' and
> 'dma-coherent' and also update to ARM 32 bit port. Earlier version of the
>
On 30 May 2014 04:11, Nishanth Menon wrote:
> The change so far is a improvement in error handling -> which,
> personally I find nice, but not necessarily related to the $subject or
> covered in commit message. I suggest splitting that specific change
> out as a patch of it's own.
I would be
Hi Alexander,
Today's linux-next merge of the kvm-ppc tree got a conflict in
include/uapi/linux/kvm.h between commit 717abd208dff ("KVM: Add
capability to advertise PSCI v0.2 support") from the kvm-arm tree and
commit f2e91042a807 ("KVM: PPC: Add CAP to indicate hcall fixes") from
the kvm-ppc
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/regulator/max8649.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/max8649.c
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/regulator/pbias-regulator.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/pbias-regulator.c
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han
---
drivers/regulator/bcm590xx-regulator.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git
On 05/29/2014 03:19 PM, Mark Rutland wrote:
> On Thu, May 29, 2014 at 10:43:05AM +0100, Michal Simek wrote:
>> Hi Mark,
>>
+static struct of_device_id cdns_wdt_of_match[] = {
+ { .compatible = "xlnx,zynq-wdt-r1p2", },
+ { .compatible = "cdns,wdt-r1p2", },
>>>
>>> If
On 05/29/2014 07:25 PM, Peter Zijlstra wrote:
> On Fri, May 23, 2014 at 05:53:05PM +0200, Vincent Guittot wrote:
>> The scheduler tries to compute how many tasks a group of CPUs can handle by
>> assuming that a task's load is SCHED_LOAD_SCALE and a CPU capacity is
>> SCHED_POWER_SCALE.
>> We can
On Mon, Jun 02, 2014 at 02:54:30PM +0900, Gioh Kim wrote:
> I found 2 problems at my platform.
>
> 1st is occured when I set CMA size 528MB and total memory is 960MB.
> I print some values in adjust_managed_cma_page_count(),
> the total value becomes 105439 and cma value 131072.
> Finally movable
Hi,
On Thursday 15 May 2014 09:31 PM, Murali Karicheri wrote:
> This phy driver is used by keystone PCI driver. The hw vendor that
> provides the phy hw published only registers and their values. So
> this driver uses these hard coded values to initialize the phy.
>
> CC: Grant Likely
> CC: Rob
On Sat, May 31, 2014 at 09:02:51AM +0900, Michal Nazarewicz wrote:
> > On Thu, May 29, 2014 at 05:09:34PM +0900, Gioh Kim wrote:
> >> Is IS_ENABLED(CONFIG_CMA) necessary?
> >> What about if (migratetype == MIGRATE_MOVABLE && zone->managed_cma_pages) ?
>
> On Fri, May 30 2014, Joonsoo Kim wrote:
* Oleg Nesterov [2014-06-01 21:25:20]:
> Purely cosmetic, no changes in .o,
>
> 1. As Jim pointed out arch_uprobe->def looks ambiguous, rename it to
>->dflt.
>
> 2. Add the comment into default_post_xol_op() to explain "regs->sp +=".
>
> 3. Remove the stale part of the comment in
Hi,
Please check below line comments.
2014-06-02 12:06 GMT+09:00 James A Shackleford :
> Signed-off-by: James A Shackleford
> ---
> drivers/staging/vt6655/baseband.c | 300
> ++---
> 1 file changed, 150 insertions(+), 150 deletions(-)
>
> diff --git
Hi,
Please check below line comments.
2014-06-02 12:06 GMT+09:00 James A Shackleford sh...@linux.com:
Signed-off-by: James A Shackleford sh...@linux.com
---
drivers/staging/vt6655/baseband.c | 300
++---
1 file changed, 150 insertions(+), 150 deletions(-)
* Oleg Nesterov o...@redhat.com [2014-06-01 21:25:20]:
Purely cosmetic, no changes in .o,
1. As Jim pointed out arch_uprobe-def looks ambiguous, rename it to
-dflt.
2. Add the comment into default_post_xol_op() to explain regs-sp +=.
3. Remove the stale part of the comment in
On Sat, May 31, 2014 at 09:02:51AM +0900, Michal Nazarewicz wrote:
On Thu, May 29, 2014 at 05:09:34PM +0900, Gioh Kim wrote:
Is IS_ENABLED(CONFIG_CMA) necessary?
What about if (migratetype == MIGRATE_MOVABLE zone-managed_cma_pages) ?
On Fri, May 30 2014, Joonsoo Kim
Hi,
On Thursday 15 May 2014 09:31 PM, Murali Karicheri wrote:
This phy driver is used by keystone PCI driver. The hw vendor that
provides the phy hw published only registers and their values. So
this driver uses these hard coded values to initialize the phy.
CC: Grant Likely
On Mon, Jun 02, 2014 at 02:54:30PM +0900, Gioh Kim wrote:
I found 2 problems at my platform.
1st is occured when I set CMA size 528MB and total memory is 960MB.
I print some values in adjust_managed_cma_page_count(),
the total value becomes 105439 and cma value 131072.
Finally movable value
On 05/29/2014 03:19 PM, Mark Rutland wrote:
On Thu, May 29, 2014 at 10:43:05AM +0100, Michal Simek wrote:
Hi Mark,
+static struct of_device_id cdns_wdt_of_match[] = {
+ { .compatible = xlnx,zynq-wdt-r1p2, },
+ { .compatible = cdns,wdt-r1p2, },
If these can currently be handled
On 05/29/2014 07:25 PM, Peter Zijlstra wrote:
On Fri, May 23, 2014 at 05:53:05PM +0200, Vincent Guittot wrote:
The scheduler tries to compute how many tasks a group of CPUs can handle by
assuming that a task's load is SCHED_LOAD_SCALE and a CPU capacity is
SCHED_POWER_SCALE.
We can now have a
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/regulator/bcm590xx-regulator.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/regulator/pbias-regulator.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/regulator/max8649.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/max8649.c
Hi Alexander,
Today's linux-next merge of the kvm-ppc tree got a conflict in
include/uapi/linux/kvm.h between commit 717abd208dff (KVM: Add
capability to advertise PSCI v0.2 support) from the kvm-arm tree and
commit f2e91042a807 (KVM: PPC: Add CAP to indicate hcall fixes) from
the kvm-ppc tree.
On 30 May 2014 04:11, Nishanth Menon n...@ti.com wrote:
The change so far is a improvement in error handling - which,
personally I find nice, but not necessarily related to the $subject or
covered in commit message. I suggest splitting that specific change
out as a patch of it's own.
I would
On Thu, Apr 24, 2014 at 11:30:00AM -0400, Santosh Shilimkar wrote:
Here is an updated v3 of the series. Series introduces support for setting up
dma parameters based on device tree properties like 'dma-ranges' and
'dma-coherent' and also update to ARM 32 bit port. Earlier version of the
series
Please also provide a man page for the system call.
I'm also very unhappy about the crazy different interpretation of the
return value depending on flags, which probably becomes more obvious if
you try to document it.
That being said I think fincore is useful, but why not stick to the
same
On Fri, May 30, 2014 at 02:50:11PM +0200, Jan Kasprzak wrote:
Not sure whether I should ack my own patch, though. But you may apply
it to the original one, which is identical to what I did.
http://marc.info/?l=linux-scsim=139277202005675w=2
Yes, that's what I will do.
Thanks a lot!
--
To
On Monday, June 02, 2014 3:17 PM, Kishon Vijay Abraham I wrote:
On Thursday 15 May 2014 09:31 PM, Murali Karicheri wrote:
This phy driver is used by keystone PCI driver. The hw vendor that
provides the phy hw published only registers and their values. So
this driver uses these hard coded
All callers of of_init_opp_table() are required to take reference of
dev-of_node, by initiating calls to of_node_{get|put}(), before and after
calling of_init_opp_table().
Its better to call these from within of_init_opp_table(), no fun adding
redundant code to every caller.
Signed-off-by:
Enhance print messages for debugging purposes. Add a dev_err() whenever we fail
to initialize OPP table due to some error in the table present in dts and add a
dev_dbg() for success case.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
V4-V5: Fix rebase conflict as 2/8 has changed a bit
This patch set splits BPF out of core networking into generic component
patch #1 splits filter.c into two logical pieces: generic BPF core and socket
filters. It only moves functions around. No real changes.
patch #2 adds hidden CONFIG_BPF that seccomp/tracing can select
The main value of the
seccomp selects BPF only instead of whole NET
Other BPF users (like tracing filters) will select BPF only too
Signed-off-by: Alexei Starovoitov a...@plumgrid.com
---
arch/Kconfig |6 +-
kernel/Makefile |2 +-
kernel/bpf/core.c | 21 +
net/Kconfig |
Hello Naoya,
As Christoph noted, it would be best to provide some good user
documentation for this proposed system call, to aid design review.
Also, as per Documentation/SubmitChecklist, patches that change the
kernel-userspace API/ABI should CC
linux-...@vger.kernel.org (see
On Mon, Jun 2, 2014 at 4:22 AM, Dave Chinner da...@fromorbit.com wrote:
Filesystems place all sorts of userspace visible limits on storage -
ever tried to create a file 16TB on ext4? The on-disk format
doesn't support it, so it returns an out of range error (E2BIG, I
think) if you try. XFS,
From: Eric Dumazet eric.duma...@gmail.com
Date: Sun, 01 Jun 2014 22:13:12 -0700
On Sun, 2014-06-01 at 21:56 -0700, David Miller wrote:
Indeed you have to provide a dummy version for a non-SMP build etc.
I'm reverting.
Hi David. I think your revert took one wrong commit.
Thanks I'll
On Sun, Jun 1, 2014 at 11:27 PM, Jingoo Han jg1@samsung.com wrote:
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/regulator/bcm590xx-regulator.c | 16
Thanks Russell,
On 31/05/14 13:35, Russell King - ARM Linux wrote:
because allegedly it makes it more readable. I don't see much benefit
to this patch.
Ok, I will drop this patch in next version.
thanks,
srini
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
I'm not sure what I'm doing wrong.
These are my code.
770 #ifdef CONFIG_CMA
771 void adjust_managed_cma_page_count(struct zone *zone, long count)
772 {
773 unsigned long flags;
774 long total, cma, movable;
775
776 spin_lock_irqsave(zone-lock, flags);
777
778
On Wed, May 28, 2014 at 06:52:56AM -0700, Guenter Roeck wrote:
On 05/28/2014 06:29 AM, Guenter Roeck wrote:
On 05/28/2014 04:51 AM, Andreas Werner wrote:
aOn Wed, May 28, 2014 at 09:24:05AM +0100, Lee Jones wrote:
The MEN 14F021P00 Board Management Controller provides an
I2C interface to the
On Sun, Jun 01, 2014 at 10:45:59AM -0700, Greg Kroah-Hartman wrote:
On Sun, Jun 01, 2014 at 11:32:17AM +0200, Johan Hovold wrote:
Remove the remaining two obsolete usb-serial subdriver entries from
MAINTAINERS, which were missed in the recent purge by commit
f896b7968b62 (USB: Maintainers
On 28 May 2014 23:08, Mark Brown broo...@kernel.org wrote:
Whatever - I don't think the particular code makes any practical
difference. We would need to audit existing users who don't have a
REGULATOR dependency for breakage though.
I tried auditing all 29 files which had this symbol:
Rickard Strandqvist wrote:
From what I know, AND is faster then modulo.
Which is why the compiler does this optimization automatically,
if it can prove that it is correct.
- if (i != 0 (i%64) == 0)
+ if (i != 0 (i63) == 0)
Did you prove that i cannot be negative?
Currently regulator_set_voltage() returns zero when support for regulators isn't
present in kernel, i.e. CONFIG_REGULATOR=n.
Make it return -EINVAL to propagate error instead of success here.
Audit of all users of this routine is done to make sure nothing breaks due to
this change.
cpufreq-cpu0 uses thermal framework to register a cooling device, but doesn't
depend on it as there are dummy calls provided by thermal layer when
CONFIG_THERMAL=n. And when these calls fail, the driver is still usable.
Similar explanation is valid for regulators as well. We do have dummy calls
This patch enables irqfd and irq routing on ARM.
It turns on CONFIG_HAVE_KVM_EVENTFD and CONFIG_HAVE_KVM_IRQ_ROUTING
irqfd framework enables to assign physical IRQs to guests.
1) user-side uses KVM_IRQFD VM ioctl to pass KVM a kvm_irqfd struct that
associates a VM, an eventfd, an IRQ number
We already have dummy implementation for most of the regulators APIs for
!CONFIG_REGULATOR case and were missing it for regulator_set_voltage_time().
Found this issue while compiling cpufreq-cpu0 driver without regulators support
in kernel.
drivers/cpufreq/cpufreq-cpu0.c: In function
On Mon, Jun 02, 2014 at 02:03:58PM +0900, Daeseok Youn wrote:
The dgap_probe1() function is just calling dgap_found_board().
So it is removed and dgap_found_board() is called directly.
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
---
RESEND : this patch is included into newly serise
I have a battery operated android device. for charging I have a docking
station. to copy the images USB stick is attached to the docking station
while device is also inserted in docking station.
I have the following issue
when I power off the docking station my USB stick is not detected even
Hi,
On Tue, May 27, 2014 at 02:23:38AM +0530, Srivatsa S. Bhat wrote:
[..snip..]
Experimental results:
I ran a modified version of ebizzy (called 'sleeping-ebizzy') that sleeps in
between its execution such that its total utilization can be a user-defined
value, say
On Sun, Jun 01, 2014 at 11:05:39PM +0200, Rickard Strandqvist wrote:
Hi Dan
I agree, this looks strange.
Have been looking for a while in history with, to see if the code has
been removed. I start my search using cppcheck for over three months
ago.
But could not find anything. Sorry about
Hi,
Johan Hovold:
-USB OPTION-CARD DRIVER
-M: Matthias Urlichs sm...@smurf.noris.de
-L: linux-...@vger.kernel.org
-S: Maintained
-F: drivers/usb/serial/option.c
Why are we taking away the maintainership of these individual drivers
from these
Am 01.06.2014 01:10, schrieb Rickard Strandqvist:
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
On the one
On Tuesday, May 27, 2014 10:54 PM, Christoffer Dall wrote:
On Mon, May 12, 2014 at 06:40:54PM +0900, Jungseok Lee wrote:
This patch sets TCR_EL2.PS, VTCR_EL2.T0SZ and vttbr_baddr_mask in runtime,
not compile time.
In ARMv8, EL2 physical address size (TCR_EL2.PS) and stage2 input address
On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote:
ubifs uses 64-bit integers for inode timestamps, which will work
practicall forever, but the VFS uses struct timespec for timestamps,
which is only good until 2038 on 32-bit CPUs.
This gets us one small step closer to lifting the VFS
On Mon, Jun 02, 2014 at 02:08:24PM +0900, Daeseok Youn wrote:
@@ -4177,12 +4183,46 @@ static int dgap_tty_register_ports(struct board_t
*brd)
brd-print_driver,
brd-firstminor + i, NULL);
Btw, the brd-firstminor + i
On Mon, Jun 02, 2014 at 02:14:47PM +0900, Daeseok Youn wrote:
Adds a label for kfree(brd). And also remove
a state value as BOARD_FAILED in brd when dgap_do_remap() is failed.
Because brd will free after failure.
Signed-off-by: Daeseok Youn daeseok.y...@gmail.com
Reviewed-by: Dan Carpenter
801 - 900 of 1712 matches
Mail list logo
