Hi,
On Tuesday 04 August 2015 09:28 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Aug 04, 2015 at 07:36:09PM +0530, Kishon Vijay Abraham I wrote:
>> Deprecate using phy-omap-control driver to write to the mailbox register
>> and start using *syscon* framework to do the same.
>>
>> Signed-off-by:
Since CMS is an evolution of PKCS#7, with much of the ASN.1 being
compatible, add support for CMS signed-data messages also [RFC5652 sec 5].
Signed-off-by: David Howells
Reviewed-By: David Woodhouse
---
crypto/asymmetric_keys/pkcs7.asn1 | 10 +
crypto/asymmetric_keys/pkcs7_parser.c
Make the X.509 ASN.1 time object decoder fill in a time64_t rather than a
struct tm to make comparison easier (unfortunately, this makes readable
display less easy) and export it so that it can be used by the PKCS#7 code
too.
Further, tighten up its parsing to reject invalid dates (eg. weird
Restrict the content type in the and the authenticated attributes permitted
in a PKCS#7 SignedData object according the purpose to which the message is
being put:
(*) VERIFYING_MODULE_SIGNATURE
(*) VERIFYING_FIRMWARE_SIGNATURE
(*) VERIFYING_UNSPECIFIED_SIGNATURE
These three all require
Make sign-file use the OpenSSL CMS routines to generate a message to be
used as the signature blob instead of the PKCS#7 routines. This allows us
to change how the matching X.509 certificate is selected. With PKCS#7 the
only option is to match on the serial number and issuer fields of an X.509
Extract the function that drives the PKCS#7 signature verification given a
data blob and a PKCS#7 blob out from the module signing code and lump it with
the system keyring code as it's generic. This makes it independent of module
config options and opens it to use by the firmware loader.
From: Igal Liberman
This patch adds The FMan Port configuration, initialization and
runtime control routines.
Signed-off-by: Igal Liberman
---
drivers/net/ethernet/freescale/fman/Makefile |2 +-
drivers/net/ethernet/freescale/fman/fm.c | 251 -
From: David Woodhouse
Where an external PEM file or PKCS#11 URI is given, we can get the cert
from it for ourselves instead of making the user drop signing_key.x509
in place for us.
Signed-off-by: David Woodhouse
Signed-off-by: David Howells
---
Documentation/module-signing.txt | 11 +--
From: David Woodhouse
Signed-off-by: David Woodhouse
Signed-off-by: David Howells
---
scripts/Makefile.modinst |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Makefile.modinst b/scripts/Makefile.modinst
index e48a4e9d8868..07650eeaaf06 100644
---
Add an ASN.1 compiler option to dump the element tree to stdout.
Signed-off-by: David Howells
Reviewed-By: David Woodhouse
---
scripts/asn1_compiler.c | 88 +--
1 file changed, 76 insertions(+), 12 deletions(-)
diff --git
Provide a utility that:
(1) Digests a module using the specified hash algorithm (typically sha256).
[The digest can be dumped into a file by passing the '-d' flag]
(2) Generates a PKCS#7 message that:
(a) Has detached data (ie. the module content).
(b) Is signed with the
If an X.509 certificate has an AuthorityKeyIdentifier extension that provides
an issuer and serialNumber, then make it so that these are used in preference
to the keyIdentifier field also held therein for searching for the signing
certificate.
If both the issuer+serialNumber and the keyIdentifier
The key identifiers fabricated from an X.509 certificate are currently:
(A) Concatenation of serial number and issuer
(B) Concatenation of subject and subjectKeyID (SKID)
When verifying one X.509 certificate with another, the AKID in the target
can be used to match the authoritative
Copy string names to tokens in ASN.1 compiler rather than storing a pointer
into the source text. This means we don't have to use "%*.*s" all over the
place.
Signed-off-by: David Howells
Reviewed-by: David Woodhouse
---
scripts/asn1_compiler.c | 155
It is possible for a PKCS#7 message to have detached data. However, to verify
the signatures on a PKCS#7 message, we have to be able to digest the data.
Provide a function to supply that data. An error is given if the PKCS#7
message included embedded data.
This is used in a subsequent patch to
From: David Woodhouse
Let the user explicitly provide a file containing trusted keys, instead of
just automatically finding files matching *.x509 in the build tree and
trusting whatever we find. This really ought to be an *explicit*
configuration, and the build rules for dealing with the files
akefile magic
he added to deal with quotes and quoting encountered when using CONFIG_*
option strings in the makefile.
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=modsign-pkcs7
and are tagged with:
modsign-pkcs7-2015080
Move to using PKCS#7 messages as module signatures because:
(1) We have to be able to support the use of X.509 certificates that don't
have a subjKeyId set. We're currently relying on this to look up the
X.509 certificate in the trusted keyring list.
(2) PKCS#7 message signed
We only support PKCS#7 signed-data [RFC2315 sec 9] content at the top level,
so reject anything else. Further, check that the version numbers in
SignedData and SignerInfo are 1 in both cases.
Note that we don't restrict the inner content type. In the PKCS#7 code we
don't parse the data attached
From: David Woodhouse
Signed-off-by: David Woodhouse
Signed-off-by: David Howells
---
Documentation/module-signing.txt | 31 ++-
Makefile |2 +-
init/Kconfig | 14 ++
kernel/Makefile
From: Igal Liberman
Add Frame Manager Multi-User RAM support.
Signed-off-by: Igal Liberman
---
drivers/net/ethernet/freescale/fman/Kconfig|1 +
drivers/net/ethernet/freescale/fman/Makefile |6 +-
drivers/net/ethernet/freescale/fman/fm_muram.c | 115
From: Igal Liberman
Add Frame Manger Driver support.
This patch adds The FMan configuration, initialization and
runtime control routines.
Signed-off-by: Igal Liberman
---
drivers/net/ethernet/freescale/fman/Makefile |2 +-
drivers/net/ethernet/freescale/fman/fm.c | 1076
From: Igal Liberman
Add Storage Profiles support.
The Storage Profiles contain parameters that are used by the FMan in
order to store frames being received on the Rx ports, or to
determine the parameters that affect writing the Internal Context
in the frame margin on Tx.
Signed-off-by: Igal
From: David Woodhouse
The current rule for generating signing_key.priv and signing_key.x509 is
a classic example of a bad rule which has a tendency to break parallel
make. When invoked to create *either* target, it generates the other
target as a side-effect that make didn't predict.
So let's
From: Luis R. Rodriguez
Make the -d option (which currently isn't actually wired to anything) write
out the PKCS#7 message as per the -p option and then exit without either
modifying the source or writing out a compound file of the source, signature
and metadata.
This will be useful when
On 05.08.2015 15:48, Rafael J. Wysocki wrote:
On Tuesday, August 04, 2015 04:01:59 PM David Daney wrote:
From: Tomasz Nowicki
Fixes the following build error when building drivers as modules:
ERROR: "acpi_dev_prop_read_single" [drivers/net/phy/mdio-octeon.ko] undefined!
ERROR:
From: Paul Gortmaker
As of commit dae6e64d2bcfd4b06304ab864c7e3a4f6b5fedf4 ("rcu: Introduce
proper blocking to no-CBs kthreads GP waits") the RCU subsystem started
making use of wait queues.
Here we convert all additions of RCU wait queues to use simple wait queues,
since they don't need the
From: Paul Gortmaker
Completions have no long lasting callbacks and therefore do not need
the complex waitqueue variant. Use simple waitqueues which reduces
the contention on the waitqueue lock.
This was a carry forward from v3.10-rt, with some RT specific chunks,
dropped, and updated to align
Hi,
It's a while since the last attempt by Paul to get simple wait ready
for mainline [1]. At the last realtime workshop it was discussed how
the swait implementation could be made preempt aware. Peter posted an
untested version of it here [2].
In order to test it, I used Paul's two patches
From: Peter Zijlstra
On Tue, Feb 17, 2015 at 06:44:19PM +0100, Sebastian Andrzej Siewior wrote:
> * Peter Zijlstra | 2015-01-21 16:07:16 [+0100]:
>
> >On Tue, Jan 20, 2015 at 01:16:13PM -0500, Steven Rostedt wrote:
> >> I'm actually wondering if we should just nuke the _interruptible()
> >>
This prepares the driver for removal of platform data.
Signed-off-by: Heikki Krogerus
---
net/rfkill/rfkill-gpio.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/net/rfkill/rfkill-gpio.c b/net/rfkill/rfkill-gpio.c
index d5d58d9..07323c3 100644
---
Helper for finding the type based on name. Useful if the
type needs to be determined based on device property.
Signed-off-by: Heikki Krogerus
---
include/linux/rfkill.h | 15 +
net/rfkill/core.c | 57 +-
2 files changed, 44
Pass the rfkill name and type to the device with properties
instead of driver specific platform data.
Signed-off-by: Heikki Krogerus
CC: Alexandre Courbot
CC: Thierry Reding
CC: Stephen Warren
---
arch/arm/mach-tegra/board-paz00.c | 17 ++---
1 file changed, 10 insertions(+), 7
Marcos for easier creation of build-in property entries.
Signed-off-by: Heikki Krogerus
---
include/linux/property.h | 35 +++
1 file changed, 35 insertions(+)
diff --git a/include/linux/property.h b/include/linux/property.h
index 76ebde9..204d899 100644
---
No more users for it.
Signed-off-by: Heikki Krogerus
---
include/linux/rfkill-gpio.h | 37 -
net/rfkill/Kconfig | 3 +--
net/rfkill/rfkill-gpio.c| 8
3 files changed, 1 insertion(+), 47 deletions(-)
delete mode 100644
The first patch adds a few helper macros for build-in property
creation and the second makes it possible to get the rfkill type
index based on name. The rest deal with rfkill-gpio.
Cheers,
Heikki Krogerus (5):
device property: helper macros for property entry creation
net: rfkill: add
On 05/08/2015 15:34, Radim Krčmář wrote:
> 2015-08-05 15:29+0200, Paolo Bonzini:
>> On 05/08/2015 15:21, Radim Krčmář wrote:
>>> + kvm_for_each_vcpu(idx, vcpu, kvm)
>>> + if (vcpu->vcpu_id == vcpu_id) {
>>> + kvm_make_request(KVM_REQ_EXIT, vcpu);
>>> +
2015-08-05 15:29+0200, Paolo Bonzini:
> On 05/08/2015 15:21, Radim Krčmář wrote:
>> +kvm_for_each_vcpu(idx, vcpu, kvm)
>> +if (vcpu->vcpu_id == vcpu_id) {
>> +kvm_make_request(KVM_REQ_EXIT, vcpu);
>> +kvm_vcpu_kick(vcpu);
>> +
>> +
On Wed, Jul 15 2015 at 6:14pm -0400,
Jens Axboe wrote:
> On 07/15/2015 10:29 AM, Mike Snitzer wrote:
> >On Wed, Jul 15 2015 at 11:30am -0400,
> >Jens Axboe wrote:
> >
> >>On 07/15/2015 05:46 AM, Austin S Hemmelgarn wrote:
> >>>On 2015-07-14 17:48, Jens Axboe wrote:
> On 07/14/2015 02:45
* Dmitry Torokhov [150803 13:05]:
> On Mon, Aug 03, 2015 at 03:21:21AM -0700, Tony Lindgren wrote:
> >
> > Hmm why do we need the check for if (device_can_wakeup(>dev)))?
>
> Because of the code in device_wakeup_attach_irq():
>
> ws = dev->power.wakeup;
> if (!ws) {
>
Hi,
Cc Julia Lawall
On (08/04/15 13:06), Brian Norris wrote:
> On Tue, Aug 04, 2015 at 08:46:30PM +0100, Salah Triki wrote:
> > kmem_cache_destroy can be called with NULL values. Thus, the checks that
> > precede the calls are useless.
>
> This isn't *currently* true. Only after a bit of work
r5 does contain the value to be updated, so lets use r5 all way long
for that. It makes the code more readable.
To avoid confusion, it is better to use adde instead of addc
The first addition is useless. Its only purpose is to clear carry.
As r4 is a signed int that is always positive, this can
From: Igal Liberman
The FMan MAC FLib provides basic API used by the drivers to
configure and control the FMan MAC hardware.
Signed-off-by: Igal Liberman
---
drivers/net/ethernet/freescale/fman/Makefile |1 +
.../net/ethernet/freescale/fman/flib/fsl_enet.h| 135
On 08/05/2015 07:06 AM, Madars Vitolins wrote:
> Jason Baron @ 2015-08-04 18:02 rakstīja:
>> On 08/03/2015 07:48 PM, Eric Wong wrote:
>>> Madars Vitolins wrote:
Hi Folks,
I am developing kind of open systems application, which uses
multiple processes/executables where each of
From: Igal Liberman
Add Frame Manger MAC Driver support.
This patch adds The FMan MAC configuration, initialization and
runtime control routines.
This patch contains support for these types of MACs:
tGEC, dTSEC and mEMAC
Signed-off-by: Igal Liberman
---
On 05/08/2015 15:21, Radim Krčmář wrote:
> + kvm_for_each_vcpu(idx, vcpu, kvm)
> + if (vcpu->vcpu_id == vcpu_id) {
> + kvm_make_request(KVM_REQ_EXIT, vcpu);
> + kvm_vcpu_kick(vcpu);
> +
> + return 0;
> + }
>
On the 8xx, load latency is 2 cycles and taking branches also takes
2 cycles. So let's unroll the loop.
Signed-off-by: Christophe Leroy
---
v2: Only use lwzu for the last load as lwzu has undocumented
additional latency
arch/powerpc/lib/checksum_32.S | 16 +++-
1 file
From: Igal Liberman
The Freescale Data Path Acceleration Architecture (DPAA)
is a set of hardware components on specific QorIQ multicore processors.
This architecture provides the infrastructure to support simplified
sharing of networking interfaces and accelerators by multiple CPU cores
and the
From: Igal Liberman
The FMan FLib provides the basic API used by the FMan drivers to
configure and control the FMan hardware.
Signed-off-by: Igal Liberman
---
drivers/net/ethernet/freescale/Kconfig |1 +
drivers/net/ethernet/freescale/Makefile|2 +
The purpose of this patchset is to optimise csum_partial() on powerpc32.
In the first part, we remove some unneccessary instructions
In the second part, we partially unloop the main loop
Christophe Leroy (2):
Optimise a few instructions in csum_partial()
Optimise csum_partial() loop
On 05.08.2015 16:01, Vlastimil Babka wrote:
Reposting due to lack of feedback in May. I hope at least patches 1 and 2
could be merged as they are IMHO bugfixes. 3 and 4 is optional but IMHO useful.
Changes since v2:
o Rebase on next-20150805.
o This means that /proc/pid/maps has
Use __acquire() and __release() in the right place to silence the sparse
lock checking warning.
drivers/staging/sm750fb/sm750.c:177:13: warning: context imbalance in
'lynxfb_ops_fillrect' - different lock contexts for basic block
drivers/staging/sm750fb/sm750.c:243:9: warning: context imbalance
On Saturday 25 July 2015 23:46:56 Pali Rohár wrote:
> Driver bq2415x_charger works also without notify power supply device for
> charger detection. But when charger detection is specified in DT, then
> bq2415x_charger refused to loaded with -EPROBE_DEFER.
>
> This patch rewrites code so that
We want to have requests abstracted from bit operations.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/vmx.c | 2 +-
include/linux/kvm_host.h | 7 ++-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 217f66343dc8..17514fe7d2cb
at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
tags/asn1-fixes-20150805
for you to fetch changes up to 233ce79db4b23a174bcf30bde5d6ad913d5f46d3:
ASN.1: Handle 'ANY OPTIONAL' in grammar (2015-08-05 13:38:07 +0100
VCPU with vcpu->vcpu_id has highest probability of being stored in
kvm->vcpus[vcpu->vcpu_id]. Other common case, sparse sequential
vcpu_id, is more likely to find a match downwards from vcpu->vcpu_id.
Random distribution does not matter so we first search slots
[vcpu->vcpu_id..0] and then slots
Hi Marc,
On 08/04/2015 08:27 PM, Marc Zyngier wrote:
On 29/07/15 11:08, Hanjun Guo wrote:
This self-probe infrastructure works in the similar way as OF,
but there is some different in the mechanism:
For DT, the init fn will be called once it finds compatible strings
in DT, but for ACPI, we
Hi Alex,
On 07/16/2015 11:26 PM, Alex Williamson wrote:
> When a physical I/O device is assigned to a virtual machine through
> facilities like VFIO and KVM, the interrupt for the device generally
> bounces through the host system before being injected into the VM.
> However, hardware technologies
When userspace wants KVM to exit to userspace, it sends a signal.
This has a disadvantage of requiring a change to the signal mask because
the signal needs to be blocked in userspace to stay pending when sending
to self.
Using a request flag allows us to shave 200-300 cycles from every
userspace
We are still interested in the amount of exits userspace requested and
signal_exits doesn't cover that anymore.
Signed-off-by: Radim Krčmář
---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/x86.c | 2 ++
2 files changed, 3 insertions(+)
diff --git
The guest can use KVM_USER_EXIT instead of a signal-based exiting to
userspace. Availability depends on KVM_CAP_USER_EXIT.
Only x86 is implemented so far.
It would be cleaner to use 'unsigned long' to store the vcpu_id, but I
really don't like its variable size and 'u64' will be same/bigger for
QEMU uses SIGUSR1 to force a userspace exit and also to queue an early
exit before calling VCPU_RUN -- the signal is blocked in user space and
temporarily unblocked in VCPU_RUN.
The temporal unblocking by sigprocmask() in kvm_arch_vcpu_ioctl_run()
takes a shared siglock, which leads to cacheline
On 08/05/2015 08:11 AM, check.ker...@gmail.com wrote:
> From: yangdongdong
>
> This also enables panic and oops messages which
> in suspend context to be logged into ramoops console
> buffer where it can be read back at some later point.
>
> Signed-off-by: yangdongdong
> Signed-off-by:
On 05.08.2015 16:01, Vlastimil Babka wrote:
From: Jerome Marchand
It's currently inconvenient to retrieve MM_ANONPAGES value from status
and statm files and there is no way to separate MM_FILEPAGES and
MM_SHMEMPAGES. Add VmAnon, VmFile and VmShm lines in /proc//status
to solve these issues.
On Tuesday, August 04, 2015 04:01:59 PM David Daney wrote:
> From: Tomasz Nowicki
>
> Fixes the following build error when building drivers as modules:
>
> ERROR: "acpi_dev_prop_read_single" [drivers/net/phy/mdio-octeon.ko]
> undefined!
> ERROR: "acpi_dev_prop_read_single"
>
An ANY object in an ASN.1 grammar that is marked OPTIONAL should be skipped
if there is no more data to be had.
This can be tested by editing X.509 certificates or PKCS#7 messages to
remove the NULL from subobjects that look like the following:
SEQUENCE {
If the ASN.1 decoder is asked to parse a sequence of objects, non-optional
matches get skipped if there's no more data to be had rather than a
data-overrun error being reported.
This is due to the code segment that decides whether to skip optional
matches (ie. matches that could get ignored
On Wed, Aug 05, 2015 at 02:37:59PM +0200, Frederic Weisbecker wrote:
> On Tue, Aug 04, 2015 at 08:12:50PM -0400, Dave Jones wrote:
> > On Tue, Aug 04, 2015 at 12:54:35AM -0400, Sasha Levin wrote:
> > > On 08/03/2015 06:03 PM, Paul E. McKenney wrote:
> > > >> > Ugh, that doesn't revert
In an ASN.1 description where there is a CHOICE construct that contains
elements with IMPLICIT tags that refer to constructed types, actions to be
taken on those elements should be conditional on the corresponding element
actually being matched. Currently, however, such actions are performed
Fix the handling of CHOICE types in the ASN.1 compiler to make SEQUENCE and
SET elements in a CHOICE be correctly rendered as skippable and conditional
as appropriate.
For example, in the following ASN.1:
Foo ::= SEQUENCE { w1 INTEGER, w2 Bar, w3 OBJECT IDENTIFIER }
Bar ::=
On Wed, Aug 5, 2015 at 4:53 AM, Kirill A. Shutemov wrote:
>> 'only' if it's multi-threaded, i.e. when some workload cares so much about
>> performance that it uses multiple threads?
>>
>> Can you see the contradiction there?
>
> I can. man 2 unshare:
>
> CLONE_NEWUSER requires that the
On Wed, Aug 05, 2015 at 01:15:50PM +0200, Michal Nazarewicz wrote:
> > On Wed, Aug 05, 2015 at 12:28:03PM +0200, Michal Nazarewicz wrote:
> >> If you need several CMA areas to allocate from, create multiple struct
> >> devices.
>
> On Wed, Aug 05 2015, Feng Tang wrote:
> > I've made a quick
On 08/05/2015 08:57 PM, Marc Zyngier wrote:
On 05/08/15 13:40, Hanjun Guo wrote:
On 08/04/2015 08:06 PM, Marc Zyngier wrote:
On 29/07/15 11:08, Hanjun Guo wrote:
There is a field added in ACPI 6.0 MADT table to indicate the
GIC version, so parse the table to get its value for later use.
If
From: yangdongdong
This also enables panic and oops messages which
in suspend context to be logged into ramoops console
buffer where it can be read back at some later point.
Signed-off-by: yangdongdong
Signed-off-by: gulinghua
---
fs/pstore/ram.c| 21 +
On 08/04, Linus Torvalds wrote:
>
> I refused to have something that broke the tasklist lock, so the "irq
> users nest" was a requirement.
And I was going to reply that this breaks tasklist lock anyway but
failed to find anything wrong after the quick grep.
> So it's not like I love the current
On 31 July 2015 at 21:03, Kees Cook wrote:
> On Fri, Jul 31, 2015 at 2:13 AM, Tomeu Vizoso wrote:
>> On 25 July 2015 at 01:20, Kees Cook wrote:
>>> Many callers either use NULL or const strings for the third argument of
>>> clk_register_clkdev. For those that do not, this is a risk for format
Reposting due to lack of feedback in May. I hope at least patches 1 and 2
could be merged as they are IMHO bugfixes. 3 and 4 is optional but IMHO useful.
Changes since v2:
o Rebase on next-20150805.
o This means that /proc/pid/maps has the proportional swap share (SwapPss:)
field as per https
From: Jerome Marchand
It's currently inconvenient to retrieve MM_ANONPAGES value from status
and statm files and there is no way to separate MM_FILEPAGES and
MM_SHMEMPAGES. Add VmAnon, VmFile and VmShm lines in /proc//status
to solve these issues.
Signed-off-by: Jerome Marchand
Signed-off-by:
Currently, /proc/pid/smaps will always show "Swap: 0 kB" for shmem-backed
mappings, even if the mapped portion does contain pages that were swapped out.
This is because unlike private anonymous mappings, shmem does not change pte
to swap entry, but pte_none when swapping the page out. In the smaps
The documentation for /proc/pid/status does not mention that the value of
VmSwap counts only swapped out anonymous private pages and not shmem. This is
not obvious, so document this limitation.
Signed-off-by: Vlastimil Babka
---
Documentation/filesystems/proc.txt | 2 ++
1 file changed, 2
From: Jerome Marchand
Currently looking at /proc//status or statm, there is no way to
distinguish shmem pages from pages mapped to a regular file (shmem
pages are mapped to /dev/zero), even though their implication in
actual memory use is quite different.
This patch adds MM_SHMEMPAGES counter to
On 05/08/15 13:40, Hanjun Guo wrote:
> On 08/04/2015 08:06 PM, Marc Zyngier wrote:
>> On 29/07/15 11:08, Hanjun Guo wrote:
>>> There is a field added in ACPI 6.0 MADT table to indicate the
>>> GIC version, so parse the table to get its value for later use.
>>>
>>> If GIC version presented in MADT
On 5 August 2015 at 14:44, Mark Brown wrote:
> On Wed, Aug 05, 2015 at 02:40:01PM +0200, Michal Suchanek wrote:
>> On 5 August 2015 at 13:50, Mark Brown wrote:
>
>> > As far as I can tell you want to set a per spi_message flag saying that
>> > the message is a flash read command? If that's what
Hello Steve,
May I have your further comments/suggestions on this version of patchset?
I know you were just back from a vacation, and must be very busy
recently, but after you finished the most urgent matters, could you
please leave us a little bandwidth to think about how you want these
patches
On 08/05/2015 08:33 AM, Julien Grall wrote:
On 05/08/15 13:19, Boris Ostrovsky wrote:
On 08/05/2015 06:51 AM, Julien Grall wrote:
diff --git a/drivers/video/fbdev/xen-fbfront.c
b/drivers/video/fbdev/xen-fbfront.c
index 09dc447..25e3cce 100644
--- a/drivers/video/fbdev/xen-fbfront.c
+++
Hello Tomeu,
On Wed, Aug 5, 2015 at 2:24 PM, Tomeu Vizoso wrote:
> ...if there isn't one already.
>
I think is better to instead splitting the subject line like this, to
change it for something that fits like "memory: omap-gpmc: Don't try
to save uninitialized GPMC context" or "memory:
On Wed, Aug 05, 2015 at 02:40:01PM +0200, Michal Suchanek wrote:
> On 5 August 2015 at 13:50, Mark Brown wrote:
> > As far as I can tell you want to set a per spi_message flag saying that
> > the message is a flash read command? If that's what this is trying to
> > do then why do you need to
On Wednesday 05 August 2015 04:16 PM, Shubhrajyoti Datta wrote:
hi ,
On Tue, Jul 21, 2015 at 6:11 PM, Vaibhav Hiremath
wrote:
From: Yi Zhang
Enable i2c module/unit before transmission and disable when it
finishes.
why?
It's because the i2c bus may be disturbed if the slave device,
On 5 August 2015 at 13:50, Mark Brown wrote:
> On Tue, Aug 04, 2015 at 11:29:52PM +0530, R, Vignesh wrote:
>> On 8/4/2015 9:21 PM, Mark Brown wrote:
>> > On Mon, Aug 03, 2015 at 10:27:19AM +0530, Vignesh R wrote:
>
>> > I still can't tell from the above what this interface is supposed to do.
>> >
On 08/04/2015 08:06 PM, Marc Zyngier wrote:
On 29/07/15 11:08, Hanjun Guo wrote:
There is a field added in ACPI 6.0 MADT table to indicate the
GIC version, so parse the table to get its value for later use.
If GIC version presented in MADT is 0, we need to fallback to
hardware discovery to get
On Tue, Aug 04, 2015 at 08:12:50PM -0400, Dave Jones wrote:
> On Tue, Aug 04, 2015 at 12:54:35AM -0400, Sasha Levin wrote:
> > On 08/03/2015 06:03 PM, Paul E. McKenney wrote:
> > >> > Ugh, that doesn't revert cleanly. Got something handy ?
> > > I do not, but perhaps either Sasha or Frederic
On 08/03/2015 05:51 PM, Viresh Kumar wrote:
On 03-08-15, 17:03, Geert Uytterhoeven wrote:
I'm seeing the same WARNING on ARM (r8a7740/armadillo), and it's fixed by
your patch.
Tested-by: Geert Uytterhoeven
Thanks. Daniel is back now and we should see this in linux-next soon.
Fixed and
On 05.08.2015 04:03, Peter Hurley wrote:
> On 08/04/2015 07:25 PM, Maciej S. Szmigiero wrote:
>> Hi Peter,
>>
>> Thanks for looking into it.
>>
>> On 04.08.2015 03:46, Peter Hurley wrote:
>>> Hi Maciej,
>>>
>>> On 08/02/2015 05:09 PM, Maciej S. Szmigiero wrote:
CIR type serial ports aren't
On 08/05/2015 06:43 PM, Jeff Kirsher wrote:
Is your intention that this patch replace the existing patch:
http://patchwork.ozlabs.org/patch/502990/
...which is currently in my queue?
Okay, please replace the previous patch.
--
To unsubscribe from this list: send the line "unsubscribe
On 05/08/15 13:19, Boris Ostrovsky wrote:
> On 08/05/2015 06:51 AM, Julien Grall wrote:
>>
diff --git a/drivers/video/fbdev/xen-fbfront.c
b/drivers/video/fbdev/xen-fbfront.c
index 09dc447..25e3cce 100644
--- a/drivers/video/fbdev/xen-fbfront.c
+++
CIR type serial ports aren't real serial ports.
This is just a way to prevent legacy 8250 serial
driver from probing and eventually binding some
resources.
Since in current state such ports aren't providing
any real functionality and it is not possible
to change their type via
This adds support for the Mediatek thermal controller found on MT8173
and likely other SoCs.
The controller is a bit special. It does not have its own ADC, instead
it controls the on-SoC AUXADC via AHB bus accesses. For this reason
we need the physical address of the AUXADC. Also it controls a mux
Signed-off-by: Sascha Hauer
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 27237a1..ddacb86 100644
---
Signed-off-by: Sascha Hauer
---
.../bindings/thermal/mediatek-thermal.txt | 38 ++
1 file changed, 38 insertions(+)
create mode 100644
Documentation/devicetree/bindings/thermal/mediatek-thermal.txt
diff --git
This series adds support for the thermal sensors included in the
MT8173 SoC. Currently only basic temperature reading is supported
without any interrupt support.
The cpufreq driver for MT8173 is currently under review, so there's no
real cooling device available in mainline. Until this is
701 - 800 of 2158 matches
Mail list logo
