On Fri, May 31, 2013 at 12:33:04PM -0600, Stephen Warren wrote:
> From: Stephen Warren
>
> Previously, the #line parsing regex ended with ({WS}+[0-9]+)?. The {WS}
> could match line-break characters. If the #line directive did not contain
> the optional flags field at the end, this could cause
Hi Arnd,
On Fri, May 31, 2013 at 3:22 PM, Arnd Bergmann wrote:
> This makes sure the conditionals for the declaration match the
> definition, so we provide the alternative
>
> #else
> #define IL_LEGACY_PM_OPS NULL
> #endif
>
> in the correct cases. As suggested by Borislav Petkov, this
Another question...
Should the core pstore fail to unlink partitions that don't have
an ->erase callback ? IE. Why would you let anyone erase the OFW
common partition for example ? That means that userspace tools
can no longer manipulate it but we certainly don't want to remove
it from the nvram
On Mon, May 27, 2013 at 10:13:09PM -0600, Stephen Warren wrote:
> On 05/26/2013 09:53 PM, Alexandre Courbot wrote:
> > The naming scheme of simplefb's mode is precise enough to allow building
> > the mode structure from it instead of using a static list of modes. This
> > patch introduces a
On Fri, 2013-04-26 at 15:26 +0530, Aruna Balakrishnaiah wrote:
> The patch set supports compression of oops messages while writing to NVRAM,
> this helps in capturing more of oops data to lnx,oops-log. The pstore file
> for oops messages will be in decompressed format making it readable.
>
> In
On Tue, 2013-05-28 at 15:45 +0200, Jiri Kosina wrote:
> I'd be glad if you could provide your Tested-by: for the patch below.
> Thanks a lot.
I tried to test this tonight, but was thwarted by Fedora 16 on the only
readily available test platform -- old bluetoothd w/ the internal
driver. I'll
On Thu, 2013-04-25 at 15:49 +0530, Aruna Balakrishnaiah wrote:
> diff --git a/fs/pstore/inode.c b/fs/pstore/inode.c
> index 8d4fb65..88cc050 100644
> --- a/fs/pstore/inode.c
> +++ b/fs/pstore/inode.c
> @@ -330,6 +330,9 @@ int pstore_mkfile(enum pstore_type_id type, char *psname,
> u64 id, int
On Sat, 2013-06-01 at 14:49 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2013-04-25 at 15:48 +0530, Aruna Balakrishnaiah wrote:
> > This patch set exploits the pstore subsystem to read details of rtas
> > partition
> > in NVRAM to a separate file in /dev/pstore. For instance, rtas details will
On Thu, 2013-04-25 at 15:48 +0530, Aruna Balakrishnaiah wrote:
> This patch set exploits the pstore subsystem to read details of rtas partition
> in NVRAM to a separate file in /dev/pstore. For instance, rtas details will be
> stored in a file named [rtas-nvram-4].
>
.../...
> diff --git
On Sat, 2013-06-01 at 14:40 +1000, Benjamin Herrenschmidt wrote:
.../...
> In fact, this applies to at least all the BookS server platforms...
>
> Things that come to mind:
>
> - nvram_64.c duplicates generic_nvram.c as far as the user accessors
> are concerned, it should be possible to get
On Fri, May 31, 2013 at 11:20:59PM -0500, Russ Anderson wrote:
> And when QueryVariableInfo reports insufficient space, don't write
> and everything is fine.
And then installs fail, which is why we implemented this additional
code.
> But when QueryVariableInfo reports insufficient space and
On Thu, 2013-04-25 at 15:47 +0530, Aruna Balakrishnaiah wrote:
> Currently the kernel provides the contents of p-series NVRAM only as a
> simple stream of bytes via /dev/nvram, which must be interpreted in user
> space by the nvram command in the powerpc-utils package. This patch set
> exploits
On Sat, Jun 01, 2013 at 01:03:11AM +0100, Matthew Garrett wrote:
> On Fri, May 31, 2013 at 05:57:31PM -0500, Russ Anderson wrote:
> > On Fri, May 31, 2013 at 05:28:16PM +0100, Matthew Garrett wrote:
> > > If nvram becaomes full, some
> > > systems crash
On Fri, May 31, 2013 at 02:55:19PM +0200, Johannes Thumshirn wrote:
> Hi Guenther,
> On Fri, May 31, 2013 at 04:40:37AM -0700, Guenter Roeck wrote:
> > > +#define GPIO_WD_ENAB 169
> > > +#define GPIO_WD_FAST 170
> > > +#define GPIO_WD_TRIG 171
> > > +
> > > +#define GPIO_RST_CAUSE_BASE
On Wednesday, November 14, 2040 8:27 PM, Shuah Khan wrote:
>
> Convert drivers/video/backlight/class to use dev_pm_ops for power
> management and remove Legacy PM ops hooks. With this change, rtc class
There is still the typo.
Please fix it.
rtc class -> backlight class
> registers
Use the more common pkt_dbg(level, fmt, ...) form.
These messages are emitted at KERN_NOTICE.
Always emit function name with pkt_dbg(2, ...) uses and
remove the sometimes abbreviated embedded function name.
This form always verifies the format and arguments.
Signed-off-by: Joe Perches
---
Add pd->name to output for these debugging messages.
Remove normally compiled out pkt_dbg(2, ...) function entry
tracing equivalents as it's better done via the function tracer.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 90 +++--
1
Add a new pkt_err macro to prefix the name to the logging output.
Convert pr_err where there is a non-null struct pktcdvd_device.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 44
1 file changed, 24 insertions(+), 20 deletions(-)
diff
Allow the device name to be emitted with pkt_err when
logging the sense data.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 31 ---
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
index
Use a more current logging style and add messages levels
to the logging messages.
Simplify pkt_dump_sense by using %*ph and adding a simple
function to emit the sense string.
Signed-off-by: Joe Perches
Improved-by: Andy Shevchenko
---
drivers/block/pktcdvd.c | 123
Add a new pkt_info macro to prefix the name to the logging output.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
index 3815f01..995d688 100644
---
Add a new pkt_notice macro to prefix the name to the logging output.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 32 +---
1 file changed, 17 insertions(+), 15 deletions(-)
diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
index
Removed the compile error the patch 1 and compile fix in 2
Added Andy's suggestion in patch 2.
Added conversions to print pd->name in logging macros.
Joe Perches (8):
pktcdvd: Convert ZONE macro to static function get_zone()
pktcdvd: Convert printk to pr_
pktcdvd: Consolidate DPRINTK and
Macros should be converted to functions where feasible to
verify arguments and the like.
Signed-off-by: Joe Perches
---
drivers/block/pktcdvd.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
index
On Wednesday, November 14, 2040 8:02 PM, Shuah Khan wrote:
>
> Convert drivers/video/backlight/class to use dev_pm_ops for power
> management and remove Legacy PM ops hooks. With this change, rtc class
No, this is a backlight class, not rtc class.
Please fix the typo as below:
rtc class ->
On Fri, May 31, 2013 at 05:19:03PM +0530, Tushar Behera wrote:
> For mach-exynos, uart_base is a pointer and the value is calculated
> in the machine folder. For other machines, uart_base is defined as
> a macro in platform directory. For symmetry, the uart_base macro
> definition is removed and
On Fri, May 31, 2013 at 05:19:02PM +0530, Tushar Behera wrote:
> Printing low-level debug messages make an assumption that the specified
> UART port has been preconfigured by the bootloader. Incorrectly
> specified UART port results in system getting stalled while printing the
> message
Convert drivers/video/backlight/class to use dev_pm_ops for power
management and remove Legacy PM ops hooks. With this change, rtc class
registers suspend/resume callbacks via class->pm (dev_pm_ops) instead of
Legacy class->suspend/resume. When __device_suspend() runs call-backs,
it will find
Convert drivers/video/backlight/class to use dev_pm_ops for power
management and remove Legacy PM ops hooks. With this change, rtc class
registers suspend/resume callbacks via class->pm (dev_pm_ops) instead of
Legacy class->suspend/resume. When __device_suspend() runs call-backs,
it will find
Hi Doug,
Looks good to me.
On 1 June 2013 00:28, Doug Anderson wrote:
> The KDIV value is often listed as unsigned but it needs to be treated
> as a 16-bit signed value when using it in calculations. Fix our rate
> recalculation to do this correctly.
>
> Before doing this, I tried setting EPLL
Having a global lock that protects all of this code is a clear
scalability problem. Instead of doing that, move most of the code to be
protected by the i_lock instead.
The exceptions are the global lists that file_lock->fl_link sits on.
Those still need a global lock of some sort, so wrap just
There's no reason we have to protect the blocked_hash and file_lock_list
with the same spinlock. With the tests I have, breaking it in two gives
a barely measurable performance benefit, but it seems reasonable to make
this locking as granular as possible.
Signed-off-by: Jeff Layton
---
Move the fl_link list handling routines into a separate set of helpers.
Also move the global list handling out of locks_insert_block, and into
the caller that ends up triggering it as that allows us to eliminate the
IS_POSIX check there.
Signed-off-by: Jeff Layton
---
fs/locks.c | 34
Break up the blocked_list into a hashtable, using the fl_owner as a key.
This speeds up searching the hash chains, which is especially significant
for deadlock detection.
Note that the initial implementation assumes that hashing on fl_owner is
sufficient. In most cases it should be, with the
...save 3 bytes of stack space.
Signed-off-by: Jeff Layton
---
fs/locks.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index a7d2253..cef0e04 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -800,7 +800,8 @@ static int
Currently, when there is a lot of lock contention the kernel spends an
inordinate amount of time taking blocked locks off of the global
blocked_list and then putting them right back on again. When all of this
code was protected by a single lock, then it didn't matter much, but now
it means a lot
Signed-off-by: Dongjin Kim
On Sat, Jun 1, 2013 at 10:34 AM, Julius Werner wrote:
> Remove an erroneous tab that should be a space.
>
> Signed-off-by: Julius Werner
> ---
> drivers/usb/misc/usb3503.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Executive summary (tl;dr version): This patchset represents an overhaul
of the file locking code with an aim toward improving its scalability
and making the code a bit easier to understand.
Longer version:
When the BKL was finally ripped out of the kernel in 2010, the strategy
taken for the file
Signed-off-by: Jeff Layton
---
fs/locks.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index 7a02064..e3140b8 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1337,7 +1337,7 @@ int fcntl_getlease(struct file *filp)
return type;
}
-int
Signed-off-by: Dongjin Kim
On Sat, Jun 1, 2013 at 10:34 AM, Julius Werner wrote:
> The usb3503 driver sleeps a flat 100ms when resetting the chip, with a
> comment about waiting for the reference clock. This seems to be a
> board-specific detail that should not hold up boot across all
commit 66189be74 (CIFS: Fix VFS lock usage for oplocked files) exported
the locks_delete_block symbol. There's already an exported helper
function that provides this capability however, so make cifs use that
instead and turn locks_delete_block back into a static function.
Note that if fl->fl_next
Currently, the hashing that the locking code uses to add these values
to the blocked_hash is simply calculated using fl_owner field. That's
valid in most cases except for server-side lockd, which validates the
owner of a lock based on fl_owner and fl_pid.
In the case where you have a small number
Testing has shown that iterating over the blocked_list for deadlock
detection turns out to be a bottleneck. In order to alleviate that,
begin the process of turning it into a hashtable. We start by turning
the fl_link into a hlist_node and the global lists into hlists. A later
patch will do the
Signed-off-by: Jeff Layton
---
fs/locks.c | 24 +++-
include/linux/fs.h |6 ++
2 files changed, 25 insertions(+), 5 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index e3140b8..a7d2253 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -150,6 +150,16 @@ static
Hi,
I have sent two patches for the same issue, these two are merged into
Greg's tree. Please review the patches.
[1] https://patchwork.kernel.org/patch/2599021
[2] https://patchwork.kernel.org/patch/2599031
Many thanks,
Dongjin.
On Sat, Jun 1, 2013 at 10:34 AM, Julius Werner wrote:
> The
2013/5/31 Julius Werner :
> This patch set contains a few minor changes to the recently added SMSC
> USB3503 driver. It addresses issues that seem to be either left-over
> stopgaps from an early development stage or board-specific hacks,
> changing them to defaults that should be most sane and
File No: Ref NO.: XYL/26510460037/06
Names:.
Tel/Mobile:
Address:...
Country:...
Age:
Congratulation once again,
Dr.Jones Green
Email: inf.gre...@hotmail.co.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 1 June 2013 03:52, Arnd Bergmann wrote:
> Like a lot of the other cpufreq drivers, this one needs to
> select CONFIG_CPU_FREQ_TABLE to avoid a build error like
>
> drivers/built-in.o: In function `spear_cpufreq_exit':
> spear-cpufreq.c:198: undefined reference to
Remove an erroneous tab that should be a space.
Signed-off-by: Julius Werner
---
drivers/usb/misc/usb3503.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/usb3503.c b/drivers/usb/misc/usb3503.c
index d3a1cce..73aeb87 100644
--- a/drivers/usb/misc/usb3503.c
The usb3503 driver sleeps a flat 100ms when resetting the chip, with a
comment about waiting for the reference clock. This seems to be a
board-specific detail that should not hold up boot across all platforms.
This patch reduces the sleep to the 4ms initialization delay that the
chip itself
The usb3503 driver currently disables port 2 and 3 without explaination.
It doesn't make sense to do this in a mainline Linux driver that should
support all platforms which use this chip. If specific use cases really
require ports to be disabled, this should either be done through local
patches or
This patch set contains a few minor changes to the recently added SMSC
USB3503 driver. It addresses issues that seem to be either left-over
stopgaps from an early development stage or board-specific hacks,
changing them to defaults that should be most sane and useable for all
platforms that
On 5/30/2013 3:24 PM, Arnd Bergmann wrote:
+ if (size > ((phys_addr_t)~0))
+ size = ((phys_addr_t)~0);
+
+ /* arm_add_memory() already checks for the case of base + size > 4GB */
+#endif
arm_add_memory(base, size);
}
This looks wrong for the case where
Dave Jones hit the following bug report:
===
[ INFO: suspicious RCU usage. ]
3.10.0-rc2+ #1 Not tainted
---
include/linux/rcupdate.h:771 rcu_read_lock() used illegally while idle!
other info that might help us debug this:
RCU used
On Fri, May 31, 2013 at 06:30:39PM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 31 May 2013, Andreas Herrmann wrote:
> > On Fri, May 31, 2013 at 01:26:49AM -0300, Henrique de Moraes Holschuh wrote:
> > > On Thu, 30 May 2013, Jacob Shin wrote:
> > > > mkdir initrd
> > > > cd initrd
> > > >
File No: Ref NO.: XYL/26510460037/06
Names:.
Tel/Mobile:
Address:...
Country:...
Age:
Congratulation once again,
Dr.Jones Green
Email: inf.gre...@hotmail.co.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
This adds in a new message to the wakeup code which adds an indication to
the log that suspend was cancelled due to a wake event occouring during
the suspend sequence. It also adjusts the message printed in suspend.c to
reflect the potential that a suspend was aborted, as opposed to a device
Hi Linus,
The following changes since commit 83c168bf8017212a9d502536f9dcd0b54d24e330:
NFS: Fix SETCLIENTID fallback if GSS is not available (2013-05-23 18:50:40
-0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.10-4
for
From: Philip J Kelleher
Giving all interrupt based events their own workqueue to complete
tasks on.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block/Documentation/dontdiff
All,
Geert ,
The related git number:
for parport.h: "4914802 m68k,m68knommu: merge header files" in 2009
for io_mm.h: "84b16b7 m68k/atari: ROM port ISA adapter support" in
Apr 6 2013
The related warning (make EXTRA_CFLAG=-W ARCH=m68k allmodconfig):
From: Philip J Kelleher
Before the partition table would have to be reread because our
card was attached before it transistioned out of it's 'starting'
state.
This change will wait until the card has transitioned from it's
'starting' state before it will attach the device. This way there
is no
From: Philip J Kelleher
Adding debugfs entries to help with debugging and testing and
testing code.
pci_regs:
This entry will spit out all of the data stored on the BAR.
stats:
This entry will display all of the driver stats for each
DMA channel.
Signed-off-by: Philip
From: Haiyang Zhang
Date: Tue, 28 May 2013 09:15:56 -0700
> Since the recent addition of 8021AD, we need to set the new field vlan_proto
> in
> sk_buff. Otherwise, it will trigger BUG() call in vlan_proto_idx().
>
> This patch fixes the problem.
>
> Signed-off-by: Haiyang Zhang
>
From: Philip J Kelleher
The block size was determined by whether or not our HW could handle
512 accesses or not. So our configuration utility was not able to
change the block size because all of our newer HW can handle 512
accesses.
This patch allows block sizes to be determined by what is
From: Philip J Kelleher
The RHEL 6.x version of the driver is using the legacy
workqueue create function, 'create_singlethread_workqueue'.
This would cause heavy usage of one CPU if data was being
thrashed pretty hard. So, in order to fix it, workqueues
are now being created with
From: Philip J Kelleher
Unfortunaly, our CPU register path does not do any kind of
EEH error checking. So to fix this issue, an ioread32 was
added to the CPU register timeout code. This way, the
driver can check to see if the timeout was caused by an EEH
error or not. This is a dummy read.
From: Philip J Kelleher
Before DMAs would never be cancelled if the data stall or
EEH Permenant failure occured.
The DMA cancellation mechanism has been modified to fix
these issues and allows DMAs to be cancelled whenever they
should be.
Signed-off-by: Philip J Kelleher
From: Philip J Kelleher
Fixing incorrect stats calculation during read retries.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block/Documentation/dontdiff
linux-block-vanilla/drivers/block/rsxx/dma.c
Geert ,
The related git number:
for parport.h: "4914802 m68k,m68knommu: merge header files" in 2009
for io_mm.h: "84b16b7 m68k/atari: ROM port ISA adapter support" in Apr 6 2013
The related warning (make EXTRA_CFLAG=-W ARCH=m68k allmodconfig):
arch/m68k/include/asm/parport.h:14:0:
From: Maxime Ripard
Date: Thu, 30 May 2013 15:49:19 +0200
> The Allwinner A10 SoC has an ethernet controller that seem to be specific to
> Allwinner. This IP has no public documentation, so exact
> details are quite sparse, and this code come from refactored Allwinner
> code.
>
> The rework to
MSM_TLMM_BASE is currently not mapped by 8x60. Remove it.
Signed-off-by: Rohit Vaswani
---
arch/arm/mach-msm/include/mach/msm_iomap-8x60.h |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-msm/include/mach/msm_iomap-8x60.h
This cleans up the gpio-msm-v2 driver of all the global define usage.
The number of gpios are now defined in the device tree. This enables
adding irqdomain support as well.
Signed-off-by: Rohit Vaswani
---
.../devicetree/bindings/gpio/gpio-msm.txt | 26 +++
Remove gpiomux-v2 as it's not being used and make way for future improvements.
Signed-off-by: Rohit Vaswani
---
arch/arm/mach-msm/Kconfig| 13 +++-
arch/arm/mach-msm/Makefile |6 +--
arch/arm/mach-msm/gpiomux-8x60.c | 19
arch/arm/mach-msm/gpiomux-v2.c |
v4:
for gpio-msm-v2 patch
* Made summary_irq and tlmm_base part of msm_gpio_dev
* Fixed the bitmap allocation
* Fixed some compile issues with non-ARM
Rohit Vaswani (3):
ARM: msm: Remove gpiomux-v2 and re-organize MSM_GPIOMUX configs
ARM: msm: Remove unused and unmapped MSM_TLMM_BASE for 8x60
On Thu, May 30, 2013 at 10:47 AM, Vinod Koul wrote:
> On Mon, May 27, 2013 at 03:14:30PM +0300, Andy Shevchenko wrote:
>> Here is a set of small independent patches that clean up or fix minor things
>> across DMA slave drivers.
> The series looks fine. I am going to wait a day more and apply, pls
From: Davidlohr Bueso
Date: Wed, 29 May 2013 14:09:03 -0700
> Use the already defined macro to pass the function return address.
>
> Signed-off-by: Davidlohr Bueso
I've decided that we should just leave this alone for now, because
frankly the choice is arbitrary.
--
To unsubscribe from this
On Fri, May 31, 2013 at 05:57:31PM -0500, Russ Anderson wrote:
> On Fri, May 31, 2013 at 05:28:16PM +0100, Matthew Garrett wrote:
> > If nvram becaomes full, some
> > systems crash during firmware initialisation. So we can't let nvram
> > become full.
On 05/31/2013 03:13 PM, Stephen Boyd wrote:
On 05/31, John Stultz wrote:
On 04/30/2013 05:54 PM, Stephen Boyd wrote:
Here's the patch to make sched_clock generic. I didn't know
where to put it so I just made a new file in kernel/sched
for now.
Signed-off-by: Stephen Boyd
Hey Stephen,
On Mon, 2013-05-20 at 18:06 +0200, Marc Kleine-Budde wrote:
> On 05/17/2013 11:09 AM, Shawn Guo wrote:
> > On Fri, May 17, 2013 at 10:59:17AM +0200, Marc Kleine-Budde wrote:
> >> This patch removes the Kconfig symbol HAVE_CAN_FLEXCAN from
> >> arch/{arm,powerpc}
> >> and allowing compilation
Hi,
On Sat, Jun 01, 2013 at 12:22:40AM +0200, Arnd Bergmann wrote:
> ARM cannot handle udelay for more than 2 miliseconds, so we
There's l missing here.
> should use mdelay instead for those.
Could this be handled
On Sat, 2013-06-01 at 09:22 +1000, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> Here are a few more fixes for powerpc 3.10. It's a bit more than I would
> have liked this late in the game but I suppose that's what happens with
> a brand new chip generation coming out.
>
> A few regression
On Fri, 31 May 2013, Russ Anderson wrote:
> OK. I get nvram looks full due to lack of garbage collection
> on some systems. Does QueryVariableInfo (at runtime) tell you
> it is full? Is the problem that it says it is full when it
> is not, or does not tell you it is full when it is?
We are
Hi Linus !
Here are a few more fixes for powerpc 3.10. It's a bit more than I would
have liked this late in the game but I suppose that's what happens with
a brand new chip generation coming out.
A few regression fixes, some last minute fixes for new P8 features such
as transactional memory,...
On Wed, May 22, 2013 at 3:13 AM, Serban Constantinescu
wrote:
> The Android userspace aligns the data written to the binder buffers to
> 4bytes. Thus for 32bit platforms or 64bit platforms running an 32bit
> Android userspace we can have a buffer looking like this:
>
> platform
On Wed, May 22, 2013 at 3:13 AM, Serban Constantinescu
wrote:
> Since this driver is meant to be used on different types of processors
> and a portable driver should specify the size a variable expects to be
> this patch changes the types used throughout the binder interface.
>
> We use
On Wed, May 22, 2013 at 3:12 AM, Serban Constantinescu
wrote:
> This change will fix the BINDER_SET_MAX_THREADS ioctl to use __u32
> instead of size_t for setting the max threads. Thus using the same
> handler for 32 and 64bit kernels.
>
> This value is stored internally in struct binder_proc and
Jorge,
Please let me know if you have any other questions/concerns.
Thanks,
Suravee
On 5/28/2013 5:45 PM, suravee.suthikulpa...@amd.com wrote:
From: Suravee Suthikulpanit
These patches implement the AMD IOMMU Performance Counter functionality
via custom perf PMU and implement static
On Thu, 30 May 2013 01:08:25 -0700 Joe Perches wrote:
> On Thu, 2013-05-30 at 15:58 +0800, liguang wrote:
> []
> > diff --git a/kernel/sys.c b/kernel/sys.c
> []
> > -static int set_one_prio(struct task_struct *p, int niceval, int error)
> > +static int set_one_prio(struct task_struct *p, int
Hello Linus,
Here is the current set of target-pending fixes for v3.10-rc4 code.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
The highlights include:
- Re-instate sess->wait_list in target_wait_for_sess_cmds() for active
On Thu, 30 May 2013 15:58:05 +0800 liguang wrote:
> --- a/include/linux/reboot.h
> +++ b/include/linux/reboot.h
> @@ -35,7 +35,7 @@ extern void kernel_restart(char *cmd);
> extern void kernel_halt(void);
> extern void kernel_power_off(void);
>
> -extern int C_A_D; /* for sysctl */
> +extern
On 05/31/2013 03:57 PM, Russ Anderson wrote:
>
>>> Which means the previous patch(es) that caused the bricking should
>>> get pulled, too.
>>
>> There are no patches that cause the bricking.
>
> I thought that was the problem you were trying to avoid.
>
There are no *patches* that cause the
On Thu, 30 May 2013 15:58:04 +0800 liguang wrote:
> kernel_shutdown_prepare's parameter can be removed
> by checking global 'system_state', so, maybe we
> can save a register to be used :-).
>
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@ -382,11 +382,10 @@ void kernel_restart(char *cmd)
> }
On Fri, May 31, 2013 at 05:28:16PM +0100, Matthew Garrett wrote:
> On Fri, May 31, 2013 at 10:43:49AM -0500, Russ Anderson wrote:
>
> > When did writing EFI variables to nvram become necessary to boot on
> > UEFI? And if it is necessary, why is it that only linux boot loaders
> > that use EFI
On Thu, 30 May 2013 15:58:03 +0800 liguang wrote:
> Signed-off-by: liguang
> ---
> kernel/sys.c | 12 +---
> 1 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/sys.c b/kernel/sys.c
> index b95d3c7..07c6177 100644
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@
On Wed, May 15, 2013 at 10:01:22PM +0200, Jens Axboe wrote:
> On Wed, May 15 2013, Kent Overstreet wrote:
> > It's only implemented for aio in this patch but it's actually completely
> > trivial to extend to sync kiocbs too - we can make killing a process
> > cancel outstanding sync DIOs, I just
On 05/31/13 15:34, Andy Shevchenko wrote:
> On Fri, May 31, 2013 at 11:22 PM, Emil Goode wrote:
>> This patch fixes a format specifier warning. dma_addr_t can be either
>> u32 or u64 so we should cast to the largest type and change the format
>> specifier to %llx.
>
> dma_addr_t is derived from
Currently, the RTC IRQ is never wakeup-enabled so is not capable of
bringing the system out of suspend.
On OMAP platforms, we have gotten by without this because the TWL RTC
is on an I2C-connected chip which is capable of waking up the OMAP via
the IO ring when the OMAP is in low-power states.
On Fri, 26 Apr 2013 09:50:12 +0900, Simon Horman wrote:
> On Thu, Apr 25, 2013 at 07:28:54PM +0200, Arnd Bergmann wrote:
> > All other irq_domain_add_* functions are exported already, and apparently
> > this one got left out by mistake, which causes build errors for ARM
> > allmodconfig kernels:
On Fri, May 31, 2013 at 11:22 PM, Emil Goode wrote:
> This patch fixes a format specifier warning. dma_addr_t can be either
> u32 or u64 so we should cast to the largest type and change the format
> specifier to %llx.
dma_addr_t is derived from phys_addr_t, thus you may use %pa specifier
which
On Fri, 31 May 2013 14:59:11 +0200, Alexander Gordeev
wrote:
> If a freshly acquired hardware interrupt number already mapped to
> a Linux IRQ number it indicates a problem exists elsewhere, i.e.
> a device driver did not dispose the mapping. Nevertheless, the
> current code reuses such mappings
1 - 100 of 1386 matches
Mail list logo
