On Thu, Apr 25, 2013 at 08:19:05AM +0100, Matt Fleming wrote:
> Yeah, I'm not advocating using casts, I was just saying "Oh, x86-64
> avoids requiring the caller of efi_call_phys* to perform the cast
> by doing it in the definition of efi_call*. That's why this is only
> affecting 32-bit."
>
>
On Thu, Apr 25, 2013 at 11:33:42AM +0800, Axel Lin wrote:
> All regulators have ascendant voltage list in this driver.
> Use regulator_map_voltage_ascend for them.
Applied, thanks.
signature.asc
Description: Digital signature
On Thu, Apr 25, 2013 at 11:12:54AM +0100, Stefano Stabellini wrote:
> On Thu, 25 Apr 2013, Will Deacon wrote:
> > > +/*
> > > + * cpu_suspend Suspend the execution on a CPU
> > > + * @statewe don't currently describe affinity levels, so just
> > > pass 0.
> > > + * @entry_point the
At Tue, 23 Apr 2013 14:51:58 -0700,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.8.9 release.
> There are 42 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
Commit a4b6a77b77ba4f526392612c2365797fab956014 ("module: fix symbol
versioning with symbol prefixes") broke the MODVERSIONS loading of any
module using memcmp (e.g. ipv6) on x86_32, as it's defined to
__builtin_memcmp which is expanded by VMLINUX_SYMBOL_STR. Use
__VMLINUX_SYMBOL_STR instead which
At Tue, 23 Apr 2013 14:53:40 -0700,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.4.42 release.
> There are 26 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
At Tue, 23 Apr 2013 14:56:07 -0700,
Greg Kroah-Hartman wrote:
>
> This is the start of the stable review cycle for the 3.0.75 release.
> There are 23 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
On Mon, Apr 1, 2013 at 12:42 PM, Maxim V. Patlasov
wrote:
> The .writepages one is required to make each writeback request carry more than
> one page on it.
I'd split this into two parts:
1) implement ->writepages() and enable it unconditionally for mmaped
writeback (why is it not enabled by
On Thu, 25 Apr 2013, Will Deacon wrote:
> On Wed, Apr 24, 2013 at 07:40:19PM +0100, Stefano Stabellini wrote:
> > From: Jon Medhurst
> >
> > Add a new 'smp_init' hook to machine_desc so platforms can specify a
> > function to be used to setup smp ops instead of having a statically
> > defined
On Mon, Apr 22, 2013 at 09:03:29PM -0700, Paul E. McKenney wrote:
> > > +This document lists per-CPU kthreads in the Linux kernel and presents
> > > +options to control OS jitter due to these kthreads. Note that kthreads
> >
> > s/due to/which can be caused by/
>
> Same meaning, but "due to" is
On Mon, Apr 1, 2013 at 12:41 PM, Maxim V. Patlasov
wrote:
>
> The .writepages callback will issue writeback requests with more than one
> page aboard. Make existing end/check code be aware of this.
>
> Original patch by: Pavel Emelyanov
If this patch was written by Pavel and then modified by
Introduce os_partition member in nvram_os_partition structure to identify
if the partition is an os partition or not. This will be useful to handle
non-os partitions of-config and common.
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by: Jim Keniston
---
arch/powerpc/platforms/pseries/nvram.c |
Hi,
We encountered this problem on 3.9-rc7, powerpc 7 system. When they trying to
mount a
btrfs partition, kernel paniced with these messages:
aimlp6 login: [ cut here ]
cpu 0x3: Vector: 700 (Program Check) at
On Thu, Feb 14, 2013 at 12:43:15PM +0100, Cong Ding wrote:
> On Sun, Jan 20, 2013 at 10:01:41PM +0100, Hans J. Koch wrote:
> > On Fri, Jan 18, 2013 at 02:00:50PM -0800, Greg Kroah-Hartman wrote:
> > > On Fri, Jan 18, 2013 at 10:05:45PM +0100, Cong Ding wrote:
> > > > On Tue, Dec 11, 2012 at 2:21
This patch set exploits the pstore subsystem to read details of
of-config partition in NVRAM to a separate file in /dev/pstore.
For instance, of-config partition details will be stored in a
file named [of-nvram-5].
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by: Jim Keniston
---
This patch exploits pstore subsystem to read details of common partition
in NVRAM to a separate file in /dev/pstore. For instance, common partition
details will be stored in a file named [common-nvram-6].
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by: Jim Keniston
---
IBM's p series machines provide persistent storage for LPARs through NVRAM.
NVRAM's lnx,oops-log partition is used to log oops messages.
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
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].
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by: Jim Keniston
---
> create mode 100644 drivers/pwm/pwm-rmob.c
> > > delete mode 100644 include/linux/platform_data/leds-renesas-tpu.h
> > > create mode 100644 include/linux/platform_data/pwm-rmob.h
> >
> > I have rebased the pinmux branch on renesas-boards3-for-v3.10 to
Introduce generic read function to read nvram partitions other than rtas.
nvram_read_error_log will be retained which is used to read rtas partition
from rtasd. nvram_read_partition is the generic read function to read from
any nvram partition.
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by:
Introduce version and timestamp information in the oops header.
oops_log_info (oops header) holds version (to distinguish between old
and new format oops header), length of the oops text
(compressed or uncompressed) and timestamp.
The version field will sit in the same place as the length in old
Removal of syslog prefix in the uncompressed oops text will
help in capturing more oops data.
Signed-off-by: Aruna Balakrishnaiah
Reviewed-by: Jim Keniston
---
arch/powerpc/platforms/pseries/nvram.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
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 the pstore subsystem to expose each partition in NVRAM as a
separate file
On Thu, 25 Apr 2013, Will Deacon wrote:
> On Wed, Apr 24, 2013 at 11:14:28PM +0100, Stefano Stabellini wrote:
> > On Wed, 24 Apr 2013, Stefano Stabellini wrote:
> > > Signed-off-by: Stefano Stabellini
> > > CC: Marc Zyngier
> > > CC: will.dea...@arm.com
> > > CC: a...@arndb.de
> > > CC:
> > Yes, I was really hoping (and originally planning) to release 3.9
> > final this weekend, but we had enough issues that I just didn't feel
> > comfy about it. It was borderline, and none of the issues were huge,
> > and maybe I could have called this just 3.9 and opened the merge
> > window,
On Thu, 25 Apr 2013, Will Deacon wrote:
> > +/*
> > + * cpu_suspend Suspend the execution on a CPU
> > + * @statewe don't currently describe affinity levels, so just pass
> > 0.
> > + * @entry_point the first instruction to be executed on return
> > + * returns 0 success, < 0 on
Hi All,
There is a kernel memory leak observed when the proc file
/proc/fs/fscache/stats is read.
The reason is that in fscache_stats_open, single_open is called and respective
release function is not called during release.
Hence fix with correct release function - single_release. The patch is
On Wed, Apr 24, 2013 at 09:22:08PM +0200, Jean Delvare wrote:
> Hi Tony,
>
> Thanks for stepping in.
>
> Le Tuesday 23 April 2013 à 22:00 +, Luck, Tony a écrit :
> > > I don't have much knowledge about IA64 either. All I see is that while
> > > x86 implements memcpy_fromio() with memcpy [1],
Signed-off-by: Zhao Hongjiang
Cc: sta...@vger.kernel.org
---
linux-next use pr_debug instead of dprintk, and fix the issue.
---
fs/aio.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 3f941f2..1dc8786 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@
On Wed, Apr 24, 2013 at 09:07:24PM -0500, Robin Holt wrote:
> On Wed, Apr 24, 2013 at 08:16:50PM +, Luck, Tony wrote:
> > > That being said, "my" SN2 machine was previously running kernel 3.0.34
> > > which has the old dmi_scan code and it also said "DMI not present or
> > > invalid." Plus
On Thu, 25 Apr 2013 11:09:56 +0200, Jiri Olsa wrote:
> On Thu, Apr 25, 2013 at 03:06:37PM +0900, Namhyung Kim wrote:
>> On Wed, 24 Apr 2013 16:09:18 +0200, Jiri Olsa wrote:
>> > On Tue, Apr 23, 2013 at 05:31:03PM +0900, Namhyung Kim wrote:
>> >> From: Namhyung Kim
>> >> +out:
>> >> +
This patch moves struct pci_controller into asm-generic to allow
for use by other architectures thus reducing code duplication in
the kernel.
Signed-off-by: Andrew Murray
---
arch/powerpc/include/asm/pci-bridge.h | 87 +---
include/asm-generic/pci-bridge.h |
This patch unifies similar definations of INDIRECT_TYPE_* between
PowerPC and Microblaze.
Signed-off-by: Andrew Murray
---
arch/microblaze/include/asm/pci-bridge.h | 23 ---
arch/powerpc/include/asm/pci-bridge.h| 23 ---
This patch removes struct pci_controller from Microblaze and instead
uses struct pci_controller from asm-generic.
Signed-off-by: Andrew Murray
---
arch/microblaze/include/asm/pci-bridge.h | 75 ++
include/asm-generic/pci-bridge.h |2 +-
2 files changed,
PowerPC and Microblaze have nearly identical definations of struct
pci_controller - this patch unifies them in asm-generic to reduce
code duplication and to allow new architectures to reuse.
This patchset follows and depends on "of/pci: Provide common
support for PCI DT parsing" which provided
Hi Matthew, Peter, Linus,
> Yes, I was really hoping (and originally planning) to release 3.9
> final this weekend, but we had enough issues that I just didn't feel
> comfy about it. It was borderline, and none of the issues were huge,
> and maybe I could have called this just 3.9 and opened the
Commit-ID: 06d219dc22daa26b79ec8e611caa68801607f15d
Gitweb: http://git.kernel.org/tip/06d219dc22daa26b79ec8e611caa68801607f15d
Author: Jean Delvare
AuthorDate: Thu, 25 Apr 2013 11:24:05 +0200
Committer: Ingo Molnar
CommitDate: Thu, 25 Apr 2013 11:32:51 +0200
x86/setup: Drop unneeded
On Mon, 22 Apr 2013, Thomas Gleixner wrote:
> With the patch below, the box should survive and we should see a
>
> "Spurious HPET timer interrupt on HPET timer..." entry in dmesg.
>
> That's a first workaround to confirm my theory. I'll look into the
> HPET code how we can avoid that at all.
>> >> >> On Thu, Apr 18, 2013 at 12:00:49PM +, Zhanghaoyu (A) wrote:
>> >> >>> I start 10 VMs(windows xp), then running geekbench tool on
>> >> >>> them, about 2 days, one of them was reset, I found the reset
>> >> >>> operation is done by int kvm_cpu_exec(CPUArchState *env) {
>> >> >>>
From: Wei Yongjun
Fix to return -ENODEV in the chip not found error handling
case instead of 0, as done elsewhere in this function.
Signed-off-by: Wei Yongjun
---
drivers/rtc/rtc-pcf2123.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/rtc-pcf2123.c
From: Wei Yongjun
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Signed-off-by: Wei Yongjun
---
drivers/staging/ozwpan/ozcdev.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/ozwpan/ozcdev.c
On 2013年04月25日 17:05, Chen Gang wrote:
> On 2013年04月25日 17:00, Michael Neuling wrote:
Signed-off-by: Chen Gang
---
arch/powerpc/include/asm/kvm_asm.h |2 +-
arch/powerpc/kernel/exceptions-64s.S |6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > This change will cost ~25KB of memory, but it's worth the trade-off,
> > as it removes a great deal of overhead. It means that instead of only
> > allocating memory for the logical channels in
arch/x86/kernel/setup.c includes but it doesn't look like
it needs it, is sufficient.
Signed-off-by: Jean Delvare
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
---
arch/x86/kernel/setup.c |1 -
1 file changed, 1 deletion(-)
--- linux-3.9-rc8.orig/arch/x86/kernel/setup.c
On 04/24/2013 09:34 PM, Gleb Natapov wrote:
>> diff --git a/arch/x86/kvm/mmu.h b/arch/x86/kvm/mmu.h
>> index 2adcbc2..6b4ba1e 100644
>> --- a/arch/x86/kvm/mmu.h
>> +++ b/arch/x86/kvm/mmu.h
>> @@ -52,6 +52,20 @@
>>
>> int kvm_mmu_get_spte_hierarchy(struct kvm_vcpu *vcpu, u64 addr, u64
>>
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > Before allocating memory for logical channels, the current driver
> > checks to see if there are any. Well as the dma40_memcpy_channels[]
> > array is always populated, the check is always true.
On 04/24/2013 08:59 PM, Gleb Natapov wrote:
> On Mon, Apr 01, 2013 at 05:56:49PM +0800, Xiao Guangrong wrote:
>> Then it has chance to trigger mmio generation number wrap-around
>>
>> Signed-off-by: Xiao Guangrong
>> ---
>> arch/x86/include/asm/kvm_host.h |1 +
>> arch/x86/kvm/mmu.c
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> The channels reserved for memcpy are the same for all currently
> supported platforms. With this in mind, we can ease the platform
> data passing requirement by moving these assignments out from
> platform code and place them directly into the
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > There are lots of lengthy if() statements located sporadically up and
> > down the driver. This simple macro should make many of them a little
> > simpler to decipher. The remainder have to stay
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> Before allocating memory for logical channels, the current driver
> checks to see if there are any. Well as the dma40_memcpy_channels[]
> array is always populated, the check is always true. Best to
> remove the check.
>
> Cc: Vinod Koul
>
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > The DMA40 controller uses two sets of base addresses. In order to have
> > them automatically setup as resources by the Open Format framework we
> > have to set names for them. The names have to
On Wed, 24 Apr 2013 11:37:30 +0200, Jiri Olsa wrote:
> Moving arch check into config/Makefile.
>
[SNIP]
> +# include config/Makefile by default and rule out
> +# non-config cases
> +config := 1
> +
> +# standalone clean
> +ifeq ($(MAKECMDGOALS),clean)
> + config := 0
> endif
> -ifeq
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > The current implementation of the DMA40's local MAX() macro evaluates
> > its arguments more times than is necessary. This patch strips it
> > optimises it to only evaluate what's appropriate.
>
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
>
> > DMA configuration data is now allocated in the MMCI driver, so these
> > are just ignored.
> >
> > Signed-off-by: Lee Jones
>
> Reviewed-by: Linus Walleij
>
> I tried just applying this
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> This change will cost ~25KB of memory, but it's worth the trade-off,
> as it removes a great deal of overhead. It means that instead of only
> allocating memory for the logical channels in use, it does so for all
> available ones, which is 32
On Thu, Apr 25, 2013 at 03:06:37PM +0900, Namhyung Kim wrote:
> On Wed, 24 Apr 2013 16:09:18 +0200, Jiri Olsa wrote:
> > On Tue, Apr 23, 2013 at 05:31:03PM +0900, Namhyung Kim wrote:
> >> From: Namhyung Kim
> >> +out:
> >> + put_tracing_file(file);
> >> + return ret;
> >> +}
> >> +
> >> +static
On Wed, Apr 24, 2013 at 10:05:46AM -0700, Michal Nazarewicz wrote:
> On Wed, Apr 24 2013, Geert Uytterhoeven wrote:
> > If gcc (e.g. 4.1.2) decides not to inline cdc_config_register() and
> > rndis_config_register(), this will cause section mismatch warnings:
> >
> > WARNING:
> > Devices which utilise DMA tend to use the same channel numbers for
> > transmitting and receiving. For this reason and the fact that it'll
> > decrease the burden of platform data passed to each device, we're
> > amalgamating source and destination device types.
>
> I don't think this
On 2013年04月25日 17:00, Michael Neuling wrote:
>> >
>> > Signed-off-by: Chen Gang
>> > ---
>> > arch/powerpc/include/asm/kvm_asm.h |2 +-
>> > arch/powerpc/kernel/exceptions-64s.S |6 +++---
>> > 2 files changed, 4 insertions(+), 4 deletions(-)
>> >
>> > diff --git
On Wed, 24 Apr 2013 11:37:28 +0200, Jiri Olsa wrote:
> Adding automated test for testing the build process.
> To run it you need to be in perf directory or specify
> one with PERF variable. It's also possible to specify
> optional Makefile to test via MK variable.
$ pwd
On Thu, Apr 25, 2013 at 09:20:44AM +0100, Paul Bolle wrote:
> On Thu, 2013-04-25 at 17:02 +0900, Jonghwan Choi wrote:
> > This patch looks like it should be in the 3.8-stable tree, should we apply
> > it?
>
> That would be only the setup.c chunk. That fixes a typo introduced in
> v3.4 (see commit
Chen Gang wrote:
>
> When CONFIG_KVM_BOOK3S_64_PR is enabled,
> MASKABLE_EXCEPTION_PSERIES(0x900 ...) will includes __KVMTEST, it will
> exceed 0x980 which STD_EXCEPTION_HV(0x980 ...) will use, it will cause
> compiling issue.
>
> The related errors:
> arch/powerpc/kernel/exceptions-64s.S:
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> 'psize' is used to calculate the maximum DMA burst size. However it
> is only taken into consideration when editing the DMA channel's
> configuration. The Audio DMA platform data is only used to allocate
> a channel, not configure it. That
On 25.4.2013 00:29, Yann E. MORIN wrote:
> From: "Yann E. MORIN"
>
> Currently the odds to set each symbol is (rounded):
> booleans: y: 50% n: 50%
> tristates: y: 33% m: 33% n: 33%
>
> Introduce a KCONFIG_PROBABILITY environment variable to tweak the
> probabilities (in
On Thu, Apr 25, 2013 at 10:36 AM, Arnd Bergmann wrote:
> On Thursday 25 April 2013, Linus Walleij wrote:
>> Are we now sacrificing that ability on the altar of simplification?
>>
>> I actually think not, but that we should do periph-to-periph transfers
>> in some other way, and that the .dir
On Wed, Apr 24, 2013 at 11:14:28PM +0100, Stefano Stabellini wrote:
> On Wed, 24 Apr 2013, Stefano Stabellini wrote:
> > Signed-off-by: Stefano Stabellini
> > CC: Marc Zyngier
> > CC: will.dea...@arm.com
> > CC: a...@arndb.de
> > CC: rob.herr...@calxeda.com
>
> Thinking twice about this patch,
于 2013年04月25日 14:57, Brian Norris 写道:
A bit late on this one, but is there a good reason this wasn't just 2
separate 16-bit fields? We already have a few, and I don't see why
this couldn't be the same.
I just want to make the ecc_strength/ecc_size more coupled for the
nand_flash_dev{}.
If we
On Wed, Apr 24, 2013 at 12:23:13PM -0700, Andrew Morton wrote:
> > } else {
> > + /*
> > +* In the case of swap-over-nfs, this can be a
> > +* temporary failure if the system has limited
> > +* memory for
On Wed, Apr 24, 2013 at 07:40:19PM +0100, Stefano Stabellini wrote:
> From: Jon Medhurst
>
> Add a new 'smp_init' hook to machine_desc so platforms can specify a
> function to be used to setup smp ops instead of having a statically
> defined value. The hook must return true when smp_ops are
Hi folks,
The following changes since commit 8c58bf3eec3b8fc8162fe557e9361891c20758f2:
x86,efi: Implement efi_no_storage_paranoia parameter (2013-04-17 15:13:38
+0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent
Hi Stefano,
On Wed, Apr 24, 2013 at 07:40:18PM +0100, Stefano Stabellini wrote:
> Rename virt_smp_ops to psci_smp_ops and move them to
> arch/arm/kernel/psci_smp.c.
> Remove mach-virt/platsmp.c, now unused.
> Compile psci_smp if CONFIG_ARM_PSCI and CONFIG_SMP.
>
> Add a cpu_die smp_op based on
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> DMA configuration data is now allocated in the UART driver, so these
> are just ignored.
>
> Signed-off-by: Lee Jones
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> DMA configuration data is now allocated in the SSP driver, so these
> are just ignored.
>
> Signed-off-by: Lee Jones
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> DMA configuration data is now allocated in the MMCI driver, so these
> are just ignored.
>
> Signed-off-by: Lee Jones
Reviewed-by: Linus Walleij
I tried just applying this (since it's pretty stand-alone) but seems to
be dependent on things
On Thursday 25 April 2013, Linus Walleij wrote:
> Are we now sacrificing that ability on the altar of simplification?
>
> I actually think not, but that we should do periph-to-periph transfers
> in some other way, and that the .dir attribute should go away from
> the struct stedma40_chan_cfg as
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> The current implementation of the DMA40's local MAX() macro evaluates
> its arguments more times than is necessary. This patch strips it
> optimises it to only evaluate what's appropriate.
>
> Cc: Vinod Koul
> Cc: Dan Williams
> Cc: Per
On Thu, Apr 25, 2013 at 10:25:11AM +0200, richard -rw- weinberger wrote:
> On Thu, Apr 25, 2013 at 9:37 AM, Uwe Kleine-König
> wrote:
> > The file header declares the code to be covered by GPL v2 only, so use
> > explicit v2 for MODULE_LICENSE, too.
>
> Doesn't this apply to almost any driver?
>
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> The DMA40 controller uses two sets of base addresses. In order to have
> them automatically setup as resources by the Open Format framework we
> have to set names for them. The names have to be the same as the ones
> used to fetch them back
On Thu, Apr 25, 2013 at 9:37 AM, Uwe Kleine-König
wrote:
> The file header declares the code to be covered by GPL v2 only, so use
> explicit v2 for MODULE_LICENSE, too.
Doesn't this apply to almost any driver?
I don't understand why you explicitly "fix" this one.
--
Thanks,
//richard
--
To
于 2013/4/25 16:21, Chen Gang 写道:
Hello Mike:
Please try this patch, at least it can pass compiling with the config
file which you provided under my cross-compiling envrionments.
I do not give a running test now, so better to try to run the new kernel
with this patch.
OK, I will use your
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> For the moment at least, the TX and RX channels for DB8500 USB are
> identical, so this patch generalises them into a single structure
> and passes it twice. Once as the TX and again for the RX configuration.
> We're keeping the infrastructure
From: Geert Uytterhoeven
Date: Wed, 24 Apr 2013 14:46:37 +0200
> drivers/isdn/sc/init.c: In function ‘__check_irq’:
> drivers/isdn/sc/init.c:36: warning: return from incompatible pointer type
> drivers/isdn/sc/init.c: In function ‘__check_ram’:
> drivers/isdn/sc/init.c:37: warning: return from
From: Geert Uytterhoeven
Date: Wed, 24 Apr 2013 11:40:55 +0200
> If gcc (e.g. 4.1.2) decides not to inline vsock_init_tables(), this will
> cause a section mismatch:
>
> WARNING: net/vmw_vsock/vsock.o(.text+0x1bc): Section mismatch in reference
> from the function __vsock_core_init() to the
From: Asias He
Date: Wed, 24 Apr 2013 14:33:52 +0800
> When we call vsock_core_init to init VSOCK the second time,
> vsock_device.minor still points to the old dynamically allocated minor
> number. misc_register will allocate it for us successfully as if we were
> asking for a static one.
Hello Mike:
Please try this patch, at least it can pass compiling with the config
file which you provided under my cross-compiling envrionments.
I do not give a running test now, so better to try to run the new kernel
with this patch.
Thanks.
On 2013年04月25日 16:18, Chen Gang wrote:
>
> When
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> There are lots of lengthy if() statements located sporadically up and
> down the driver. This simple macro should make many of them a little
> simpler to decipher. The remainder have to stay in place, as they
> detail slightly more specific
On Thu, 2013-04-25 at 17:02 +0900, Jonghwan Choi wrote:
> This patch looks like it should be in the 3.8-stable tree, should we apply
> it?
That would be only the setup.c chunk. That fixes a typo introduced in
v3.4 (see commit e5ab85800820edd907d3f43f285e1232f84d5a41
("ARM: 7382/1: mm: truncate
When CONFIG_KVM_BOOK3S_64_PR is enabled,
MASKABLE_EXCEPTION_PSERIES(0x900 ...) will includes __KVMTEST, it will
exceed 0x980 which STD_EXCEPTION_HV(0x980 ...) will use, it will cause
compiling issue.
The related errors:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
From: "Maxin B. John"
With 3.9.0-rc8 kernel in p2020rdb powerpc target, the console gets
flooded with this message without any SD-Cards present:
"mmc0: Timeout waiting for hardware interrupt"
Since the driver doesn't implement proper card detection, it assumes that
card is always present. This
* Matt Fleming wrote:
> On 25/04/13 07:55, Ingo Molnar wrote:
> > It's a basic cleanliness and robustness issue: we generally avoid type
> > casts in the kernel, because type casts override compile-time type checks
> > and are easy to get wrong. They are also ugly.
> >
> > So in generaly we
On Wed, 24 Apr 2013, Rabin Vincent wrote:
> 2013/4/24 Lee Jones :
> > The aim is to make the code that little more readable.
> >
> > Acked-by: Vinod Koul
> > Acked-by: Arnd Bergmann
> > Signed-off-by: Lee Jones
>
> Please pay closer attention to the semantics of each usage instead of
> just
Hi all,
Some time ago, I mentioned there are some problems on x86-32 system about
handling md-block-device which size is larger than 16TB.
And i send a patch.But there are no concern with it.
The website of is: http://www.spinics.net/lists/linux-fsdevel/msg55672.html.
Except the wrapping
On Thu, Apr 18, 2013 at 12:11 PM, Lee Jones wrote:
> Devices which utilise DMA tend to use the same channel numbers for
> transmitting and receiving. For this reason and the fact that it'll
> decrease the burden of platform data passed to each device, we're
> amalgamating source and destination
This patch looks like it should be in the 3.8-stable tree, should we apply
it?
--
From: "Paul Bolle "
commit 4e1db26a0b42e2b6e27c05d68adcc01709c2eed2 upstream
CONFIG_LPAE doesn't exist: the correct option is CONFIG_ARM_LPAE, so fix
up the two typos under arch/arm/.
The fix to
From: Nicholas Bellinger
This patches fixes a regression with solicited NopIN handling
in traditional iSCSI code introduced during TX immediate queue
refactoring for v3.10 for-next code.
Cc: Or Gerlitz
Signed-off-by: Nicholas Bellinger
---
drivers/target/iscsi/iscsi_target.c |6 --
1
From: Nicholas Bellinger
This patch fixes a regression where failures before backend se_cmd
execution in iscsit_handle_scsi_cmd() is leaking iscsi_cmd due to
a missing target_put_sess_cmd() call to drop the extra kref.
Introduced during the RX PDU refactoring in v3.10 for-next code.
Cc: Or
From: Nicholas Bellinger
During early ISCSI_OP_SCSI_CMD exception handling with non GOOD status, the
TX thread context in isert_response_queue() needs to post IB_WR_SEND via
isert_put_response() when processing ISTATE_SEND_STATUS.
Cc: Or Gerlitz
Signed-off-by: Nicholas Bellinger
---
From: Nicholas Bellinger
Hi folks,
This series addresses two bugs within v3.10 for-next code related to
the upcoming iscsi-target series adding multi-transport support, along
with a third iser-target bugfix related to early ISCSI_OP_SCSI_CMD
exception handling.
These three patches are being
On Mon, 2013-04-22 at 17:07 +0100, Nicolas Pitre wrote:
> Sure there are ways to screw up Xen support from within this hook, but
> that can be achieved in many other places. Will Xen take over every
> possible hooks in the kernel to prevent that from happening?
In the majority of the other
On Wed, Mar 27, 2013 at 10:26 PM, Michael Kerrisk (man-pages)
wrote:
>Inside the user namespace, the shell has user and group ID 0,
>and a full set of permitted and effective capabilities:
>
>bash$ cat /proc/$$/status | egrep '^[UG]id'
>Uid: 000
501 - 600 of 1278 matches
Mail list logo
