Hi Jingoo,
On Friday 27 September 2013 12:28:21 Jingoo Han wrote:
> On Thursday, September 26, 2013 9:08 PM, Tomi Valkeinen wrote:
> > On 26/09/13 14:51, Thierry Reding wrote:
> > > On Thu, Sep 26, 2013 at 01:03:06PM +0300, Tomi Valkeinen wrote:
> > > [...]
> > >
> > >> But if you and Thierry thi
On Sun, Sep 29, 2013 at 7:22 AM, Pádraig Brady wrote:
> On 09/25/2013 03:37 PM, richard -rw- weinberger wrote:
>> On Wed, Sep 25, 2013 at 4:28 PM, Thomas Meyer wrote:
>>> Am Mittwoch, den 25.09.2013, 08:59 -0500 schrieb Rob Landley:
On 09/24/2013 01:36:56 PM, Thomas Meyer wrote:
> Hi,
>>
Attached patch fixes the issue. Both methods function as they did
before. Thanks for the superfast fix!
2013/9/29 Rafael J. Wysocki :
> On Saturday, September 28, 2013 08:18:18 PM Ronald wrote:
>> [ resend, forgot to disable HTML (sorry!) ]
>>
>> Dear kernel developers,
>>
>> Commit 8fd37a4c9 (PM
If reread partitions of disk, the paths are:
blkdev_ioctl->blkdev_reread_part->rescan_partitions->drop_partitions
->invalidate_partition->__invalidate_device
In func __invalidate_device, if disk already mounted, it will do
shrink_dcache_sb and invalidate_inodes.
This operation will effect the fs.
S
>majianpeng writes:
>
>>>majianpeng writes:
>>>
For async-write on block device,if device removed,but the vfs don't know
it.
It will continue to do.
Patch1 set size of inode of block device to zero when removed disk.By
this,vfs know
disk changed.
Path2 add si
Hi,
This series removes the redundant driver field from the i2c_client struct. The
field is redundant since the same pointer can be accessed through
to_i2c_driver(client->dev.driver). The commit log suggests that the field has
been around since forever (since before v2.6.12-rc2) and it looks as if
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. Use 'to_i2c_driver(client->dev.driver)' instead to get direct
access to the i2c_driver struct.
Signed-off-by: Lars-Peter Clausen
---
sound/ppc/keywest.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the later.
Signed-off-by: Lars-Peter Clausen
Cc: Kyungmin
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. Use 'to_i2c_driver(client->dev.driver)' instead to get direct access to
the i2c_driver struct.
Signed-off-by: Lars-Peter Clausen
Cc: Martin Peres
---
drivers/gpu/drm/nouveau/core/subdev/therm/ic.c | 3 ++-
1 fi
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the later. To get direct access to the i2c_driver struct us
The 'driver' field of the i2c_client struct is redundant. The same data can be
accessed through to_i2c_driver(client->dev.driver). The generated code for both
approaches in more or less the same.
E.g. on ARM the expression client->driver->command(...) generates
...
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. Check i2c_client->dev.driver instead to see if a driver is bound to the
device.
Signed-off-by: Lars-Peter Clausen
---
sound/soc/fsl/imx-wm8962.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the later.
Signed-off-by: Lars-Peter Clausen
---
drivers
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the later.
Signed-off-by: Lars-Peter Clausen
Cc: Kyungmin
On Sat, Sep 28, 2013 at 04:13:29PM -0700, H. Peter Anvin wrote:
> For negative numbers presumably we need to d++ for the minus sign, no?
That's easy - the function is called num_digits, so we count only digits.
The real question is, is there a use case where we would need to count
the sign too or
On 09/26/2013 12:30 PM, Jason Wang wrote:
> On 09/23/2013 03:16 PM, Michael S. Tsirkin wrote:
>> > On Thu, Sep 05, 2013 at 10:54:44AM +0800, Jason Wang wrote:
>> > On 09/04/2013 07:59 PM, Michael S. Tsirkin wrote:
>> >>> > > On Mon, Sep 02, 2013 at 04:40:59PM +0800, Jason Wang wrote:
>
Current pread/pwrite functions simply checks whether offset is
negative. Thus we couldn't use these functions for the large
(negative) offsets although some files did allow that.
Checking it correctly requires a file pointer and we already did
the check in rw_verify_area() so just remove the chec
The file->f_op check in do_readv_writev() is redundant since all of
its caller (vfs_readv and vfs_writev) already did the check. The
same goes to compat_do_readv_writev().
Signed-off-by: Namhyung Kim
---
fs/read_write.c |9 -
1 file changed, 9 deletions(-)
diff --git a/fs/read_writ
On Fri, Sep 27, 2013 at 6:03 PM, Hannes Frederic Sowa
wrote:
> On Fri, Sep 27, 2013 at 05:36:45PM +0100, Oussama Ghorbel wrote:
>> Please see my comments below
>>
>> Regards,
>> Oussama
>>
>> On Fri, Sep 27, 2013 at 11:58 AM, Hannes Frederic Sowa
>> wrote:
>> > On Fri, Sep 27, 2013 at 11:45:48AM
On Fri, Sep 20, 2013 at 06:46:59AM -0700, tip-bot for Vladimir Davydov wrote:
> Commit-ID: 7e3115ef5149fc502e3a2e80719dba54a8e7409d
> Gitweb: http://git.kernel.org/tip/7e3115ef5149fc502e3a2e80719dba54a8e7409d
> Author: Vladimir Davydov
> AuthorDate: Sat, 14 Sep 2013 19:39:46 +0400
> Commi
Hi Alexandre,
On 9/28/2013 00:52, Alexandre Belloni wrote:
[snip]
+static int atmel_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
+{
+ struct atmel_pwm_chip *atmel_pwm = to_atmel_pwm_chip(chip);
+ int ret;
+
+ ret = clk_enable(atmel_pwm->clk);
+ if (ret) {
+
Hi,
I have got a client request to support on their board 2 instances of
linux(Ubuntu) running as an AMP.
The board has 2 ARM cores and a GPU. The LED monitor which connects to
the board is using HDMI.
Two cores can communicate via a IPI handshake.
So release and acquire of the GPU can be done co
Hi Alexandre,
On 9/28/2013 04:10, Alexandre Belloni wrote:
I found that disabling a pwm while it is at a low level will actually put it
back at a high level. The main symptom is that leds-pwm is calling pwm_disable()
after setting the duty cycle to 0. Hence, instead of getting a switched off LED
On Thu, Sep 26, 2013 at 03:43:24PM -0500, Kees Cook wrote:
> On Wed, Sep 25, 2013 at 3:14 PM, Djalal Harouni wrote:
> > The /proc/*/stack contains sensitive information and currently its mode
> > is 0444. Change this to 0400 so the VFS will be able to block
> > unprivileged processes to get file d
On 2013.09.28 at 20:03 +0200, Ingo Molnar wrote:
> Andi Kleen (1):
> perf symbols: Demangle cloned functions
The commit above e95ab53645:
commit de95ab53645a2f0015e0f68ee723f18dce2b8b51
Author: Andi Kleen
Date: Thu Sep 12 08:16:38 2013 -0700
perf symbols: Demangle cloned functio
Correct spelling typo in Kconfig.
Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
---
arch/arm/mach-sti/Kconfig| 4 ++--
drivers/cpufreq/Kconfig.x86 | 2 +-
drivers/dma/Kconfig | 2 +-
drivers/fmc/Kconfig | 2 +-
drivers/infiniband/ulp
On Sun, Sep 29, 2013 at 10:51:05AM +0200, Lars-Peter Clausen wrote:
> The 'driver' field of the i2c_client struct is redundant and is going to be
> removed. Check i2c_client->dev.driver instead to see if a driver is bound to
> the
> device.
Acked-by: Mark Brown
signature.asc
Description: Digit
On Fri, Sep 27, 2013 at 10:01:36PM +0200, Lars-Peter Clausen wrote:
> On 09/27/2013 09:22 PM, Mark Brown wrote:
> > Indeed. I don't think that's terribly well thought through though,
> > especially not now we have annotations for endianness (as you noticed!).
> I wouldn't mind updating spi_w8r16
On Thu, Sep 12, 2013 at 03:23:15PM -0600, Alex Williamson wrote:
> So far we've succeeded at making KVM and VFIO mostly unaware of each
> other, but there's any important point where that breaks down. Intel
> VT-d hardware may or may not support snoop control. When snoop
> control is available, i
From: "baker.zhang"
Because 'node' is the i'st child of 'oldnode',
thus, here 'i' equals
tkey_extract_bits(node->key, oldtnode->pos, oldtnode->bits)
we just get 1 more bit,
and need not care the detail value of this bits.
Signed-off-by: baker.zhang
---
net/ipv4/fib_trie.c | 9 +++--
1 fil
From: "baker.zhang"
Because 'node' is the i'st child of 'oldnode',
thus, here 'i' equals
tkey_extract_bits(node->key, oldtnode->pos, oldtnode->bits)
we just get 1 more bit,
and need not care the detail value of this bits.
Signed-off-by: baker.zhang
---
net/ipv4/fib_trie.c | 9 +++--
1 fil
On Sun, 2013-09-29 at 16:16 +0300, Gleb Natapov wrote:
> On Thu, Sep 12, 2013 at 03:23:15PM -0600, Alex Williamson wrote:
> > So far we've succeeded at making KVM and VFIO mostly unaware of each
> > other, but there's any important point where that breaks down. Intel
> > VT-d hardware may or may n
On 09/27, Oleg Nesterov wrote:
>
> I tried hard to find any hole in this version but failed, I believe it
> is correct.
And I still believe it is. But now I am starting to think that we
don't need cpuhp_seq. (and imo cpuhp_waitcount, but this is minor).
> We need to ensure 2 things:
>
> 1. The re
On Sat, Sep 28, 2013 at 11:55:35PM +0100, Mark Brown wrote:
> No, having the supplies bound to the parent is desired (especially given
> that there isn't a child node) - it's the fact that you're bodging this
> in the framework by just randomly peering at the parent device and
> hoping it's an MFD
Wakko Warner wrote:
> Please keep me in CC.
>
> I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> happens when I'm on a console, the screen has gone into power save and I
> press a key to wake it up.
>
> This doesn't happen when I'm in X.
>
> Kernel is Vanilla 3.11.2.
Te
* Markus Trippelsdorf wrote:
> On 2013.09.28 at 20:03 +0200, Ingo Molnar wrote:
> > Andi Kleen (1):
> > perf symbols: Demangle cloned functions
>
> The commit above e95ab53645:
>
> commit de95ab53645a2f0015e0f68ee723f18dce2b8b51
> Author: Andi Kleen
> Date: Thu Sep 12 08:16:38 2013
On Sun, Sep 29, 2013 at 07:52:28AM -0600, Alex Williamson wrote:
> On Sun, 2013-09-29 at 16:16 +0300, Gleb Natapov wrote:
> > On Thu, Sep 12, 2013 at 03:23:15PM -0600, Alex Williamson wrote:
> > > So far we've succeeded at making KVM and VFIO mostly unaware of each
> > > other, but there's any impo
Let's CC some more people.
On Sun, Sep 29, 2013 at 10:17:34AM -0400, Wakko Warner wrote:
> Wakko Warner wrote:
> > Please keep me in CC.
> >
> > I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> > happens when I'm on a console, the screen has gone into power save and I
> >
On Sun, Sep 29, 2013 at 10:17:34AM -0400, Wakko Warner wrote:
> Wakko Warner wrote:
> > Please keep me in CC.
> >
> > I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> > happens when I'm on a console, the screen has gone into power save and I
> > press a key to wake it up.
Btw,
while I got your attention, on a not-really related topic: how do we
feel about adding support for specifying a non-contiguous set of cpus
for a numa node in qemu with the -numa option? I.e., like this, for
example:
x86_64-softmmu/qemu-system-x86_64 -smp 8 -numa node,nodeid=0,cpus=0\;2\;4-5
On Sun, Sep 29, 2013 at 04:58:39PM +0200, Borislav Petkov wrote:
> Let's CC some more people.
Please boot with drm.debug=0xe, reproduce the WARN and then attach the
full dmesg.
Thanks, Daniel
>
> On Sun, Sep 29, 2013 at 10:17:34AM -0400, Wakko Warner wrote:
> > Wakko Warner wrote:
> > > Please
From: Borislav Petkov
Turn it into (for example):
[0.073380] x86: Booting SMP configuration:
[0.074005] node #0, CPUs: #1 #2 #3 #4 #5 #6 #7
[0.603005] node #1, CPUs: #8 #9 #10 #11 #12 #13 #14 #15
[1.25] node #2, CPUs:#
On 2 September 2013 18:23, Valentin Ilie wrote:
> Convert a compound if-else blob to a switch statement.
>
> Signed-off-by: Valentin Ilie
> ---
> arch/arm/mach-iop32x/iq31244.c | 29 +++--
> 1 file changed, 11 insertions(+), 18 deletions(-)
>
> diff --git a/arch/arm/mach-
James,
could you pull and forward the follow fixes for the 3.12 kernel. Both
issues have had multiple reports.
thanks
---
The following changes since commit eb8948a03704f3dbbfc7e83090e20e93c6c476d2:
X.509: remove possible code fragility: enumeration values not handled
(2013-09-25 17:17:01
The recent 3.12 pull request for apparmor was missing a couple rcu _protected
access modifiers. Resulting in the follow suspicious RCU usage
[ 29.804534] [ INFO: suspicious RCU usage. ]
[ 29.804539] 3.11.0+ #5 Not tainted
[ 29.804541] ---
[ 29.804545] securi
From: Tyler Hicks
Use the shash interface, rather than the hash interface, when hashing
AppArmor profiles. The shash interface does not use scatterlists and it
is a better fit for what AppArmor needs.
This fixes a kernel paging BUG when aa_calc_profile_hash() is passed a
buffer from vmalloc(). T
If the goal is to feed this to the field width in printf, which I would think
would be the dominant use, then you do have to account for the minus sign.
Borislav Petkov wrote:
>On Sat, Sep 28, 2013 at 04:13:29PM -0700, H. Peter Anvin wrote:
>> For negative numbers presumably we need to d++ for t
On Sun, Sep 29, 2013 at 10:40:11AM +0100, Oussama Ghorbel wrote:
> On Fri, Sep 27, 2013 at 6:03 PM, Hannes Frederic Sowa
> wrote:
> > Ok, let's go with one function per protocol type. Seems easier.
> >
> > It seems to get more hairy, because it depends on the tunnel driver if the
> > prepended ip
On 29/09/2013 12:12, Bo Shen wrote:
> Hi Alexandre,
>
> On 9/28/2013 04:10, Alexandre Belloni wrote:
>> I found that disabling a pwm while it is at a low level will actually
>> put it
>> back at a high level. The main symptom is that leds-pwm is calling
>> pwm_disable()
>> after setting the duty cy
On Sun, 2013-09-29 at 17:44 +0300, Gleb Natapov wrote:
> On Sun, Sep 29, 2013 at 07:52:28AM -0600, Alex Williamson wrote:
> > On Sun, 2013-09-29 at 16:16 +0300, Gleb Natapov wrote:
> > > On Thu, Sep 12, 2013 at 03:23:15PM -0600, Alex Williamson wrote:
> > > > So far we've succeeded at making KVM an
On 29/09/2013 12:02, Bo Shen wrote:
> Hi Alexandre,
> [snip]
> Thank for point out this.
>
> I see you have sent out a patch to fix it (however the other contents
> of your patch doesn't work). So, do you prefer I send out v5 patch to
> fix this? or you fix your patch at same time fix this issue?
On Saturday 28 of September 2013 23:00:27 Alan Stern wrote:
> On Sat, 28 Sep 2013, Tomasz Figa wrote:
> > A series of commit starting at
> >
> > 50a97e059b USB: OHCI: make ohci-exynos a separate driver
> >
> > and ending at
> >
> > b8ad5c3706 USB: OHCI: make ohci-pxa27x a separate driver
> >
>
According to board schematics, for HSMMC1 a GPIO line is used to detect
card presence, while currently it is being configured for internal card
detect line, which is multiplexed with card detect line of HSMMC0 and
thus breaking it.
This patch adds proper sdhci platform data setting card detect typ
On Sun, Sep 29, 2013 at 4:45 PM, Hannes Frederic Sowa
wrote:
> On Sun, Sep 29, 2013 at 10:40:11AM +0100, Oussama Ghorbel wrote:
>> On Fri, Sep 27, 2013 at 6:03 PM, Hannes Frederic Sowa
>> wrote:
>> > Ok, let's go with one function per protocol type. Seems easier.
>> >
>> > It seems to get more ha
Please keep me in CC.
CCing Borislav Petkov , intel-...@lists.freedesktop.org,
dri-de...@lists.freedesktop.org as they were on another part of this thread.
Chris Wilson wrote:
> > > I receive a warning in drivers/gpu/drm/i915/intel_display.c:3869. This
> > > happens when I'm on a console, the s
On 09/29/2013 08:14 AM, Richard Weinberger wrote:
> On Sun, Sep 29, 2013 at 7:22 AM, Pádraig Brady wrote:
>> On 09/25/2013 03:37 PM, richard -rw- weinberger wrote:
>>> On Wed, Sep 25, 2013 at 4:28 PM, Thomas Meyer wrote:
Am Mittwoch, den 25.09.2013, 08:59 -0500 schrieb Rob Landley:
> On
On Sat, Sep 28, 2013 at 11:06 PM, Al Viro wrote:
>
> Sigh... Looks like there's a lot of fun in shrink_dcache_for_umount() -
> at the very least, it needs to bump ->d_seq on everything, because with
> that change we *can* walk into a filesystem in the middle of that.
> We obviously don't want to
On Sun, Sep 29, 2013 at 10:50:58AM +0200, Lars-Peter Clausen wrote:
> This series removes the redundant driver field from the i2c_client struct. The
> field is redundant since the same pointer can be accessed through
> to_i2c_driver(client->dev.driver). The commit log suggests that the field has
>
On 09/29/2013 10:50 AM, Lars-Peter Clausen wrote:
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the lat
On 09/29/2013 10:51 AM, Lars-Peter Clausen wrote:
The 'driver' field of the i2c_client struct is redundant and is going to be
removed. The results of the expressions 'client->driver.driver->field' and
'client->dev.driver->field' are identical, so replace all occurrences of the
former with the lat
On Sun, Sep 29, 2013 at 03:11:37PM +0100, Charles Keepax wrote:
> There is currently only one other MFD driver (tps65910) which defines
> the GPIOs on the main MFD node as we do in the Arizona driver and it
> uses the 'hack' that I suggested in my first email of copying the
> of_node.
> tps65910_
From: Austin S. Hemmelgarn
This patch adds Kconfig options to allow optimization for AMD family
10h, AMD Bulldozer, and AMD Piledriver derived CPU's in version
3.12-rc2. These provide noticeable improvements over the K8 config
option, and allow the kernel to take full advantage of AMD specific
i
On Sun, Sep 29, 2013 at 01:54:00PM -0400, Austin S Hemmelgarn wrote:
> From: Austin S. Hemmelgarn
>
> This patch adds Kconfig options to allow optimization for AMD family
> 10h, AMD Bulldozer, and AMD Piledriver derived CPU's in version
> 3.12-rc2. These provide noticeable improvements over the
On Sun, Sep 29, 2013 at 06:52:36PM +0100, Mark Brown wrote:
> On Sun, Sep 29, 2013 at 03:11:37PM +0100, Charles Keepax wrote:
>
> > There is currently only one other MFD driver (tps65910) which defines
> > the GPIOs on the main MFD node as we do in the Arizona driver and it
> > uses the 'hack' tha
Hello everyone,
I would like to write a driver to support the "Security System" hardware
block on some Allwinner ARM SoCs. The hardware supports AES, DES, 3DES,
SHA-1, MD5 and has a PRNG. Data passing is done via two FIFOs. You can
find some ugly userspace code to calculate a SHA1 hash here, s
On Sun, Sep 29, 2013 at 10:19:59AM -0700, Linus Torvalds wrote:
> I have to say, that when I was working with the dcache lockref code, I
> absolutely _detested_ the magical shrink_dcache_for_umount() code that
> violated all the locking rules.
... and duplicated random-half-of-an-arseload of stuff
Hi,
Am Thu, 26 Sep 2013 16:54:47 +0200
schrieb Ulf Hansson :
> Suspend and resume of cards are being handled from the protocol layer
> and consequently the mmc_suspend|resume_host APIs are deprecated.
>
> This means we can simplify the suspend|resume callbacks by removing
> the use of the deprec
On Sun, Sep 29, 2013 at 11:10 AM, Al Viro wrote:
>
> FWIW, right now I'm reviewing the subset of fs code that can be hit in
> RCU mode. Not a pretty sight, that... ;-/ First catch: in
> fuse_dentry_revalidate() we have a case (reachable with LOOKUP_RCU) where
> we do this:
> } else if (i
On Sun, Sep 29, 2013 at 01:34:08AM -0300, Emilio López wrote:
> >>Also, would any special considerations be needed when adjusting the
> >>ahb clock? A future cpufreq driver will most likely need to.
> >
> >While this will be needed at some point, I don't really see how to
> >handle that properly. T
Hello.
Paul, Peter, et al, could you review the code below?
I am not sending the patch, I think it is simpler to read the code
inline (just in case, I didn't try to compile it yet).
It is functionally equivalent to
struct xxx_struct {
atomic_t counter;
};
On Sun, Sep 29, 2013 at 07:10:47PM +0100, Al Viro wrote:
> FWIW, right now I'm reviewing the subset of fs code that can be hit in
> RCU mode. Not a pretty sight, that... ;-/ First catch: in
> fuse_dentry_revalidate() we have a case (reachable with LOOKUP_RCU) where
> we do this:
> } else
On Sun, Sep 29, 2013 at 07:10:47PM +0100, Al Viro wrote:
> FWIW, right now I'm reviewing the subset of fs code that can be hit in
> RCU mode. Not a pretty sight, that... ;-/ First catch: in
[snip]
and another, this one completely unrelated to RCU:
unsigned long gen = (unsigned l
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 6e956da2027c767859128b9bfef085cf2a8e233b upstream.
We should not do temperature compensation on devices without
EXTERNAL_TX_ALC bit set (called DynamicTxAgcControl on v
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 331415ff16a12147d57d5c953f3a961b7ede348b upstream.
Many drivers need to validate the characteristics of their HID report
during initialization to avoid misusing the reports. Th
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 78214e81a1bf43740ce89bb5efda78eac2f8ef83 upstream.
The zeroplus HID driver was not checking the size of allocated values
in fields it used. A HID device could send a malicious
This is the start of the stable review cycle for the 3.0.98 release.
There are 17 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.
Responses should be made by Tue Oct 1 19:07:47 UTC 2013.
Anything receive
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit cc6b54aa54bf40b762cab45a9fc8aa81653146eb upstream.
When dealing with usage_index, be sure to properly use unsigned instead of
int to avoid overflows.
When working on
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 4543eda52113d1e2cc0e9bf416f79597e6ef1ec7 upstream.
Need to swap the data fetched over i2c properly. This
is the same fix as the endian fix for aux channel
transactions.
Si
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 91f3a6aaf280294b07c05dfe606e6c27b7ba3c72 upstream.
The OUTPUT_ENABLE action jumps past the point in the coder where
the data_offset is set on certain rs780 cards. This work
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit 8ac1c8d5deba65513b6a82c35e89e73996c8e0d6 upstream.
After commit 829199197a43 ("kernel/audit.c: avoid negative sleep
durations") audit emitters will block forever i
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit c2f5b7507ac5d808f29287d77ee6148358d7fbfe which is
commit f6e80abeab928b7c47cc1fbf53df13b4398a2bec.
Michal writes:
Mainline commit f6e80abe was int
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 0b31e02363b0db4e7931561bc6c141436e729d9f upstream.
We need to allocate line buffer to each display when
setting up the watermarks. Failure to do so can lead
to a blank scr
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Li Zefan
commit f169007b2773f285e098cb84c74aac0154d65ff7 upstream.
If we pass fd of memory.usage_in_bytes of cgroup A to cgroup.event_control
of cgroup B, then we won't get memory usage notific
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: John Stultz
commit 7bd36014460f793c19e7d6c94dab67b0afcfcb7f upstream.
Gerlando Falauto reported that when HRTICK is enabled, it is
possible to trigger system deadlocks. These were hard to
repr
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit fb93df1c2d8b3b1fb16d6ee9e32554e0c038815d upstream.
The table has the following format:
typedef struct _ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT //usSrcDstTableOffset
poi
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 0a9cd0a80ac559357c6a90d26c55270ed752aa26 upstream.
A HID device could send a malicious output report that would cause the
lenovo-tpkbd HID driver to write just beyond the outp
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Christian König
commit 4f66c59922cbcda14c9e103e6c7f4ee616360d43 upstream.
Putting everything into VRAM seems to help.
Signed-off-by: Christian König
Signed-off-by: Alex Deucher
Signed-off-b
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 9a71677874d200865433647e9282fcf9fa6b05dd upstream.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
include/drm/drm_pciids.h |3 +++
1 file changed
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Emil Velikov
commit 5087f51da805f53cba7366f70d596e7bde2a5486 upstream.
Commit ea9197cc323839ef3d5280c0453b2c622caa6bc7 effectively enabled the
use of an improved DAC detection code, but introd
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit b2e4c70a9747ecb618d563b004ba746869dde5aa upstream.
This fills in the GPU specific details for berlin
GPU cores so that the driver will work with them.
Signed-off-by: Alex
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Skeggs
commit 182b17c8dc4e83aab000ce86587b6810e515da87 upstream.
After a vmalloc failure in ttm_dma_tt_alloc_page_directory(),
ttm_dma_tt_init() will call ttm_tt_destroy() to cleanup, and
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 7c4622d5415038a74964480844de885e7253a0f4 upstream.
Sets the right paramters for the new pci id.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
drive
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit e5903d399a7b0e5c14673c1206f4aeec2859c730 upstream.
The vram scratch buffer needs to be initialized
before the mc is programmed otherwise we program
0 as the GPU address of
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Anatol Pomozov
commit f3cff25f05f2ac29b2ee355e611b0657482f6f1d upstream.
'samples' is 64bit operant, but do_div() second parameter is 32.
do_div silently truncates high 32 bits and calculated
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 0b31e02363b0db4e7931561bc6c141436e729d9f upstream.
We need to allocate line buffer to each display when
setting up the watermarks. Failure to do so can lead
to a blank scr
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
commit adbe6991efd36104ac9eaf751993d35eaa7f493a upstream.
This fixes a copy and paste error introduced by 9f060e2231
("block: Convert integrity to bvec_alloc_bs()").
Found by Co
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 4543eda52113d1e2cc0e9bf416f79597e6ef1ec7 upstream.
Need to swap the data fetched over i2c properly. This
is the same fix as the endian fix for aux channel
transactions.
S
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit bc01a8c7a24169f8b111b7dda6f5d8e7088309af upstream.
We need to allocate line buffer to each display when
setting up the watermarks. Failure to do so can lead
to a blank scr
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit c194992cbe71c20bb3623a566af8d11b0bfaa721 upstream.
The patch 136d8f377e1575463b47840bc5f1b22d94bf8f63 broke the skge driver.
Note this part of the patch:
+
3.11-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 0431b2742f8e7755f3bbf5924900d12973412e94 upstream.
This adds the pci ids for the berlin GPU core.
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
---
inc
1 - 100 of 343 matches
Mail list logo
