On 09/03/2012 02:26 AM, Jiri Kosina wrote:
On Sun, 2 Sep 2012, Xin Tong wrote:
3. can two different processes have their CR3 being the same value
even though they have different first level page tables ?
Yes, if they are created by clone(CLONE_VM). In such case they share the
same mm_struct,
On Tue, Sep 04, 2012 at 08:46:12AM +0200, Paolo Bonzini wrote:
> Il 04/09/2012 04:21, Nicholas A. Bellinger ha scritto:
> >> @@ -112,6 +118,9 @@ static void virtscsi_complete_cmd(struct virtio_scsi
> >> *vscsi, void *buf)
> >>struct virtio_scsi_cmd *cmd = buf;
> >>struct scsi_cmnd *sc =
Adding support for LM74 and LM71 chips
Signed-off-by: Christophe Leroy
diff -u linux-3.5-vanilla/drivers/hwmon/Kconfig linux-3.5/drivers/hwmon/Kconfig
--- linux-3.5-vanilla/drivers/hwmon/Kconfig 2012-07-21 22:58:29.0
+0200
+++ linux-3.5/drivers/hwmon/Kconfig 2012-08-25
Removing the 3wire limitation on LM70 as the component also allows
operation on 4wire SPI bus
Signed-off-by: Christophe Leroy
diff -u linux-3.5-vanilla/drivers/hwmon/lm70.c linux-3.5/drivers/hwmon/lm70.c
--- linux-3.5-vanilla/drivers/hwmon/lm70.c 2012-07-21 22:58:29.0
+0200
+++
Hello,
The two following patches do:
1) Allow the use of NS LM70 with a 4 wire SPI bus too, since the component
allows both configuration
2) Adds support for NS LM71 and LM74
Regards
Christophe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Mon, Sep 3, 2012 at 3:29 PM, G.Shark Jeong wrote:
> From: "G.Shark Jeong"
>
> LM3554 and LM3556 have similar functions but very different register map.
> This driver is a general version for lm3554 and lm3556 both,led chips of TI.
> lm3556 driver can be replaced by this driver.
>
> LM3554 :
>
On 09/03/2012 09:08 PM, Michal Hocko wrote:
> On Mon 03-09-12 19:46:51, Glauber Costa wrote:
>> Here is a new attempt to lay down a path that will allow us to deprecate
>> the non-hierarchical mode of operation from memcg. Unlike what I posted
>> before, I am making this behavior conditional on a
Aiaiai! :-) [1] [2]
I've build-tested this using aiaiai and it reports that this change breaks the
build:
dedekind@blue:~/git/maintaining$ ./verify ../l2-mtd/ mpc5121_nfc <
~/tmp/julia2.mbox
Tested the patch(es) on top of the following commits:
ba64756 Quick fixes - applied by aiaiai
651c6fa
>
>> + of the root memcg, regardless of their positioning in the tree.
>> +
>> + Use of flat hierarchies is highly discouraged, but has been the
>> + default for performance reasons for quite some time. Setting this flag
>> + to on will make hierarchical accounting the
powernow-k8 is quite prematurely crying Hooray and outputs diagnostic
messages, although the actual initialization can still fail.
Since now we may have acpi-cpufreq already loaded, we move the
messages at the end of the init routine to avoid confusing output
if the loading of powernow-k8 should
On 08/29/2012 11:49 AM, Nicolas Ferre :
> If the number of ports present on the SoC/board is not the maximum
> and that the platform data is not filled with all data, there is
> an easy way to mess the PIO setup for this interface.
> This quick fix addresses mis-configuration in USB host platform
From: Matthew Garrett
The programming model for P-states on modern AMD CPUs is very similar to
that of Intel and VIA. It makes sense to consolidate this support into one
driver rather than duplicating functionality between two of them. This
patch adds support for AMDs with hardware P-state
One feature present in powernow-k8 that isn't present in acpi-cpufreq
is support for enabling or disabling AMD's core performance boost
technology. This patch adds support to acpi-cpufreq, but also
includes support for Intel's dynamic acceleration.
The original boost disabling sysfs file was per
The powernow-k8 driver supported a sysfs knob called "cpb", which was
instantiated per CPU, but actually acted globally for the whole
system. To keep some compatibility with this feature, we re-introduce
this behavior here, but:
a) only enable it on AMD CPUs and
b) protect it with a Kconfig switch
From: Matthew Garrett
These chips are now supported by acpi-cpufreq, so we can delete all the
code handling them.
Andre: Tighten the deprecation warning message. Trigger load of
acpi-cpufreq and let the load of the module finally fail.
This avoids the problem of users ending up without any
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo wrote:
> LP5523 driver supports both LP5523 and LP55231.
> The i2c device id is one of the two - lp5523 or lp55231.
> So it's better to use matching i2c device id while enumerating the device
> and naming LED channels.
>
Applied, thanks.
-Bryan
>
To workaround some Windows specific behavior, the ACPI _PSD table
on AMD desktop boards advertises all cores as dependent, meaning
that they all can only use the same P-state. acpi-cpufreq strictly
obeys this description, instantiating one CPU only and symlinking
the others. But the hardware can
cpufreq modules are often loaded from init scripts that assume that
all recent AMD systems will use powernow-k8.
To inform the user of the change of support and ease the transition
to acpi-cpufreq, emit a warning message.
Signed-off-by: Andre Przywara
---
drivers/cpufreq/Kconfig.x86 | 3 ++-
From: Matthew Garrett
Some AMD systems may round the frequencies in ACPI tables to 100MHz
boundaries. We can obtain the real frequencies from MSRs, so add a quirk
to fix these frequencies up on AMD systems.
Signed-off-by: Matthew Garrett
Signed-off-by: Andre Przywara
---
Hi,
now the second, revised version of the patch set. I now tested loading
both drivers after each other in several combinations, after two bug
fixes this now works as expected.
I added a patch to move messages from powernow-k8 after the initialization
phase, so it remains silent if driver
> > After merging the drm tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> > drivers/usb/Kconfig:76:
The kernel doesn't check pid on a negative values, so if
you would try to write -2 in /proc/sys/kernel/ns_last_pid,
you will get a kernel panic.
In this case the next pid is -1, and alloc_pidmap will try to access
to a nonexistent pidmap.
map = _ns->pidmap[pid/BITS_PER_PAGE];
Cc: Andrew Morton
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo wrote:
> To support LP55231 device, the device id is added.
> Additionally, the i2c driver name is changed from lp5523 to lp5523x.
>
Applied to my for-next.
-Bryan
> Signed-off-by: Milo(Woogyom) Kim
> ---
> drivers/leds/leds-lp5523.c | 10
On Tuesday 04 September 2012, Stephen Rothwell wrote:
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/mm/mmu.c between commit a849088aa155 ("ARM: Fix ioremap() of
> address zero") from the arm-current tree and commit c2794437091a ("ARM:
> Add fixed PCI i/o mapping")
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo wrote:
> New TI LP55231 device has same I2C register layout as LP5523.
> Therefore, all of LED operations can be shared with the LP5523 driver.
>
> To support new LP55231 device explicitly, the device description
> is added in the configuration file.
2012/9/3, Jan Kara :
> Hello,
>
> On Fri 31-08-12 12:51:58, Namjae Jeon wrote:
>> From: Namjae Jeon
>>
>> While mapping logical blocks of a file to physical blocks on the
>> partition,
>> everytime UDF read file metadata from the begining which decrease
>> preformance.
>> The drawback of this
On Sat, 2012-09-01 at 18:33 +0200, Julia Lawall wrote:
> From: Julia Lawall
>
> devm free functions should not have to be explicitly used.
>
> A semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem
Let's CC LKML and Paul.
On Sat, 2012-09-01 at 22:19 -0700, Subodh Nijsure wrote:
> Hello,
>
> I am running 3.6-rc4 kernel on my MX28 based board and every time I
> mount UBI file system I see following warning.
> Anybody else seen this errors, particularly those running it on MXS
> platform?
On Sun, Sep 2, 2012 at 5:58 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks!
Linus Walleij
--
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, Sep 03, 2012 at 01:26:26PM -0700, Guenter Roeck wrote:
> Actually, spi_master_put() after spi_alloc_master() must _not_ be followed
> by kfree(). The memory is already freed with the call to spi_master_put()
> through spi_master_class, which registers a release function. Calling both
>
On Sun, Sep 2, 2012 at 5:58 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks!
Linus Walleij
--
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 Sun, Sep 2, 2012 at 2:08 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks!
Linus Walleij
--
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 Sun, Sep 2, 2012 at 2:04 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks!
Linus Walleij
--
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
> Today's linux-next merge of the pci tree got a conflict in
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c between commit
> 8eee694c3e66 ("bnx2x: fix unload previous driver flow when flr-capable")
> from Linus' tree and commit 2a80eebcbf3e ("bnx2x: Use PCI Express
> Capability accessors")
Hi all,
Changes since 20120824:
The pci tree gained conflicts against Linus' tree.
The v4l-dvb tree gained a conflict against the arm tree.
The ubi tree lost its build failure.
The scsi tree lost its conflict.
The drm tree lost its build failure and conflicts.
The sound tree lost its build
On Mon, Sep 03, 2012 at 10:54:49PM +0200, Oliver Hartkopp wrote:
> On 03.09.2012 20:29, Fabio Baltieri wrote:
>
> > On Mon, Sep 03, 2012 at 08:13:35PM +0200, Kurt Van Dijck wrote:
> >> On Mon, Sep 03, 2012 at 02:40:39PM +0200, Marc Kleine-Budde wrote:
> >>> The net->ifindex is unique. But it's
LP5523 driver supports both LP5523 and LP55231.
The i2c device id is one of the two - lp5523 or lp55231.
So it's better to use matching i2c device id while enumerating the device
and naming LED channels.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5523.c | 10 ++
1
New TI LP55231 device has same I2C register layout as LP5523.
Therefore, all of LED operations can be shared with the LP5523 driver.
To support new LP55231 device explicitly, the device description
is added in the configuration file.
Signed-off-by: Milo(Woogyom) Kim
---
To support LP55231 device, the device id is added.
Additionally, the i2c driver name is changed from lp5523 to lp5523x.
Signed-off-by: Milo(Woogyom) Kim
---
drivers/leds/leds-lp5523.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/leds/leds-lp5523.c
On 08/30/2012 12:15 PM, Sachin Agarwalla wrote:
Dear Sir/Madam,
I have some questions on development of linux kernel as follows:-
1.I want to know the location of files in linux kernel source code that
contains timer initialization and scheduler part.
Scheduler source code is in
Hi ,
After merging the final tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:
net/built-in.o: In function `tcp_fastopen_ctx_free':
tcp_fastopen.c:(.text+0x5cc5c): undefined reference to `crypto_destroy_tfm'
net/built-in.o: In function `tcp_fastopen_reset_cipher':
Stephen Warren wrote @ Wed, 15 Aug 2012 18:13:18 +0200:
> On 08/14/2012 11:47 PM, Hiroshi Doyu wrote:
> > The commit c3b1a35 "debugfs: make sure that debugfs_create_file() gets
> > used only for regulars" doesn't allow to use debugfs_create_file() for
> > dir. Keep debugfs data in smmu_device
The following changes since commit 4cbe5a555fa58a79b6ecbb6c531b8bab0650778d:
Linux 3.6-rc4 (2012-09-01 10:39:58 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubi.git tags/upstream-3.6-rc5
for you to fetch changes up to
Il 04/09/2012 04:21, Nicholas A. Bellinger ha scritto:
>> @@ -112,6 +118,9 @@ static void virtscsi_complete_cmd(struct virtio_scsi
>> *vscsi, void *buf)
>> struct virtio_scsi_cmd *cmd = buf;
>> struct scsi_cmnd *sc = cmd->sc;
>> struct virtio_scsi_cmd_resp *resp = >resp.cmd;
>> +
On Tue, Sep 4, 2012 at 5:58 AM, Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL
On Mon, Sep 3, 2012 at 4:06 PM, Hein Tibosch wrote:
> 1. The first draft of the patches worked with the max allowable value for
> the SRC_WIDTH & DST_WIDTH fields: 0,1,2,3... Viresh thought it was not
> transparent enough, he suggested to make it simpler with a binary choice of
> 32- or 64-bits,
Hi Javier,
On 09/03/2012 10:27 AM, Javier Martin wrote:
The following commit should be reverted:
0865a75d4166bddc533fd50831829ceefb94f9b0
The bug this patch is meant to solve doesn't occur in Visstrim_M10 boards.
Furthermore, after applying this patch sound in Visstrim_M10 is played
at slower
Jan Kara writes:
> On Mon 03-09-12 10:45:15, Kristian Nielsen wrote:
>> It appears that ext3 and ext4 fdatasync() does not fully sync data to
>> disk. Specifically, when new data is written at the end (so that the file
>> length is increased), not all of the new data is synced by fdatasync().
>
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mm/mmu.c between commit a849088aa155 ("ARM: Fix ioremap() of
address zero") from the arm-current tree and commit c2794437091a ("ARM:
Add fixed PCI i/o mapping") from the arm-soc tree.
I am not sure how to fix this,
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mm/mmu.c between commit a849088aa155 (ARM: Fix ioremap() of
address zero) from the arm-current tree and commit c2794437091a (ARM:
Add fixed PCI i/o mapping) from the arm-soc tree.
I am not sure how to fix this, so I
Jan Kara j...@suse.cz writes:
On Mon 03-09-12 10:45:15, Kristian Nielsen wrote:
It appears that ext3 and ext4 fdatasync() does not fully sync data to
disk. Specifically, when new data is written at the end (so that the file
length is increased), not all of the new data is synced by
Hi Javier,
On 09/03/2012 10:27 AM, Javier Martin wrote:
The following commit should be reverted:
0865a75d4166bddc533fd50831829ceefb94f9b0
The bug this patch is meant to solve doesn't occur in Visstrim_M10 boards.
Furthermore, after applying this patch sound in Visstrim_M10 is played
at slower
On Mon, Sep 3, 2012 at 4:06 PM, Hein Tibosch hein_tibo...@yahoo.es wrote:
1. The first draft of the patches worked with the max allowable value for
the SRC_WIDTH DST_WIDTH fields: 0,1,2,3... Viresh thought it was not
transparent enough, he suggested to make it simpler with a binary choice of
On Tue, Sep 4, 2012 at 5:58 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Dave,
After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
drivers/gpu/drm/udl/Kconfig:1:
Il 04/09/2012 04:21, Nicholas A. Bellinger ha scritto:
@@ -112,6 +118,9 @@ static void virtscsi_complete_cmd(struct virtio_scsi
*vscsi, void *buf)
struct virtio_scsi_cmd *cmd = buf;
struct scsi_cmnd *sc = cmd-sc;
struct virtio_scsi_cmd_resp *resp = cmd-resp.cmd;
+struct
The following changes since commit 4cbe5a555fa58a79b6ecbb6c531b8bab0650778d:
Linux 3.6-rc4 (2012-09-01 10:39:58 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubi.git tags/upstream-3.6-rc5
for you to fetch changes up to
Stephen Warren swar...@wwwdotorg.org wrote @ Wed, 15 Aug 2012 18:13:18 +0200:
On 08/14/2012 11:47 PM, Hiroshi Doyu wrote:
The commit c3b1a35 debugfs: make sure that debugfs_create_file() gets
used only for regulars doesn't allow to use debugfs_create_file() for
dir. Keep debugfs data in
Hi ,
After merging the final tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:
net/built-in.o: In function `tcp_fastopen_ctx_free':
tcp_fastopen.c:(.text+0x5cc5c): undefined reference to `crypto_destroy_tfm'
net/built-in.o: In function `tcp_fastopen_reset_cipher':
On 08/30/2012 12:15 PM, Sachin Agarwalla wrote:
Dear Sir/Madam,
I have some questions on development of linux kernel as follows:-
1.I want to know the location of files in linux kernel source code that
contains timer initialization and scheduler part.
Scheduler source code is in
To support LP55231 device, the device id is added.
Additionally, the i2c driver name is changed from lp5523 to lp5523x.
Signed-off-by: Milo(Woogyom) Kim milo@ti.com
---
drivers/leds/leds-lp5523.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git
New TI LP55231 device has same I2C register layout as LP5523.
Therefore, all of LED operations can be shared with the LP5523 driver.
To support new LP55231 device explicitly, the device description
is added in the configuration file.
Signed-off-by: Milo(Woogyom) Kim milo@ti.com
---
LP5523 driver supports both LP5523 and LP55231.
The i2c device id is one of the two - lp5523 or lp55231.
So it's better to use matching i2c device id while enumerating the device
and naming LED channels.
Signed-off-by: Milo(Woogyom) Kim milo@ti.com
---
drivers/leds/leds-lp5523.c | 10
On Mon, Sep 03, 2012 at 10:54:49PM +0200, Oliver Hartkopp wrote:
On 03.09.2012 20:29, Fabio Baltieri wrote:
On Mon, Sep 03, 2012 at 08:13:35PM +0200, Kurt Van Dijck wrote:
On Mon, Sep 03, 2012 at 02:40:39PM +0200, Marc Kleine-Budde wrote:
The net-ifindex is unique. But it's only an
Hi all,
Changes since 20120824:
The pci tree gained conflicts against Linus' tree.
The v4l-dvb tree gained a conflict against the arm tree.
The ubi tree lost its build failure.
The scsi tree lost its conflict.
The drm tree lost its build failure and conflicts.
The sound tree lost its build
Today's linux-next merge of the pci tree got a conflict in
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c between commit
8eee694c3e66 (bnx2x: fix unload previous driver flow when flr-capable)
from Linus' tree and commit 2a80eebcbf3e (bnx2x: Use PCI Express
Capability accessors) from the pci
On Sun, Sep 2, 2012 at 2:04 AM, Axel Lin axel@gmail.com wrote:
Signed-off-by: Axel Lin axel@gmail.com
Applied, thanks!
Linus Walleij
--
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 Sun, Sep 2, 2012 at 2:08 AM, Axel Lin axel@gmail.com wrote:
Signed-off-by: Axel Lin axel@gmail.com
Applied, thanks!
Linus Walleij
--
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, Sep 03, 2012 at 01:26:26PM -0700, Guenter Roeck wrote:
Actually, spi_master_put() after spi_alloc_master() must _not_ be followed
by kfree(). The memory is already freed with the call to spi_master_put()
through spi_master_class, which registers a release function. Calling both
On Sun, Sep 2, 2012 at 5:58 AM, Axel Lin axel@gmail.com wrote:
Signed-off-by: Axel Lin axel@gmail.com
Applied, thanks!
Linus Walleij
--
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 Sun, Sep 2, 2012 at 5:58 AM, Axel Lin axel@gmail.com wrote:
Signed-off-by: Axel Lin axel@gmail.com
Applied, thanks!
Linus Walleij
--
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
Let's CC LKML and Paul.
On Sat, 2012-09-01 at 22:19 -0700, Subodh Nijsure wrote:
Hello,
I am running 3.6-rc4 kernel on my MX28 based board and every time I
mount UBI file system I see following warning.
Anybody else seen this errors, particularly those running it on MXS
platform?
I
On Sat, 2012-09-01 at 18:33 +0200, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
devm free functions should not have to be explicitly used.
A semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)
Pushed to l2-mtd.git, thanks!
--
Best Regards,
2012/9/3, Jan Kara j...@suse.cz:
Hello,
On Fri 31-08-12 12:51:58, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
While mapping logical blocks of a file to physical blocks on the
partition,
everytime UDF read file metadata from the begining which decrease
preformance.
The
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo milo@ti.com wrote:
New TI LP55231 device has same I2C register layout as LP5523.
Therefore, all of LED operations can be shared with the LP5523 driver.
To support new LP55231 device explicitly, the device description
is added in the
On Tuesday 04 September 2012, Stephen Rothwell wrote:
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mm/mmu.c between commit a849088aa155 (ARM: Fix ioremap() of
address zero) from the arm-current tree and commit c2794437091a (ARM:
Add fixed PCI i/o mapping) from the
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo milo@ti.com wrote:
To support LP55231 device, the device id is added.
Additionally, the i2c driver name is changed from lp5523 to lp5523x.
Applied to my for-next.
-Bryan
Signed-off-by: Milo(Woogyom) Kim milo@ti.com
---
The kernel doesn't check pid on a negative values, so if
you would try to write -2 in /proc/sys/kernel/ns_last_pid,
you will get a kernel panic.
In this case the next pid is -1, and alloc_pidmap will try to access
to a nonexistent pidmap.
map = pid_ns-pidmap[pid/BITS_PER_PAGE];
Cc: Andrew
After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
drivers/usb/Kconfig:76: symbol
Hi,
now the second, revised version of the patch set. I now tested loading
both drivers after each other in several combinations, after two bug
fixes this now works as expected.
I added a patch to move messages from powernow-k8 after the initialization
phase, so it remains silent if driver
From: Matthew Garrett m...@redhat.com
Some AMD systems may round the frequencies in ACPI tables to 100MHz
boundaries. We can obtain the real frequencies from MSRs, so add a quirk
to fix these frequencies up on AMD systems.
Signed-off-by: Matthew Garrett m...@redhat.com
Signed-off-by: Andre
cpufreq modules are often loaded from init scripts that assume that
all recent AMD systems will use powernow-k8.
To inform the user of the change of support and ease the transition
to acpi-cpufreq, emit a warning message.
Signed-off-by: Andre Przywara andre.przyw...@amd.com
---
To workaround some Windows specific behavior, the ACPI _PSD table
on AMD desktop boards advertises all cores as dependent, meaning
that they all can only use the same P-state. acpi-cpufreq strictly
obeys this description, instantiating one CPU only and symlinking
the others. But the hardware can
On Tue, Sep 4, 2012 at 3:06 PM, Kim, Milo milo@ti.com wrote:
LP5523 driver supports both LP5523 and LP55231.
The i2c device id is one of the two - lp5523 or lp55231.
So it's better to use matching i2c device id while enumerating the device
and naming LED channels.
Applied, thanks.
From: Matthew Garrett m...@redhat.com
These chips are now supported by acpi-cpufreq, so we can delete all the
code handling them.
Andre: Tighten the deprecation warning message. Trigger load of
acpi-cpufreq and let the load of the module finally fail.
This avoids the problem of users ending up
The powernow-k8 driver supported a sysfs knob called cpb, which was
instantiated per CPU, but actually acted globally for the whole
system. To keep some compatibility with this feature, we re-introduce
this behavior here, but:
a) only enable it on AMD CPUs and
b) protect it with a Kconfig switch
One feature present in powernow-k8 that isn't present in acpi-cpufreq
is support for enabling or disabling AMD's core performance boost
technology. This patch adds support to acpi-cpufreq, but also
includes support for Intel's dynamic acceleration.
The original boost disabling sysfs file was per
From: Matthew Garrett m...@redhat.com
The programming model for P-states on modern AMD CPUs is very similar to
that of Intel and VIA. It makes sense to consolidate this support into one
driver rather than duplicating functionality between two of them. This
patch adds support for AMDs with
On 08/29/2012 11:49 AM, Nicolas Ferre :
If the number of ports present on the SoC/board is not the maximum
and that the platform data is not filled with all data, there is
an easy way to mess the PIO setup for this interface.
This quick fix addresses mis-configuration in USB host platform data
powernow-k8 is quite prematurely crying Hooray and outputs diagnostic
messages, although the actual initialization can still fail.
Since now we may have acpi-cpufreq already loaded, we move the
messages at the end of the init routine to avoid confusing output
if the loading of powernow-k8 should
+ of the root memcg, regardless of their positioning in the tree.
+
+ Use of flat hierarchies is highly discouraged, but has been the
+ default for performance reasons for quite some time. Setting this flag
+ to on will make hierarchical accounting the default. It is
Aiaiai! :-) [1] [2]
I've build-tested this using aiaiai and it reports that this change breaks the
build:
dedekind@blue:~/git/maintaining$ ./verify ../l2-mtd/ mpc5121_nfc
~/tmp/julia2.mbox
Tested the patch(es) on top of the following commits:
ba64756 Quick fixes - applied by aiaiai
651c6fa
On 09/03/2012 09:08 PM, Michal Hocko wrote:
On Mon 03-09-12 19:46:51, Glauber Costa wrote:
Here is a new attempt to lay down a path that will allow us to deprecate
the non-hierarchical mode of operation from memcg. Unlike what I posted
before, I am making this behavior conditional on a
On Mon, Sep 3, 2012 at 3:29 PM, G.Shark Jeong gshark.je...@gmail.com wrote:
From: G.Shark Jeong gshark.je...@gmail.com
LM3554 and LM3556 have similar functions but very different register map.
This driver is a general version for lm3554 and lm3556 both,led chips of TI.
lm3556 driver can be
Hello,
The two following patches do:
1) Allow the use of NS LM70 with a 4 wire SPI bus too, since the component
allows both configuration
2) Adds support for NS LM71 and LM74
Regards
Christophe
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Removing the 3wire limitation on LM70 as the component also allows
operation on 4wire SPI bus
Signed-off-by: Christophe Leroy christophe.le...@c-s.fr
diff -u linux-3.5-vanilla/drivers/hwmon/lm70.c linux-3.5/drivers/hwmon/lm70.c
--- linux-3.5-vanilla/drivers/hwmon/lm70.c 2012-07-21
Adding support for LM74 and LM71 chips
Signed-off-by: Christophe Leroy christophe.le...@c-s.fr
diff -u linux-3.5-vanilla/drivers/hwmon/Kconfig linux-3.5/drivers/hwmon/Kconfig
--- linux-3.5-vanilla/drivers/hwmon/Kconfig 2012-07-21 22:58:29.0
+0200
+++ linux-3.5/drivers/hwmon/Kconfig
On Tue, Sep 04, 2012 at 08:46:12AM +0200, Paolo Bonzini wrote:
Il 04/09/2012 04:21, Nicholas A. Bellinger ha scritto:
@@ -112,6 +118,9 @@ static void virtscsi_complete_cmd(struct virtio_scsi
*vscsi, void *buf)
struct virtio_scsi_cmd *cmd = buf;
struct scsi_cmnd *sc = cmd-sc;
On 09/03/2012 02:26 AM, Jiri Kosina wrote:
On Sun, 2 Sep 2012, Xin Tong wrote:
3. can two different processes have their CR3 being the same value
even though they have different first level page tables ?
Yes, if they are created by clone(CLONE_VM). In such case they share the
same mm_struct,
On Mon, Sep 3, 2012 at 3:33 PM, Lee Jones lee.jo...@linaro.org wrote:
Author: Lee Jones lee.jo...@linaro.org
Date: Fri Aug 24 12:40:58 2012 +0100
ARM: ux500: Provide SMSC911x fixed-regulator when not booting DT
The SMSC911x Ethernet chip requires a fixed-regulator in order to
On Tue, Sep 4, 2012 at 10:22 AM, Dave Airlie airl...@linux.ie wrote:
After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL
601 - 700 of 1298 matches
Mail list logo
