On Saturday 24 August 2013, Frantisek Hrbata wrote:
> If I understand it correctly, this would mean that you will be able to use
> only
> one implementation of gcov format at the time. Meaning you will be able to get
> coverage data for module, but not for kernel if it was compiled with different
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.11-rc7
for you to fetch changes up to
The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:
Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-3.11-rc7
for you to fetch changes up to
On 08/25, Oleg Nesterov wrote:
>
> > I find it hard to believe that anything actually relies on open(2)
> > succeeding, given that it returns an fd with the wrong f_ops.
>
> OK, let me send the patch then. I won't argue if it is ignored or
> nacked.
Damn. Sorry for noise, I removed lkml by
open("/proc/pid/$anon-fd") should fail, we can't create the new
file with correct f_op/etc correctly. Currently this creates the
bogus file with the empty anon_inode_fops, this is harmless but
still wrong and misleading.
Add anon_inode_fops->anon_open() which simply returns ENXIO like
On 08/23/13 17:02, Naveen Krishna Chatradhi wrote:
Add ADC device tree node for exynos5420 and exynos5250
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Doug Anderson
---
Added recipients accordingly,
./scripts/get_maintainer.pl -f of the modified files
On Sun, Aug 25, 2013 at 11:19:37PM +0800, Lai Jiangshan wrote:
> Hi, Steven
>
> Any comments about this patch?
For whatever it is worth, it ran without incident for two hours worth
of rcutorture on my P5 test (boosting but no CPU hotplug).
Lai, do you have a specific test for this patch? Your
Since v3.7 the acpi backlight driver doesn't work correctly in several
machines because ACPI code has different code for Windows 8, and the
rest.
The commit ea45ea7 (in v3.11-rc2) tried to fix this problem by using the
intel backlight driver, however it introduced several other issues in
On Sunday 25 August 2013 16:51:06 Deucher, Alexander wrote:
> > -Original Message-
> > From: Ondrej Zary [mailto:li...@rainbow-software.org]
> > Sent: Friday, August 23, 2013 1:55 PM
> > To: Deucher, Alexander
> > Cc: Kernel development list
> > Subject: Re: Asus F5RL laptop unable to
On Sun, Aug 25, 2013 at 7:23 AM, Al Viro wrote:
> On Sun, Aug 25, 2013 at 12:26:34AM -0700, Andy Lutomirski wrote:
>
>> I think this is more screwed up than just flink and open. For example:
>>
>> $ echo 'WTF' >test
>> $ truncate -s 1 /proc/self/fd/3 3> $ cat test
>> W$
>>
>> IMO that should
On Thu 2013-08-22 19:01:56, Lee, Chun-Yi wrote:
> This patch introduced SNAPSHOT_SIG_HASH config for user to select which
> hash algorithm will be used during signature generation of snapshot.
>
> v2:
> Add define check of oCONFIG_SNAPSHOT_VERIFICATION in snapshot.c before
> declare pkey_hash().
On Thu 2013-08-22 19:01:54, Lee, Chun-Yi wrote:
> In current solution, the snapshot signature check used the RSA key-pair
> that are generated by bootloader(e.g. shim) and pass the key-pair to
> kernel through EFI variables. I choice to binding the snapshot
> signature check mechanism with UEFI
On Thu 2013-08-22 19:01:52, Lee, Chun-Yi wrote:
> This patch add swsusp_page_is_sign_key() method to hibernate_key.c and
> check the page is S4 sign key data when collect saveable page in
> snapshot.c to avoid sign key data included in snapshot image.
>
> Reviewed-by: Jiri Kosina
>
On Thu 2013-08-22 19:01:51, Lee, Chun-Yi wrote:
> This patch add the code for generate/verify signature of snapshot, it
> put the signature to snapshot header. This approach can support both
> on userspace hibernate and in-kernel hibernate.
>
> v2:
> - Due to loaded S4 sign key before
On Sun, Aug 25, 2013 at 06:22:43PM +0200, Pavel Machek wrote:
> On Thu 2013-08-22 19:01:49, Lee, Chun-Yi wrote:
> > From: Matthew Garrett
> >
> > The firmware has a set of flags that indicate whether secure boot is enabled
> > and enforcing. Use them to indicate whether the kernel should lock
On Thu 2013-08-22 19:01:50, Lee, Chun-Yi wrote:
> Introduced a hibernate_key.c file to query the key pair from EFI variables
> and maintain key pair for check signature of S4 snapshot image. We
> loaded the private key when snapshot image stored success.
>
> This patch introduced 2 EFI variables
On Thu 2013-08-22 19:01:49, Lee, Chun-Yi wrote:
> From: Matthew Garrett
>
> The firmware has a set of flags that indicate whether secure boot is enabled
> and enforcing. Use them to indicate whether the kernel should lock itself
> down. We also indicate the machine is in secure boot mode by
You may want to check subject. If it does something, it is not dummy.
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2784,6 +2784,13 @@ bytes respectively. Such letter suffixes can also be
> entirely omitted.
> Note: increases
On Thu 2013-08-22 19:01:47, Lee, Chun-Yi wrote:
> From: Matthew Garrett
>
> Secure boot adds certain policy requirements, including that root must not
> be able to do anything that could cause the kernel to execute arbitrary code.
> The simplest way to handle this would seem to be to add a new
On Thu 2013-08-22 19:01:46, Lee, Chun-Yi wrote:
> Per PKCS1 spec, the EMSA-PKCS1-v1_5 encoded message is leading by 0x00 0x01 in
> its first 2 bytes. The leading zero byte is suppressed by MPI so we pass a
> pointer to the _preceding_ byte to RSA_verify() in original code, but it has
> risk for
On Thu 2013-08-22 19:01:45, Lee, Chun-Yi wrote:
> Add ASN.1 files and parser to support parsing PKCS #8 noncompressed private
> key information. It's better than direct parsing pure private key because
> PKCS #8 has a privateKeyAlgorithm to indicate the algorithm of private
> key, e.g. RSA from
On Thu 2013-08-22 19:01:42, Lee, Chun-Yi wrote:
> Due to RSA_I2OSP is not only used by signature verification path but also used
> in signature generation path. So, separate the length checking of octet string
> because it's not for generate 0x00 0x01 leading string when used in signature
>
Add a resource managed regulator_get_exclusive()
Signed-off-by: Matthias Kaehlcke
---
drivers/regulator/core.c | 30 ++
include/linux/regulator/consumer.h |2 ++
2 files changed, 32 insertions(+)
diff --git a/drivers/regulator/core.c
On Thu 2013-08-22 19:01:41, Lee, Chun-Yi wrote:
> Implement EMSA_PKCS1-v1_5-ENCODE [RFC3447 sec 9.2] in rsa.c. It's the
> first step of signature generation operation
> (RSASSA-PKCS1-v1_5-SIGN).
Is this your own code, or did you copy it from somewhere?
> + if (!T)
> + goto
Hi Willy,
On 08/24, Willy Tarreau wrote:
>
> On Sat, Aug 24, 2013 at 08:29:39PM +0200, Oleg Nesterov wrote:
> >
> > On 08/22, Willy Tarreau wrote:
> > >
> > > It's not only that, it also supports sockets and pipes that you can access
> > > via /proc/pid/fd and not via a real symlink which would
Booting current git kernel dmesg shows a set of new warnings:
"wm8775 9-001b: I2C: cannot write ??? to register R??"
Nevertheless, the hardware seems to work fine.
This is a new problem, introduced after kernel 3.10.
If necessary I can bisect.
dmesg snippet:
[ 11.841431] Linux video
Hi!
> Use the name_to_dev_t call to parse the device name echo'd to
> to /sys/power/resume. This imitates the method used in hibernate.c
> in software_resume, and allows the resume partition to be specified
> using other equivalent device formats as well. By allowing
> /sys/debug/resume to
Sent from my iPhone
On 23 Aug 2013, at 18:25, Sylwester Nawrocki wrote:
> On 08/13/2013 03:00 AM, Kumar Gala wrote:
>> On Aug 11, 2013, at 1:25 AM, Lad, Prabhakar wrote:
>>
>>> From: "Lad, Prabhakar"
>>>
>>> add OF support for the tvp7002 driver.
>>>
>>> Signed-off-by: Lad, Prabhakar
>>>
On 24.08.2013, at 21:14, Yann Droneaud wrote:
> KVM uses anon_inode_get() to allocate file descriptors as part
> of some of its ioctls. But those ioctls are lacking a flag argument
> allowing userspace to choose options for the newly opened file descriptor.
>
> In such case it's advised to use
> -Original Message-
> From: Ondrej Zary [mailto:li...@rainbow-software.org]
> Sent: Friday, August 23, 2013 1:55 PM
> To: Deucher, Alexander
> Cc: Kernel development list
> Subject: Re: Asus F5RL laptop unable to resume from S3 because of radeon
> module
>
> On Friday 23 August 2013
On Sun, Aug 25, 2013 at 12:26:34AM -0700, Andy Lutomirski wrote:
> I think this is more screwed up than just flink and open. For example:
>
> $ echo 'WTF' >test
> $ truncate -s 1 /proc/self/fd/3 3 $ cat test
> W$
>
> IMO that should have failed.
Why? truncate() always follows links, so
On 08/22/2013 04:49:31 PM, Zoltan Kiss wrote:
The sample missed the moving of the header files into the events
subdirectory.
I've also extended it based on the existing headers, and mentioned
the tiny
but important role of CREATE_TRACE_POINTS.
Signed-off-by: Zoltan Kiss
---
On Wed, Aug 07, 2013 at 12:40:36AM +0530, Raghavendra K T wrote:
> On 08/07/2013 12:02 AM, Eric Northup wrote:
> >
> >If this is about migration correctness, could it get folded into the
> >previous patch 2/5, so that there's not a broken commit which could
> >hurt bisection?
>
> Yes. It could
Vážení E-mail užívateľa;
Prekročili ste 23432 boxy nastaviť svoje
Webová služba / Administrátor, a budete mať problémy pri odosielaní a
prijímať e-maily, kým znova overiť. Musíte aktualizovať kliknutím na
odkaz nižšie a vyplňte údaje pre overenie vášho účtu
Prosím, kliknite na odkaz nižšie
2013/8/23 Seth Jennings :
> On Fri, Aug 23, 2013 at 07:03:37PM +0800, Weijie Yang wrote:
>> zswap_tree is not freed when swapoff, and it got re-kzalloc in swapon,
>> memory leak occurs.
>> Add check statement in zswap_frontswap_init so that zswap_tree is
>> inited only once.
>>
>> ---
>>
On Wed, Aug 21, 2013 at 02:27:05PM +0300, Andy Shevchenko wrote:
> ACPI DMA provides managed function to register the slave DMA controller in the
> internal container. This patch anounces that function in the corresponding
> documentation file.
Applied, thanks
~Vinod
--
To unsubscribe from this
On Fri, Aug 23, 2013 at 04:55:49PM +0800, Jason Wang wrote:
> On 08/20/2013 10:48 AM, Jason Wang wrote:
> > On 08/16/2013 06:02 PM, Michael S. Tsirkin wrote:
> >> > On Fri, Aug 16, 2013 at 01:16:30PM +0800, Jason Wang wrote:
> >>> >> We used to limit the max pending DMAs to prevent guest from
On Fri, Aug 23, 2013 at 04:50:38PM +0800, Jason Wang wrote:
> On 08/20/2013 10:33 AM, Jason Wang wrote:
> > On 08/16/2013 05:54 PM, Michael S. Tsirkin wrote:
> >> On Fri, Aug 16, 2013 at 01:16:26PM +0800, Jason Wang wrote:
> Switch to use vhost_add_used_and_signal_n() to avoid multiple calls
On Wed, Aug 21, 2013 at 09:34:02PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam
>
> When CONFIG_ARM_LPAE=y the following build warning are generated:
>
> drivers/dma/ste_dma40.c:3228:2: warning: format '%x' expects argument of type
> 'unsigned int', but argument 4 has type
On Thu, Aug 22, 2013 at 02:03:24PM -0700, Guenter Roeck wrote:
> Fix:
>
> arch/arm/common/built-in.o: undefined reference to `edma_filter_fn'
>
> seen with "make ARCH=arm allmodconfig"
>
> Commit 6cba4355 (ARM: edma: Add DT and runtime PM support to the private EDMA
> API) adds a dependency on
Avoid processing garbage data by NULL terminating the strings.
Signed-off-by: Djalal Harouni
---
Patch compile tested only.
drivers/net/wireless/ath/ath5k/debug.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git
In interrupt context, after reading and comparing the UTRLDBR to
hba->outstanding_request and before resetting the interrupt aggregation,
there might be completion of another transfer request (TR). Such TRs might
get stuck, pending, until the next interrupt is generated.
The fix reads the UTRLDBR
Am Freitag 23 August 2013, 21:10:00 schrieb Linus Walleij:
> On Thu, Aug 22, 2013 at 11:56 AM, Lars Poeschel
wrote:
> > From: Lars Poeschel
> >
> > The device tree property should be more descriptive.
> > microchip seems more reasonable than mcp. As there are no
> > in tree users of this
Tested-by: David Oberhollenzer
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, Aug 21, 2013 at 06:52:54PM +0900, Jingoo Han wrote:
> The driver core clears the driver data to NULL after device_release
> or on probe failure. Thus, it is not needed to manually clear the
> device driver data to NULL.
Applied, thanks
~Vinod
--
To unsubscribe from this list: send the
Tomas Winkler (4):
mei: me: fix reset state machine
mei: don't have to clean the state on power up
mei: me: fix waiting for hw ready
mei: me: fix hardware reset flow
drivers/misc/mei/hw-me.c | 22 +-
drivers/misc/mei/init.c | 3 ++-
2 files changed, 15
stable: 3.10
commit ff96066e3171acdea356b331163495957cb833d0 char-misc
Both H_IS and H_IE needs to be set to receive H_RDY
interrupt
1. Assert H_IS to clear the interrupts during hw reset
and use mei_me_reg_write instead of mei_hcsr_set as the later
strips down the H_IS
2. fix interrupt
stable: 3.10
commit 315a383ad7dbd484fafb93ef08038e3dbafbb7a8 upstream
ME HW ready bit is down after hw reset was asserted or on error.
Only on error we need to enter the reset flow, additional reset
need to be prevented when reset was triggered during
initialization , power up/down or a reset
stable: 3.10
commit 99f22c4ef24cf87b0dae6aabe6b5e620b62961d9 upstream
When powering up, we don't have to clean up the device state
nothing is connected.
Cc: sta...@vger.kernel.org
Tested-by: Shuah Khan
Signed-off-by: Tomas Winkler
Signed-off-by: Greg Kroah-Hartman
---
drivers/misc/mei/init.c
stable: 3.10
commit dab9bf41b23fe700c4a74133e41eb6a21706031e upstream
1. MEI_INTEROP_TIMEOUT is in seconds not in jiffies
so we use mei_secs_to_jiffies macro
While cold boot is fast this is relevant in resume
2. wait_event_interruptible_timeout can return with
-ERESTARTSYS so do not override it
On Wed, Aug 21, 2013 at 06:51:56PM +0900, Jingoo Han wrote:
> The driver core clears the driver data to NULL after device_release
> or on probe failure. Thus, it is not needed to manually clear the
> device driver data to NULL.
Can you pls rebase this as resend. I have applied bunch of sh-dma
On Sat, Aug 24, 2013 at 09:09:39PM -0700, Greg Kroah-Hartman wrote:
> Same as before, are you unloading and loading modules? We have a fix
> for modules that cause problems when unloading with the config option
> above enabled. But that shouldn't be this issue.
What seems to be is going on here
Correct spelling typo in various Kconfig files.
Signed-off-by: Masanari Iida
---
arch/arm/mach-sti/Kconfig| 4 ++--
drivers/cpufreq/Kconfig.x86 | 2 +-
drivers/dma/Kconfig | 2 +-
drivers/fmc/Kconfig | 2 +-
On Fri, Aug 02, 2013 at 04:50:35PM +0200, Guennadi Liakhovetski wrote:
> In this version of shdma Device Tree support I preserved the DT
> configuration approach via OF device ID tables from v4, but now it is only
> used for the DT-mode, the C-version is left untouched. In this series I
> only
On Fri, Aug 02, 2013 at 04:18:09PM +0200, Guennadi Liakhovetski wrote:
> Platform data shouldn't be changed at run-time, so, pointers to it should
> be const.
Applied, thanks
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Jul 02, 2013 at 05:45:49PM +0200, Guennadi Liakhovetski wrote:
> Hi
>
> The first two patches in this small series improve driver internals a bit
> by using preferred APIs, the 3rd patch adds support for new DMAC versions,
> present on AG5, APE6, H2.
Applied, thanks
Although the patch
On Tue, Jul 02, 2013 at 05:37:58PM +0200, Guennadi Liakhovetski wrote:
> struct sh_dmae_device::chan_reg is a pointer to u32, therefore when adding
> offsets to it care should be taken to add offsets in sizeof(u32) units, not
> in bytes. This patch corrects such a bug. While at it we also remove
On 08/25/2013 02:26 AM, Laurent Pinchart wrote:
Add DT bindings for the pcf857x-compatible chips and parse the device
tree node in the driver.
Signed-off-by: Laurent Pinchart
---
.../devicetree/bindings/gpio/gpio-pcf857x.txt | 71 ++
drivers/gpio/gpio-pcf857x.c
On 08/25/2013 02:15 AM, Laurent Pinchart wrote:
On Saturday 24 August 2013 16:13:11 Tomasz Figa wrote:
On Saturday 24 of August 2013 02:54:07 Laurent Pinchart wrote:
On Saturday 24 August 2013 02:41:59 Tomasz Figa wrote:
On Tuesday 20 of August 2013 01:04:54 Laurent Pinchart wrote:
Add DT
On Sat, Aug 24, 2013 at 8:37 PM, Al Viro wrote:
> On Fri, Aug 23, 2013 at 02:07:26AM +0100, Al Viro wrote:
>> On Thu, Aug 22, 2013 at 01:54:15PM -0700, Linus Torvalds wrote:
>> > On Thu, Aug 22, 2013 at 1:48 PM, Andy Lutomirski
>> > wrote:
>> > >
>> > > Sure. But aren't they always last?
>> >
Add a cpu_relaxt to sk_busy_loop.
Julie Cummings reported performance issues when hyperthreading is on.
Arjan van de Ven observed that we should have a cpu_relax() in the
busy poll loop.
Reported-by: Julie Cummings
Signed-off-by: Eliezer Tamir
---
include/net/busy_poll.h |1 +
1 files
The struct static_key will have a atomic_t type member no matter
whether jump label is enabled or not. We would include linux/atomic.h
when jump label is not enabled. But it also does make sense to include
this header file when jump label is enabled.
Signed-off-by: Kevin Hao
---
Inspired by Benjamin Herrenschmidt, this patch series try to reduce the
cpu/mmu feature checking overhead by using jump label. The following is
the difference of the run path of cpu_has_feature between before and after
applying these patches:
before after
addis
We plan to use the jump label in the cpu/mmu feature check on ppc.
This will need to include the jump_label.h in several very basic header
files of ppc which seems to be included by most of the other head
files implicitly or explicitly. But in the current jump_label.h,
it also include the
Hi Ian,
> This patch adds a device ID found for mid-2013 Macbook Air 6,1 from
> lsusb:
>
> Bus 001 Device 003: ID 05ac:0290 Apple, Inc.
>
> Since IDs already exist for this generation Macbook air as WELLSPRING8,
> name this one WELLSPRING8A. This only adds an ANSI version since it's
> device ID
This patch adds the Write-through memory type in combination with mtrr.
If you call ioremap_cache to request cachable memory (write-back) the function
tries to set the PAT to write-back only if the mtrr setting of the requested
region
is also marked as Write-Back.
If the mttr regions are marked
Il 24/08/2013 22:14, Yann Droneaud ha scritto:
> KVM uses anon_inode_get() to allocate file descriptors as part
> of some of its ioctls. But those ioctls are lacking a flag argument
> allowing userspace to choose options for the newly opened file descriptor.
>
> In such case it's advised to use
On Sat, Aug 24, 2013 at 04:26:30PM -0700, Dmitry Torokhov wrote:
> Hi Ian,
>
> On Sun, Aug 25, 2013 at 12:17:52AM +1000, Ian Munsie wrote:
> > This patch adds a device ID found for mid-2013 Macbook Air 6,1 from
> > lsusb:
> >
> > Bus 001 Device 003: ID 05ac:0290 Apple, Inc.
> >
> > Since IDs
On Sun, Aug 25, 2013 at 06:23:17AM +0100, Al Viro wrote:
> On Sat, Aug 24, 2013 at 11:24:32PM +0200, Willy Tarreau wrote:
>
> > I doubt it. It seems to me that most such entries are implemented
> > for completeness while most valid uses only concern /proc/self/fd.
> > Maybe if we had an option so
On Sun, Aug 25, 2013 at 06:23:17AM +0100, Al Viro wrote:
On Sat, Aug 24, 2013 at 11:24:32PM +0200, Willy Tarreau wrote:
I doubt it. It seems to me that most such entries are implemented
for completeness while most valid uses only concern /proc/self/fd.
Maybe if we had an option so that
Il 24/08/2013 22:14, Yann Droneaud ha scritto:
KVM uses anon_inode_get() to allocate file descriptors as part
of some of its ioctls. But those ioctls are lacking a flag argument
allowing userspace to choose options for the newly opened file descriptor.
In such case it's advised to use
On Sat, Aug 24, 2013 at 04:26:30PM -0700, Dmitry Torokhov wrote:
Hi Ian,
On Sun, Aug 25, 2013 at 12:17:52AM +1000, Ian Munsie wrote:
This patch adds a device ID found for mid-2013 Macbook Air 6,1 from
lsusb:
Bus 001 Device 003: ID 05ac:0290 Apple, Inc.
Since IDs already exist for
This patch adds the Write-through memory type in combination with mtrr.
If you call ioremap_cache to request cachable memory (write-back) the function
tries to set the PAT to write-back only if the mtrr setting of the requested
region
is also marked as Write-Back.
If the mttr regions are marked
Hi Ian,
This patch adds a device ID found for mid-2013 Macbook Air 6,1 from
lsusb:
Bus 001 Device 003: ID 05ac:0290 Apple, Inc.
Since IDs already exist for this generation Macbook air as WELLSPRING8,
name this one WELLSPRING8A. This only adds an ANSI version since it's
device ID is only
Inspired by Benjamin Herrenschmidt, this patch series try to reduce the
cpu/mmu feature checking overhead by using jump label. The following is
the difference of the run path of cpu_has_feature between before and after
applying these patches:
before after
addis
We plan to use the jump label in the cpu/mmu feature check on ppc.
This will need to include the jump_label.h in several very basic header
files of ppc which seems to be included by most of the other head
files implicitly or explicitly. But in the current jump_label.h,
it also include the
The struct static_key will have a atomic_t type member no matter
whether jump label is enabled or not. We would include linux/atomic.h
when jump label is not enabled. But it also does make sense to include
this header file when jump label is enabled.
Signed-off-by: Kevin Hao haoke...@gmail.com
Add a cpu_relaxt to sk_busy_loop.
Julie Cummings reported performance issues when hyperthreading is on.
Arjan van de Ven observed that we should have a cpu_relax() in the
busy poll loop.
Reported-by: Julie Cummings julie.a.cummi...@intel.com
Signed-off-by: Eliezer Tamir
On Sat, Aug 24, 2013 at 8:37 PM, Al Viro v...@zeniv.linux.org.uk wrote:
On Fri, Aug 23, 2013 at 02:07:26AM +0100, Al Viro wrote:
On Thu, Aug 22, 2013 at 01:54:15PM -0700, Linus Torvalds wrote:
On Thu, Aug 22, 2013 at 1:48 PM, Andy Lutomirski l...@amacapital.net
wrote:
Sure. But
On 08/25/2013 02:15 AM, Laurent Pinchart wrote:
On Saturday 24 August 2013 16:13:11 Tomasz Figa wrote:
On Saturday 24 of August 2013 02:54:07 Laurent Pinchart wrote:
On Saturday 24 August 2013 02:41:59 Tomasz Figa wrote:
On Tuesday 20 of August 2013 01:04:54 Laurent Pinchart wrote:
Add DT
On 08/25/2013 02:26 AM, Laurent Pinchart wrote:
Add DT bindings for the pcf857x-compatible chips and parse the device
tree node in the driver.
Signed-off-by: Laurent Pinchartlaurent.pinchart+rene...@ideasonboard.com
---
.../devicetree/bindings/gpio/gpio-pcf857x.txt | 71
On Tue, Jul 02, 2013 at 05:37:58PM +0200, Guennadi Liakhovetski wrote:
struct sh_dmae_device::chan_reg is a pointer to u32, therefore when adding
offsets to it care should be taken to add offsets in sizeof(u32) units, not
in bytes. This patch corrects such a bug. While at it we also remove the
On Tue, Jul 02, 2013 at 05:45:49PM +0200, Guennadi Liakhovetski wrote:
Hi
The first two patches in this small series improve driver internals a bit
by using preferred APIs, the 3rd patch adds support for new DMAC versions,
present on AG5, APE6, H2.
Applied, thanks
Although the patch 1
On Fri, Aug 02, 2013 at 04:18:09PM +0200, Guennadi Liakhovetski wrote:
Platform data shouldn't be changed at run-time, so, pointers to it should
be const.
Applied, thanks
~Vinod
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Fri, Aug 02, 2013 at 04:50:35PM +0200, Guennadi Liakhovetski wrote:
In this version of shdma Device Tree support I preserved the DT
configuration approach via OF device ID tables from v4, but now it is only
used for the DT-mode, the C-version is left untouched. In this series I
only
Correct spelling typo in various Kconfig files.
Signed-off-by: Masanari Iida standby2...@gmail.com
---
arch/arm/mach-sti/Kconfig| 4 ++--
drivers/cpufreq/Kconfig.x86 | 2 +-
drivers/dma/Kconfig | 2 +-
drivers/fmc/Kconfig | 2 +-
On Sat, Aug 24, 2013 at 09:09:39PM -0700, Greg Kroah-Hartman wrote:
Same as before, are you unloading and loading modules? We have a fix
for modules that cause problems when unloading with the config option
above enabled. But that shouldn't be this issue.
What seems to be is going on here is
On Wed, Aug 21, 2013 at 06:51:56PM +0900, Jingoo Han wrote:
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Can you pls rebase this as resend. I have applied bunch of sh-dma patches
stable: 3.10
commit dab9bf41b23fe700c4a74133e41eb6a21706031e upstream
1. MEI_INTEROP_TIMEOUT is in seconds not in jiffies
so we use mei_secs_to_jiffies macro
While cold boot is fast this is relevant in resume
2. wait_event_interruptible_timeout can return with
-ERESTARTSYS so do not override it
stable: 3.10
commit ff96066e3171acdea356b331163495957cb833d0 char-misc
Both H_IS and H_IE needs to be set to receive H_RDY
interrupt
1. Assert H_IS to clear the interrupts during hw reset
and use mei_me_reg_write instead of mei_hcsr_set as the later
strips down the H_IS
2. fix interrupt
stable: 3.10
commit 315a383ad7dbd484fafb93ef08038e3dbafbb7a8 upstream
ME HW ready bit is down after hw reset was asserted or on error.
Only on error we need to enter the reset flow, additional reset
need to be prevented when reset was triggered during
initialization , power up/down or a reset
stable: 3.10
commit 99f22c4ef24cf87b0dae6aabe6b5e620b62961d9 upstream
When powering up, we don't have to clean up the device state
nothing is connected.
Cc: sta...@vger.kernel.org
Tested-by: Shuah Khan shuah...@samsung.com
Signed-off-by: Tomas Winkler tomas.wink...@intel.com
Signed-off-by: Greg
Tomas Winkler (4):
mei: me: fix reset state machine
mei: don't have to clean the state on power up
mei: me: fix waiting for hw ready
mei: me: fix hardware reset flow
drivers/misc/mei/hw-me.c | 22 +-
drivers/misc/mei/init.c | 3 ++-
2 files changed, 15
On Wed, Aug 21, 2013 at 06:52:54PM +0900, Jingoo Han wrote:
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Applied, thanks
~Vinod
--
To unsubscribe from this list: send the line
Tested-by: David Oberhollenzer david.oberhollen...@tele2.at
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Am Freitag 23 August 2013, 21:10:00 schrieb Linus Walleij:
On Thu, Aug 22, 2013 at 11:56 AM, Lars Poeschel la...@wh2.tu-dresden.de
wrote:
From: Lars Poeschel poesc...@lemonage.de
The device tree property should be more descriptive.
microchip seems more reasonable than mcp. As there are
In interrupt context, after reading and comparing the UTRLDBR to
hba-outstanding_request and before resetting the interrupt aggregation,
there might be completion of another transfer request (TR). Such TRs might
get stuck, pending, until the next interrupt is generated.
The fix reads the UTRLDBR
Avoid processing garbage data by NULL terminating the strings.
Signed-off-by: Djalal Harouni tix...@opendz.org
---
Patch compile tested only.
drivers/net/wireless/ath/ath5k/debug.c | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git
On Thu, Aug 22, 2013 at 02:03:24PM -0700, Guenter Roeck wrote:
Fix:
arch/arm/common/built-in.o: undefined reference to `edma_filter_fn'
seen with make ARCH=arm allmodconfig
Commit 6cba4355 (ARM: edma: Add DT and runtime PM support to the private EDMA
API) adds a dependency on
On Wed, Aug 21, 2013 at 09:34:02PM -0300, Fabio Estevam wrote:
From: Fabio Estevam fabio.este...@freescale.com
When CONFIG_ARM_LPAE=y the following build warning are generated:
drivers/dma/ste_dma40.c:3228:2: warning: format '%x' expects argument of type
'unsigned int', but argument 4 has
101 - 200 of 338 matches
Mail list logo
