Sorry, I didn't realize that text would look so ugly in LKML.
I'll be sure to keep the lines nice and short next time.
~Cruz
--
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
On Mon, Jul 30, 2012 at 9:29 PM, Christoph Lameter wrote:
> On Sat, 28 Jul 2012, JoonSoo Kim wrote:
>
>> 2012/7/28 Christoph Lameter :
>> > On Sat, 28 Jul 2012, Joonsoo Kim wrote:
>> >
>> >> move_pages() syscall may return success in case that
>> >> do_move_page_to_node_array return positive
On Wed, 1 Aug 2012, Jingoo Han wrote:
On Wednesday, August 01, 2012 1:38 PM Sachin Kamat wrote:
On 1 August 2012 10:00, Jingoo Han wrote:
On Wednesday, August 01, 2012 1:00 PMSachin Kamat wrote:
On 1 August 2012 04:51, Jingoo Han wrote:
On Wednesday, August 01, 2012 1:39 AM Damien
On Wednesday, August 01, 2012 1:00 PM Sachin Kamat wrote:
>
> On 1 August 2012 04:51, Jingoo Han wrote:
> > On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
> >>
> >> From: Damien Cassou
> >>
> >> The various devm_ functions allocate memory that is released when a driver
> >>
On Tue, Jul 31, 2012 at 06:08:01PM -0700, Linus Torvalds wrote:
> On Tue, Jul 31, 2012 at 1:19 AM, Thierry Reding
> wrote:
> >
> > I just sent a new pull request with a signed tag. I've also included a
> > more detailed description of why this is useful, along the lines of what
> > Arnd already
On Wednesday, August 01, 2012 1:38 PM Sachin Kamat wrote:
>
> On 1 August 2012 10:00, Jingoo Han wrote:
> > On Wednesday, August 01, 2012 1:00 PMSachin Kamat wrote:
> >>
> >> On 1 August 2012 04:51, Jingoo Han wrote:
> >> > On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
> >> >>
> >>
I will document the rest later if they remain unchanged
Normally, I would do them all at once, but I don't have the chance to do them
all at the moment
Signed-off-by: Cruz Julian Bishop
---
drivers/staging/android/logger.c | 90 +-
1 file changed, 60
Previously, there were simply comments after each part - Now, it is completed
properly according to "Kernel doc"
Sorry in advance if I made any mistakes.
Signed-off-by: Cruz Julian Bishop
---
drivers/staging/android/logger.h | 24 +---
1 file changed, 17 insertions(+), 7
Previously, when calling is_between(a, b, c), the calculation was wrong.
It counted C as between A and B if C was equal to B, but not A.
Example of this are:
is_between(1, 10, 10) = 1 (Expected: 0)
is_between(1, 10, 1) = 0 (Expected: 0)
is_between(20, 10, 10) = 1 (Expected: 0)
And so on and so
Signed-off-by: Cruz Julian Bishop
---
drivers/staging/android/logger.c | 40 +-
1 file changed, 26 insertions(+), 14 deletions(-)
diff --git a/drivers/staging/android/logger.c b/drivers/staging/android/logger.c
index f7b8237..1d5ed47 100644
---
Signed-off-by: Cruz Julian Bishop
---
drivers/staging/android/ashmem.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index 69cf2db..94a740d 100644
---
Hi,
This set of patches completes more documentation in android/logger.c, as well
as fixing a bug there and a comment formatting issue in android/ashmem.c.
Sorry if kernel-doc was not supposed to be applied to driver files - If it
isn't, I'll be sure to remember that for next time. :)
Cruz
On 1 August 2012 10:00, Jingoo Han wrote:
> On Wednesday, August 01, 2012 1:00 PMSachin Kamat wrote:
>>
>> On 1 August 2012 04:51, Jingoo Han wrote:
>> > On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
>> >>
>> >> From: Damien Cassou
>> >>
>> >> The various devm_ functions allocate
Seth Jennings wrote:
> As part of the Kconfig rework for drivers/crypto/nx, the meaning of
> CONFIG_CRYPTO_DEV_NX was changed. At the same time this commit was
> heading upstream
>
> fd297b3a7302ab866306f53c1fd1e97b083fe83e
> powerpc: Enable pseries hardware RNG and crypto module
>
> still
On Wednesday, August 01, 2012 1:00 PMSachin Kamat wrote:
>
> On 1 August 2012 04:51, Jingoo Han wrote:
> > On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
> >>
> >> From: Damien Cassou
> >>
> >> The various devm_ functions allocate memory that is released when a driver
> >> detaches.
As part of the Kconfig rework for drivers/crypto/nx, the meaning of
CONFIG_CRYPTO_DEV_NX was changed. At the same time this commit was
heading upstream
fd297b3a7302ab866306f53c1fd1e97b083fe83e
powerpc: Enable pseries hardware RNG and crypto module
still used the old meaning, set
On Fri, Jul 27, 2012 at 2:23 PM, Jiri Olsa wrote:
> hi,
> patches available also as tarball in here:
> http://people.redhat.com/~jolsa/perf_post_unwind_v8.tar.bz2
>
> v8 changes:
>- patch 2 - added dump registers ABI specification as suggested
>by Stephane
>- v7 patches
On 1 August 2012 04:51, Jingoo Han wrote:
> On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
>>
>> From: Damien Cassou
>>
>> The various devm_ functions allocate memory that is released when a driver
>> detaches. This patch uses these functions for data that is allocated in
>> the
Hi Linus,
These move the OLPC Embedded Controller driver out of arch/x86/platform and
into drivers/platform/olpc. OLPC machines are now ARM-based (which means lots
of x86 and ARM changes), but are typically pretty self-contained.. so it makes
more sense to go through a separate OLPC tree after
Hi Linus,
Here are the irqdomain changes I've got queued up. I held off sending
this pull request due to a late discovered bug and I wanted to give it
some extra time in linux-next. All should be good now. Please pull.
g.
The following changes since commit
On Thu, Jul 26, 2012 at 02:22:48PM +0200, Markus Trippelsdorf wrote:
> Every time I start qemu-kvm on my system the following line is added to
> the syslog:
>
> vcpu0 unhandled rdmsr: 0xc0010001
>
> AFAICS all calls to vcpu_unimpl only contain debugging info with little
> or no value for the
Kevin Ross wrote:
On 07/27/2012 09:45 PM, Grant Coady wrote:
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for
On Tue, Jul 24, 2012 at 02:23:59PM +0530, Raghavendra K T wrote:
> From: Raghavendra K T
>
> Thanks Alex for KVM_HC_FEATURES inputs and Jan for VAPIC_POLL_IRQ,
> and Peter (HPA) for suggesting hypercall ABI addition.
>
> Signed-off-by: Raghavendra K T
> ---
> Please have a closer look at
On 31.07.2012 22:59, s...@shealevy.com wrote:
On some setups (probably due to too new a GNU Make), firmware
installation fails with
*** No rule to make target `lib/firmware/./', needed by
`lib/firmware/.fw'. Stop.
when a file in the top-level firmware/ directory is needed.
Original patch idea
On some setups (probably due to too new a GNU Make), firmware
installation fails with
*** No rule to make target `lib/firmware/./', needed by
`lib/firmware/.fw'. Stop.
when a file in the top-level firmware/ directory is needed.
Original patch idea by Denys Dmytriyenko, see
On some setups (probably due to too new a GNU Make), firmware
installation fails with
*** No rule to make target `lib/firmware/./', needed by
`lib/firmware/.fw'. Stop.
when a file in the top-level firmware/ directory is needed.
Original patch idea by Denys Dmytriyenko, see
On 07/31/2012 07:19 PM, Thierry Reding wrote:
* PGP Signed by an unknown key
On Tue, Jul 31, 2012 at 06:51:03PM +0900, Alex Courbot wrote:
On 07/30/2012 08:33 PM, Thierry Reding wrote:
+You will need an instance of power_seq_resources to keep track of the resources
+that are already
On 07/31/2012 04:06 PM, Michal Hocko wrote:
On Tue 31-07-12 13:49:21, Larry Woodman wrote:
On 07/31/2012 08:46 AM, Mel Gorman wrote:
Fundamentally I think the problem is that we are not correctly detecting
that page table sharing took place during huge_pte_alloc(). This patch is
longer and
2012/7/27 Wen Congyang :
> We don't call __add_pages() directly in the function add_memory()
> because some other architecture related things need to be done
> before or after calling __add_pages(). So we should introduce
> a new function arch_remove_memory() to revert the things
> done in
On Tue, 2012-07-31 at 22:56 -0300, Herton Ronaldo Krzesinski wrote:
> On Tue, Jul 31, 2012 at 05:43:38AM +0100, Ben Hutchings wrote:
> > 3.2-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Nishanth Menon
> >
> > commit
From: Alex
Adds an expert Kconfig option, CONFIG_COREDUMP, which allows disabling of core
dump.
This saves approximately 2.6k in the compiled kernel, and complements
CONFIG_ELF_CORE,
which now depends on it.
CONFIG_COREDUMP also disables coredump-related sysctls, except for
suid_dumpable and
This was done in preparation for making core dump functionality optional.
The variable "suid_dumpable" and associated functions are left in fs/exec.c
because they're used elsewhere, such as in ptrace.
Signed-off-by: Alex Kelly
Reviewed-by: Josh Triplett
---
fs/Makefile | 2 +-
On Jul 31, 2012, at 7:10 PM, "Jianbin Kang" wrote:
>> Actually this is what I'm working on now, using async_tx to replace the
>> memcpy. I believe the changes shouldn't be that significant.
>>
>> Is the "hardware that can setup dma" you refer to something that does
>> not use this interface?
On 8/1/2012 9:47 AM, Alex Courbot wrote:
> On 07/31/2012 09:55 PM, Mitch Bradley wrote:
>> On 7/31/2012 8:38 PM, Thierry Reding wrote:
>>> On Tue, Jul 31, 2012 at 08:22:17PM +0800, Mitch Bradley wrote:
On 7/31/2012 6:56 PM, Thierry Reding wrote:
> On Tue, Jul 31, 2012 at 07:32:20PM +0900,
On Tue, 31 Jul 2012 13:56:58 -0700
Yinghai Lu wrote:
> On Mon, Jul 30, 2012 at 8:20 PM, Len Brown wrote:
> > Applied.
> >
> > thanks,
> > Len Brown, Intel Open Source Technology Center
> >
> > ps. next time, please send to linux-a...@vger.kernel.org list
> > also, put comments not for the
> Actually this is what I'm working on now, using async_tx to replace the
> memcpy. I believe the changes shouldn't be that significant.
>
> Is the "hardware that can setup dma" you refer to something that does
> not use this interface?
>
Yes, they use this interface, but split 'memcpy_toio' to
From: fangxiaozhi
1. This patch is based on the kernel of 3.5
2. In this patch, we add new micro for matching the series USB devices with
vendor ID and interface information.
3. In this patch, we add new declarations into option.c to support the new
interfaces of Huawei Data Card devices. And
Hello,
When building with
MODLIB=/nix/store/ghx6s9hnk9irim7c7f63zrxqiv6xjh3w-linux-3.5/lib/modules/3.5.0
and
INSTALL_FW_PATH="/nix/store/ghx6s9hnk9irim7c7f63zrxqiv6xjh3w-linux-3.5/lib/firmware",
building Linux 3.5 with CONFIG_ATM_AMBASSADOR=m fails with:
"make[2]: *** No rule to make
On Tue, Jul 31, 2012 at 05:43:38AM +0100, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Nishanth Menon
>
> commit b110547e586eb5825bc1d04aa9147bff83b57672 upstream.
This change is uneeded in 3.2, but doesn't
2012/7/27, Jeff Layton :
> On Fri, 27 Jul 2012 11:15:23 +0900
> Namjae Jeon wrote:
>
>> Hi Jeff.
>>
>> Which testcase(or test method) do I use to know improved point from
>> ESTALE error ?
>> I want to know before & after using testcase with this patch-set.
>>
>
> It's a bit labor intensive, I'm
On 07/31/2012 09:55 PM, Mitch Bradley wrote:
On 7/31/2012 8:38 PM, Thierry Reding wrote:
On Tue, Jul 31, 2012 at 08:22:17PM +0800, Mitch Bradley wrote:
On 7/31/2012 6:56 PM, Thierry Reding wrote:
On Tue, Jul 31, 2012 at 07:32:20PM +0900, Alex Courbot wrote:
On 07/31/2012 07:45 AM, Stephen
On 07/31/2012 09:22 PM, Mitch Bradley wrote:
On 7/31/2012 6:56 PM, Thierry Reding wrote:
On Tue, Jul 31, 2012 at 07:32:20PM +0900, Alex Courbot wrote:
On 07/31/2012 07:45 AM, Stephen Warren wrote:
I wonder if using the same structure/array as input and output would
simplify the API; the
At 07/31/2012 08:40 PM, Gerald Schaefer Wrote:
> On Mon, 30 Jul 2012 18:35:37 +0800
> Wen Congyang wrote:
>
>> At 07/30/2012 06:23 PM, Heiko Carstens Wrote:
>>> On Fri, Jul 27, 2012 at 06:32:15PM +0800, Wen Congyang wrote:
We don't call __add_pages() directly in the function add_memory()
On Tue, 31 Jul 2012, Konstantin Khlebnikov wrote:
> Some security modules and oprofile still uses VM_EXECUTABLE for retrieving
> task's executable file, after this patch they will use mm->exe_file directly.
> mm->exe_file protected with mm->mmap_sem, so locking stays the same.
>
Acked-by: James
On Tue, 31 Jul 2012 12:41:21 +1000, NeilBrown said:
> On Mon, 30 Jul 2012 21:22:10 +0200 "C. Schmid"
> wrote:
> > i want to complain about the removal of the --pid-owner Support for
> > iptables.
> > As far as i understand it this support was just removed without replacement.
>
> Yes, 7 years
To set REGULATOR_MODE_IDLE mode, what we do is to clear DC1_ACTIVE and
DC1_SLEEP bits, this can be done in one wm8400_set_bits() call.
Signed-off-by: Axel Lin
---
drivers/regulator/wm8400-regulator.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
On Tue, Jul 31, 2012 at 1:19 AM, Thierry Reding
wrote:
>
> I just sent a new pull request with a signed tag. I've also included a
> more detailed description of why this is useful, along the lines of what
> Arnd already mentioned.
>
> My key was signed by Sebastian Andrzej Siewior today and I
It is expected that Extended CSD register(the size of this register
is larger than CID/CSD) will be referenced more frequently as more
fields have been added to Extended CSD and it seems that it is not
a good option to double the memory used.
This patch is intended to avoid the use of bounce
On 五, 2012-07-27 at 18:48 +0800, Wei Ni wrote:
> On Fri, 2012-07-27 at 15:39 +0800, Zhang Rui wrote:
> > On 五, 2012-07-27 at 09:30 +0200, Jean Delvare wrote:
> > > On Fri, 27 Jul 2012 10:58:21 +0800, Wei Ni wrote:
> > > > On Fri, 2012-07-27 at 09:21 +0800, Zhang Rui wrote:
> > > > > is it possible
On Thu, Jul 19, 2012 at 01:59:36PM -0400, Chen Gong wrote:
> Date: Thu, 19 Jul 2012 13:59:36 -0400
> From: Chen Gong
> To: t...@linutronix.de
> Cc: tony.l...@intel.com, b...@amd64.org, x...@kernel.org,
> linux-kernel@vger.kernel.org
> Subject: [RESEND PATCH 0/5 V2] x86: mce: Bugfixes,
On Mon, Jul 30, 2012 at 10:59:39PM +0200, Rafael J. Wysocki wrote:
[...]
> > Well, currently drivers/power/ is indeed just for power supply class
> > subsystem and drivers. But if the trend is to gather power management
> > ("policy") stuff under one directory, i.e.
> >
> > drivers/
> > power/
On Fri, Jun 22, 2012 at 10:04 AM, Alan Cox wrote:
> On Fri, 22 Jun 2012 08:36:57 -0700
> Greg KH wrote:
>
>> On Fri, Jun 22, 2012 at 04:44:59PM +0100, Alan Cox wrote:
>> > From: Alan Cox
>> >
>> > tty: move the termios object into the tty
>> >
>> > This will let us sort out a whole pile of
On Fri, Jun 22, 2012 at 8:47 AM, Alan Cox wrote:
> Now that we don't have tty->termios tied to drivers->tty we can untangle
> the logic here. In addition we can push the removal logic out of the
> destructor path.
>
> At that point we can think about sorting out tty_port and console and all
> the
On Tue, Jul 31, 2012 at 05:18:11PM -0700, Paul E. McKenney wrote:
> On Tue, Jul 31, 2012 at 08:09:38PM -0400, Steven Rostedt wrote:
> > On Tue, 2012-07-31 at 16:57 -0700, Paul E. McKenney wrote:
> >
> > > > What was the next lines? I bet you it was "PASSED". Which means it did
> > > > not fail.
blk_set_stacking_limits is intended to allow stacking drivers to build
up the limits of the stacked device based on the underlying devices'
limits. But defaulting 'max_sectors' to BLK_DEF_MAX_SECTORS (1024)
doesn't allow the stacking driver to inherit a max_sectors larger than
1024 -- due to
On Tue, Jul 31, 2012 at 08:09:38PM -0400, Steven Rostedt wrote:
> On Tue, 2012-07-31 at 16:57 -0700, Paul E. McKenney wrote:
>
> > > What was the next lines? I bet you it was "PASSED". Which means it did
> > > not fail. This is the second bug you found that has to do with RCU being
> > > called
On Tue, 2012-07-31 at 16:57 -0700, Paul E. McKenney wrote:
> > What was the next lines? I bet you it was "PASSED". Which means it did
> > not fail. This is the second bug you found that has to do with RCU being
> > called in 'idle'. The one that Paul posted a patch for.
>
> Though it needs
On Tue, Jul 31, 2012 at 07:51:39PM -0400, Steven Rostedt wrote:
> On Wed, 2012-08-01 at 07:43 +0800, Fengguang Wu wrote:
> > On Tue, Jul 31, 2012 at 09:13:39AM -0400, Steven Rostedt wrote:
> > > On Tue, 2012-07-31 at 15:50 +0300, Avi Kivity wrote:
> > > > On 07/31/2012 03:43 PM, Steven Rostedt
On Tue, Jul 31, 2012 at 07:51:39PM -0400, Steven Rostedt wrote:
> On Wed, 2012-08-01 at 07:43 +0800, Fengguang Wu wrote:
> > On Tue, Jul 31, 2012 at 09:13:39AM -0400, Steven Rostedt wrote:
> > > On Tue, 2012-07-31 at 15:50 +0300, Avi Kivity wrote:
> > > > On 07/31/2012 03:43 PM, Steven Rostedt
On Wed, 2012-08-01 at 07:43 +0800, Fengguang Wu wrote:
> On Tue, Jul 31, 2012 at 09:13:39AM -0400, Steven Rostedt wrote:
> > On Tue, 2012-07-31 at 15:50 +0300, Avi Kivity wrote:
> > > On 07/31/2012 03:43 PM, Steven Rostedt wrote:
> >
> > > That would be better. A hypervisor might be real-time
On Fri, Jul 27, 2012 at 10:14:59PM +0200, Jean Delvare wrote:
> Right now we have support for explicit platform device IDs, as well as
> ID-less platform devices when a given device type can only have one
> instance. However there are cases where multiple instances of a device
> type can exist,
Seth Jennings wrote:
> As part of the Kconfig rework for drivers/crypto/nx, the meaning of
> CONFIG_CRYPTO_DEV_NX was changed. At the same time this commit was
> heading upstream
>
> fd297b3a7302ab866306f53c1fd1e97b083fe83e
> powerpc: Enable pseries hardware RNG and crypto module
>
> still
Hi Seth,
On Tue, 31 Jul 2012 18:34:51 -0500 Seth Jennings
wrote:
>
> diff --git a/arch/powerpc/configs/pseries_defconfig
> b/arch/powerpc/configs/pseries_defconfig
> index 1f65b3c..9f4a936 100644
> --- a/arch/powerpc/configs/pseries_defconfig
> +++ b/arch/powerpc/configs/pseries_defconfig
> @@
On Tue, Jul 31, 2012 at 09:13:39AM -0400, Steven Rostedt wrote:
> On Tue, 2012-07-31 at 15:50 +0300, Avi Kivity wrote:
> > On 07/31/2012 03:43 PM, Steven Rostedt wrote:
>
> > That would be better. A hypervisor might be real-time capable (with
> > some effort kvm can do this), so we don't want to
As part of the Kconfig rework for drivers/crypto/nx, the meaning of
CONFIG_CRYPTO_DEV_NX was changed. At the same time this commit was
heading upstream
fd297b3a7302ab866306f53c1fd1e97b083fe83e
powerpc: Enable pseries hardware RNG and crypto module
still used the old meaning, set
On Wed, Aug 01, 2012 at 03:19:10AM +0400, Evgeniy Polyakov wrote:
> On Fri, Jul 27, 2012 at 10:04:44AM +0300, Felipe Balbi (ba...@ti.com) wrote:
> > > Feel free to add my acked-by: Evgeniy Polyakov
> >
> > I thought you would :-p Then I guess Tony, maybe ?
>
> Greg, will you pick this patchset?
On 07/31/2012 11:58 AM, Salar Ali Mumtaz wrote:
> Now the debug_info only shows y/n/m values.
>
or no value at all??
for CONFIG_BINFMT_ELF:
Kernel support for ELF binaries (BINFMT_ELF)
type: boolean
unknown property: symbol
dep: ( MMU y && (BROKEN n || !FRV ) ) =y
prompt: Kernel
Linus Walleij wrote:
>
> On Fri, Jul 20, 2012 at 10:58 PM, Sean Paul wrote:
>
> > Move gpc4 to the end of the automatically processed gpio controllers so
> > we don't taint the automatic offset calculation.
> >
> > This bug caused all controllers coming after gpc4 to map to the
> > incorrect
On 07/31/2012 04:03 PM, Rob Herring wrote:
> On 07/30/2012 02:47 AM, Thierry Reding wrote:
>> On Sun, Jul 29, 2012 at 07:13:57PM +0200, Linus Walleij wrote:
>>> On Mon, Jul 23, 2012 at 1:59 PM, Thierry Reding
>>> wrote:
>>>
This commit adds a driver for the Avionic Design N-bit GPIO
On Wednesday, August 01, 2012 1:39 AM Damien Cassou wrote:
>
> From: Damien Cassou
>
> The various devm_ functions allocate memory that is released when a driver
> detaches. This patch uses these functions for data that is allocated in
> the probe function of a platform device and is only
On Tue, 2012-07-31 at 17:13 +0100, Mark Brown wrote:
> On Tue, Jul 31, 2012 at 01:11:01PM -0300, Herton Ronaldo Krzesinski wrote:
>
> > Hi, this doesn't build on 3.2:
>
> > linux-stable/sound/soc/soc-dapm.c: In function 'soc_dapm_shutdown_codec':
> > linux-stable/sound/soc/soc-dapm.c:2982:18:
On Fri, Jul 27, 2012 at 10:04:44AM +0300, Felipe Balbi (ba...@ti.com) wrote:
> > Feel free to add my acked-by: Evgeniy Polyakov
>
> I thought you would :-p Then I guess Tony, maybe ?
Greg, will you pick this patchset?
It is fairly simple and without any behaviour changes, but things look
like
On 07/30/2012 11:25 AM, Mark Brown wrote:
> On Mon, Jul 30, 2012 at 11:00:04AM -0600, Stephen Warren wrote:
>> On 07/29/2012 02:36 PM, Mark Brown wrote:
>>> On Fri, Jul 27, 2012 at 01:01:56PM -0600, Stephen Warren wrote:
>
>> I had implemented this in regmap since you'd specifically mentioned
>>
On Tue, Jul 31, 2012 at 05:48:38PM -0500, Alexis R. Cortes wrote:
> This patch is intended to work around a known issue on the
> SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
> between a device and the host past the usual handshake timeout,
> and if that happens on the first
On Tue, Jul 31, 2012 at 05:54:04PM -0500, Alexis Cortes wrote:
> Hi Greg,
>
> I have resent the patch. Hopefully it know arrives properly. BTW, I'm using
> Thunderbird configured as described in Documentation/email-clients.txt for
> sending the patch.
The resend looks like it worked properly,
On Tuesday 31 July 2012, Cyril Chemparathy wrote:
> Texas Instruments Keystone family of multicore devices now includes an
> upcoming slew of Cortex A15 based devices. This patch adds basic definitions
> for a new Keystone sub-architecture in ARM.
>
> Subsequent patches in this series will
On Tue, Jul 31, 2012 at 03:51:05PM -0700, Jon Mason wrote:
> On Tue, Jul 31, 2012 at 03:23:38PM -0700, Greg KH wrote:
> > On Sun, Jul 29, 2012 at 05:26:33PM -0700, Jon Mason wrote:
> > > + * You should have received a copy of the GNU General Public License
> > > + * along with this program; if
On Tue, 2012-07-31 at 18:03 +0100, Mel Gorman wrote:
> On Tue, Jul 31, 2012 at 06:00:51PM +0100, Mel Gorman wrote:
> > On Tue, Jul 31, 2012 at 01:42:04PM -0300, Herton Ronaldo Krzesinski wrote:
> > > On Tue, Jul 31, 2012 at 05:43:16AM +0100, Ben Hutchings wrote:
> > > > 3.2-stable review patch.
On Keystone platforms, physical memory is entirely outside the 32-bit
addressible range. Therefore, the (bank->start > ULONG_MAX) check below marks
the entire system memory as highmem, and this causes unpleasentness all over.
This patch eliminates the extra bank start check (against ULONG_MAX)
From: Vitaly Andrianov
On some PAE systems (e.g. TI Keystone), memory is above the 32-bit addressible
limit, and the interconnect provides an aliased view of parts of physical
memory in the 32-bit addressible space. This alias is strictly for boot time
usage, and is not otherwise usable because
From: Vitaly Andrianov
This patch fixes the alloc_init_pud() function to use phys_addr_t instead of
unsigned long when passing in the phys argument.
This is an extension to commit 97092e0c56830457af0639f6bd904537a150ea4a, which
applied similar changes elsewhere in the ARM memory management
This patch adds an architecture defined override for ARCH_LOW_ADDRESS_LIMIT.
On PAE systems, the absence of this override causes bootmem to incorrectly
limit itself to 32-bit addressable physical memory.
Signed-off-by: Cyril Chemparathy
Signed-off-by: Vitaly Andrianov
---
This patch modifies the highmem sanity checking code to use physical addresses
instead. This change eliminates the wrap-around problems associated with the
original virtual address based checks, and this simplifies the code a bit.
The one constraint imposed here is that low physical memory must
Keystone platforms have their physical memory mapped at an address outside the
32-bit physical range. A Keystone machine with 16G of RAM would find its
memory at 0x08 - 0x0b.
For boot purposes, the interconnect supports a limited alias of some of this
memory within the 32-bit
This patch adds basic SMP support for Keystone machines. Nothing very fancy
here, just enough to get 4 CPUs booted up. This does not include support for
hotplug, etc.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arch/arm/Kconfig|1 +
This patch replaces the original physical offset patching implementation
with one that uses the newly added patching framework. In the process, we now
unconditionally initialize the __pv_phys_offset and __pv_offset globals in the
head.S code.
Signed-off-by: Cyril Chemparathy
---
This patch moves the TTBR1 offset calculation and the T1SZ calculation out
of the TTB setup assembly code. This should not affect functionality in
any way, but improves code readability as well as readability of subsequent
patches in this series.
Signed-off-by: Cyril Chemparathy
Signed-off-by:
The original phys_to_virt/virt_to_phys patching implementation relied on early
patching prior to MMU initialization. On PAE systems running out of >4G
address space, this would have entailed an additional round of patching after
switching over to the high address space.
The approach implemented
From: Vitaly Andrianov
The free_memmap() was mistakenly using unsigned long type to represent
physical addresses. This breaks on PAE systems where memory could be placed
above the 32-bit addressible limit.
This patch fixes this function to properly use phys_addr_t instead.
Signed-off-by:
This patch adds support for 64-bit physical addresses in virt_to_phys
patching. This does not do real 64-bit add/sub, but instead patches in the
upper 32-bits of the phys_offset directly into the output of virt_to_phys.
In addition to adding 64-bit support, this patch also adds a
This patch redefines the early boot time use of the R4 register to steal a few
low order bits (ARCH_PGD_SHIFT bits), allowing for up to 38-bit physical
addresses.
This is probably not the best means to the end, and a better alternative may
be to modify the head.S register allocations to fit in
This patch fixes up the types used when converting back and forth between
physical and virtual addresses.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
arch/arm/include/asm/memory.h | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git
Texas Instruments Keystone family of multicore devices now includes an
upcoming slew of Cortex A15 based devices. This patch adds basic definitions
for a new Keystone sub-architecture in ARM.
Subsequent patches in this series will extend support to include SMP and take
advantage of the large
This series is a follow on to the RFC series posted earlier (archived at [1]).
The major change introduced here is the modification to the kernel patching
mechanism for phys_to_virt/virt_to_phys, in order to support LPAE platforms
that require late patching. In addition to these changes, we've
From: Vitaly Andrianov
This patch fixes the initrd setup code to use phys_addr_t instead of assuming
32-bit addressing. Without this we cannot boot on systems where initrd is
located above the 4G physical address limit.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
---
This patch adds a step in the init sequence, in order to recreate the kernel
code/data page table mappings prior to full paging initialization. This is
necessary on LPAE systems that run out of a physical address space outside the
4G limit. On these systems, this implementation provides a
This patch allows ARM processor setup functions (*_setup in proc-*.S) to
indicate that the page table has already been programmed. This is
done by setting r4 (page table pointer) to -1 before returning from the
processor setup handler.
This capability is particularly needed on LPAE systems,
This patch cleans up the highmem sanity check code by simplifying the range
checks with a pre-calculated size_limit. This patch should otherwise have no
functional impact on behavior.
This patch also removes a redundant (bank->start < vmalloc_limit) check, since
this is already covered by the
This patch adds TTBR accessor macros, and modifies cpu_get_pgd() and
the LPAE version of cpu_set_reserved_ttbr0() to use these instead.
In the process, we also fix these functions to correctly handle cases
where the physical address lies beyond the 4G limit of 32-bit addressing.
Signed-off-by:
This patch modifies the switch_mm() processor functions to use 64-bit
addresses. We use u64 instead of phys_addr_t, in order to avoid having config
dependent register usage when calling into switch_mm assembly code.
The changes in this patch are primarily adjustments for registers used for
1 - 100 of 1328 matches
Mail list logo
