On Tue, 9 Oct 2018, David Howells wrote:
>
> Hi James,
>
> Here's a set of patches that does the following, if you could pull it please:
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
next-keys
and next-testing
Please test.
--
James Morris
On Mon, Oct 8, 2018 at 11:53 PM Aleksa Sarai wrote:
> * AT_NO_PROCLINK: Disallows ->get_link "symlink" jumping. This is a very
> specific restriction, and it exists because /proc/$pid/fd/...
> "symlinks" allow for access outside nd->root and pose risk to
> container runtimes that don't want
On Tue, 9 Oct 2018, David Howells wrote:
>
> Hi James,
>
> Here's a set of patches that does the following, if you could pull it please:
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
next-keys
and next-testing
Please test.
--
James Morris
On Mon, Oct 8, 2018 at 11:53 PM Aleksa Sarai wrote:
> * AT_NO_PROCLINK: Disallows ->get_link "symlink" jumping. This is a very
> specific restriction, and it exists because /proc/$pid/fd/...
> "symlinks" allow for access outside nd->root and pose risk to
> container runtimes that don't want
On Thu, Oct 4, 2018 at 6:50 PM Joel Fernandes (Google)
wrote:
>
> I am one of the main engineers working on ashmem. I have been fixing
> bugs in the driver and have been involved in the memfd conversion
> discussions and sending patches about that. I also have an understanding
> of the binder
On Thu, Oct 4, 2018 at 6:50 PM Joel Fernandes (Google)
wrote:
>
> I am one of the main engineers working on ashmem. I have been fixing
> bugs in the driver and have been involved in the memfd conversion
> discussions and sending patches about that. I also have an understanding
> of the binder
[Resending to a wider audience]
In trying to get the termios2 interface actually implemented in glibc,
the question came up if we will ever care about baud rates in excess of
4 Gbps, even in the relatively remote future.
If this is something we care about *at all*, I would like to suggest
that
[Resending to a wider audience]
In trying to get the termios2 interface actually implemented in glibc,
the question came up if we will ever care about baud rates in excess of
4 Gbps, even in the relatively remote future.
If this is something we care about *at all*, I would like to suggest
that
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
On Tue, 2018-10-09 at 14:46 -0400, Jason Gunthorpe wrote:
>
>
> On Tue., Oct. 9, 2018, 2:44 p.m. Kamal Heib, wrote:
> > On Tue, Oct 09, 2018 at 02:31:27PM -0400, Doug Ledford wrote:
> > > On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> > > > This patchset introduce a new structure that
On Tue, 2018-10-09 at 14:46 -0400, Jason Gunthorpe wrote:
>
>
> On Tue., Oct. 9, 2018, 2:44 p.m. Kamal Heib, wrote:
> > On Tue, Oct 09, 2018 at 02:31:27PM -0400, Doug Ledford wrote:
> > > On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> > > > This patchset introduce a new structure that
This will allow to use generic refcount_t interfaces
to check counters overflow instead of currently existing
VM_BUG_ON(). The only difference after the patch is
VM_BUG_ON() may cause BUG(), while refcount_t fires
with WARN(). But this seems not to be significant here,
since such the problems are
This will allow to use generic refcount_t interfaces
to check counters overflow instead of currently existing
VM_BUG_ON(). The only difference after the patch is
VM_BUG_ON() may cause BUG(), while refcount_t fires
with WARN(). But this seems not to be significant here,
since such the problems are
On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing
> > > private
On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing
> > > private
Can you reproduce the segfault from the perf.data file I provided?
Tony
On Tue, Oct 9, 2018 at 11:47 AM Jiri Olsa wrote:
>
> On Tue, Oct 09, 2018 at 11:27:04AM -0500, Anthony LaTorre wrote:
> > Hi,
> >
> > I'm currently running Linux kernel 4.18.10-100.fc27.x86_64 and have a
> > problem
Can you reproduce the segfault from the perf.data file I provided?
Tony
On Tue, Oct 9, 2018 at 11:47 AM Jiri Olsa wrote:
>
> On Tue, Oct 09, 2018 at 11:27:04AM -0500, Anthony LaTorre wrote:
> > Hi,
> >
> > I'm currently running Linux kernel 4.18.10-100.fc27.x86_64 and have a
> > problem
From: "Wesley W. Terpstra"
DT documentation for PWM controller added with updated compatible
string.
Signed-off-by: Wesley W. Terpstra
[Atish: Compatible string update]
Signed-off-by: Atish Patra
---
.../devicetree/bindings/pwm/pwm-sifive.txt | 32 ++
1 file
From: "Wesley W. Terpstra"
Adds the GPIO driver for SiFive RISC-V SoCs.
Signed-off-by: Wesley W. Terpstra
[Atish: Various fixes and code cleanup]
Signed-off-by: Atish Patra
---
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-sifive.c | 326
From: "Wesley W. Terpstra"
DT documentation for PWM controller added with updated compatible
string.
Signed-off-by: Wesley W. Terpstra
[Atish: Compatible string update]
Signed-off-by: Atish Patra
---
.../devicetree/bindings/pwm/pwm-sifive.txt | 32 ++
1 file
From: "Wesley W. Terpstra"
Adds the GPIO driver for SiFive RISC-V SoCs.
Signed-off-by: Wesley W. Terpstra
[Atish: Various fixes and code cleanup]
Signed-off-by: Atish Patra
---
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-sifive.c | 326
From: "Wesley W. Terpstra"
DT documentation for GPIO added with updated compatible
string.
Signed-off-by: Wesley W. Terpstra
[Atish: Compatible string update]
Signed-off-by: Atish Patra
---
.../devicetree/bindings/gpio/gpio-sifive.txt | 28 ++
1 file changed, 28
From: "Wesley W. Terpstra"
DT documentation for GPIO added with updated compatible
string.
Signed-off-by: Wesley W. Terpstra
[Atish: Compatible string update]
Signed-off-by: Atish Patra
---
.../devicetree/bindings/gpio/gpio-sifive.txt | 28 ++
1 file changed, 28
From: "Wesley W. Terpstra"
Adds a PWM driver for PWM chip present in SiFive's HiFive Unleashed SoC.
Signed-off-by: Wesley W. Terpstra
[Atish: Various fixes and code cleanup]
Signed-off-by: Atish Patra
---
drivers/pwm/Kconfig | 10 ++
drivers/pwm/Makefile | 1 +
From: "Wesley W. Terpstra"
Adds a PWM driver for PWM chip present in SiFive's HiFive Unleashed SoC.
Signed-off-by: Wesley W. Terpstra
[Atish: Various fixes and code cleanup]
Signed-off-by: Atish Patra
---
drivers/pwm/Kconfig | 10 ++
drivers/pwm/Makefile | 1 +
This patch series adds GPIO & PWM drivers and DT documentation
for HiFive Unleashed board. The patches are mostly based on
Wesley's patch.
Wesley W. Terpstra (4):
pwm: sifive: Add DT documentation for SiFive PWM Controller.
pwm: sifive: Add a driver for SiFive SoC PWM
gpio: sifive: Add DT
This patch series adds GPIO & PWM drivers and DT documentation
for HiFive Unleashed board. The patches are mostly based on
Wesley's patch.
Wesley W. Terpstra (4):
pwm: sifive: Add DT documentation for SiFive PWM Controller.
pwm: sifive: Add a driver for SiFive SoC PWM
gpio: sifive: Add DT
The shadow shrinker is invoked per NUMA node, but the shadow limit
enforced for cgroups is based on the page counter, which isn't NUMA
aware. Instead of shrinking shadow pages to desired_size, we end up
with desired_size * nr_online_nodes.
Switch to NUMA-aware lru and slab counters to approximate
The shadow shrinker is invoked per NUMA node, but the shadow limit
enforced for cgroups is based on the page counter, which isn't NUMA
aware. Instead of shrinking shadow pages to desired_size, we end up
with desired_size * nr_online_nodes.
Switch to NUMA-aware lru and slab counters to approximate
Make it easier to catch bugs in the shadow node shrinker by adding a
counter for the shadow nodes in circulation.
Signed-off-by: Johannes Weiner
---
include/linux/mmzone.h | 1 +
mm/vmstat.c| 1 +
mm/workingset.c| 12 ++--
3 files changed, 12 insertions(+), 2
Make it easier to catch bugs in the shadow node shrinker by adding a
counter for the shadow nodes in circulation.
Signed-off-by: Johannes Weiner
---
include/linux/mmzone.h | 1 +
mm/vmstat.c| 1 +
mm/workingset.c| 12 ++--
3 files changed, 12 insertions(+), 2
No need to use the preemption-safe lruvec state function inside the
reclaim region that has irqs disabled.
Signed-off-by: Johannes Weiner
---
mm/workingset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/workingset.c b/mm/workingset.c
index e5c70bc94077..f564aaa6b71d
The page cache and most shrinkable slab caches hold data that has been
read from disk, but there are some caches that only cache CPU work,
such as the dentry and inode caches of procfs and sysfs, as well as
the subset of radix tree nodes that track non-resident page cache.
Currently, all these
No need to use the preemption-safe lruvec state function inside the
reclaim region that has irqs disabled.
Signed-off-by: Johannes Weiner
---
mm/workingset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/workingset.c b/mm/workingset.c
index e5c70bc94077..f564aaa6b71d
The page cache and most shrinkable slab caches hold data that has been
read from disk, but there are some caches that only cache CPU work,
such as the dentry and inode caches of procfs and sysfs, as well as
the subset of radix tree nodes that track non-resident page cache.
Currently, all these
Hi Andrew,
these patches address problems we've had in our fleet with excessive
shadow radix tree nodes and proc inodes.
Patch #1 is a fix for the same-named patch already queued up in the
-mm tree. The other three patches are stand-alone.
Hi Andrew,
these patches address problems we've had in our fleet with excessive
shadow radix tree nodes and proc inodes.
Patch #1 is a fix for the same-named patch already queued up in the
-mm tree. The other three patches are stand-alone.
On Tue, Oct 09, 2018 at 02:31:27PM -0400, Doug Ledford wrote:
> On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> > This patchset introduce a new structure that will contain all the
> > infiniband device operations, the structure will be used by the
> > providers to initialize their supported
On Tue, Oct 09, 2018 at 02:31:27PM -0400, Doug Ledford wrote:
> On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> > This patchset introduce a new structure that will contain all the
> > infiniband device operations, the structure will be used by the
> > providers to initialize their supported
Hi Baolin,
On 10/09/2018 02:01 PM, Baolin Wang wrote:
> Hi Jacek and Pavel,
>
> On 5 October 2018 at 04:00, Jacek Anaszewski
> wrote:
>> Hi Baolin,
>>
>> On 10/03/2018 03:21 AM, Baolin Wang wrote:
>>> Hi Jacek,
>>>
>>> On 3 October 2018 at 04:25, Jacek Anaszewski
>>> wrote:
Hi Baolin,
Hi Baolin,
On 10/09/2018 02:01 PM, Baolin Wang wrote:
> Hi Jacek and Pavel,
>
> On 5 October 2018 at 04:00, Jacek Anaszewski
> wrote:
>> Hi Baolin,
>>
>> On 10/03/2018 03:21 AM, Baolin Wang wrote:
>>> Hi Jacek,
>>>
>>> On 3 October 2018 at 04:25, Jacek Anaszewski
>>> wrote:
Hi Baolin,
On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> This patchset introduce a new structure that will contain all the
> infiniband device operations, the structure will be used by the
> providers to initialize their supported operations. This patchset also
> includes the required changes in the
On Tue, 2018-10-09 at 19:27 +0300, Kamal Heib wrote:
> This patchset introduce a new structure that will contain all the
> infiniband device operations, the structure will be used by the
> providers to initialize their supported operations. This patchset also
> includes the required changes in the
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers publishing
> > private information such as email addresses unacceptable behaviour. Since
> > the
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers publishing
> > private information such as email addresses unacceptable behaviour. Since
> > the
[v7]
* Cleanup header file inclusions.
* Move the comments along with the flags.
* Update the commit with details for CLK_IGNORE_UNUSED.
[v6]
* Update the logic to register the lpass clocks when the device tree property
is not present.
* Add the CLK_IGNORE_UNUSED flag for the lpass
Hi Malathi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.19-rc7 next-20181009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks present on the global clock controller would be registered
with the clock framework based on the device
[v7]
* Cleanup header file inclusions.
* Move the comments along with the flags.
* Update the commit with details for CLK_IGNORE_UNUSED.
[v6]
* Update the logic to register the lpass clocks when the device tree property
is not present.
* Add the CLK_IGNORE_UNUSED flag for the lpass
Hi Malathi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.19-rc7 next-20181009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks present on the global clock controller would be registered
with the clock framework based on the device
On Tue 09 Oct 09:02 PDT 2018, Arnaud Pouliquen wrote:
> hello Bjorn,
>
> On 10/08/2018 06:23 PM, Bjorn Andersson wrote:
> > On Mon 08 Oct 06:08 PDT 2018, Arnaud Pouliquen wrote:
> >
> >> Hi Arun, Bjorn,
> >>
> >> On 10/08/2018 08:38 AM, Arun Kumar Neelakantam wrote:
> >>> Glink transport
On Tue 09 Oct 09:02 PDT 2018, Arnaud Pouliquen wrote:
> hello Bjorn,
>
> On 10/08/2018 06:23 PM, Bjorn Andersson wrote:
> > On Mon 08 Oct 06:08 PDT 2018, Arnaud Pouliquen wrote:
> >
> >> Hi Arun, Bjorn,
> >>
> >> On 10/08/2018 08:38 AM, Arun Kumar Neelakantam wrote:
> >>> Glink transport
On Thu, Jan 4, 2018 at 3:53 PM Wendy Liang wrote:
>
> Xilinx ZynqMP IPI(Inter Processor Interrupt) is a hardware block
> in ZynqMP SoC used for the communication between various processor
> systems.
>
> Signed-off-by: Wendy Liang
> ---
> .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt | 104
On Thu, Jan 4, 2018 at 3:53 PM Wendy Liang wrote:
>
> Xilinx ZynqMP IPI(Inter Processor Interrupt) is a hardware block
> in ZynqMP SoC used for the communication between various processor
> systems.
>
> Signed-off-by: Wendy Liang
> ---
> .../bindings/mailbox/xlnx,zynqmp-ipi-mailbox.txt | 104
On 10/9/2018 4:10 AM, Joel Fernandes wrote:
On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote:
On Mon, 8 Oct 2018 19:46:15 +0530
Sai Prakash Ranjan wrote:
Hi Joel,
Sorry for the long delay in updating this thread.
But I just observed one weird behaviour in ftrace-ramoops when I
On 10/9/2018 4:10 AM, Joel Fernandes wrote:
On Mon, Oct 08, 2018 at 10:36:59AM -0400, Steven Rostedt wrote:
On Mon, 8 Oct 2018 19:46:15 +0530
Sai Prakash Ranjan wrote:
Hi Joel,
Sorry for the long delay in updating this thread.
But I just observed one weird behaviour in ftrace-ramoops when I
Here is a second round of prototype registering rseq(2) TLS for each
thread (including main), and unregistering for each thread (excluding
main). "rseq" stands for Restartable Sequences.
Remaining open questions:
- How early do we want to register rseq and how late do we want to
unregister it
Here is a second round of prototype registering rseq(2) TLS for each
thread (including main), and unregistering for each thread (excluding
main). "rseq" stands for Restartable Sequences.
Remaining open questions:
- How early do we want to register rseq and how late do we want to
unregister it
From: Enrico Granata
This commit allows cros_ec_lpc to register a direct IRQ instead of relying
on the ACPI notification chain to receive MKBP events.
This change is done in the interest of allowing reduced jitter in the
communication path between the CrOS EC and the host for receiving sensor
From: Enrico Granata
This commit allows cros_ec_lpc to register a direct IRQ instead of relying
on the ACPI notification chain to receive MKBP events.
This change is done in the interest of allowing reduced jitter in the
communication path between the CrOS EC and the host for receiving sensor
On Tue, Sep 04, 2018 at 12:33:09PM -0600, Jon Derrick wrote:
> During probe, the port driver will disable error reporting and assumes
> it will be enabled later by the AER driver's pci_walk_bus() sequence.
> This may not be the case for host-bridge enabled root ports, who will
> enable first error
On Tue, Sep 04, 2018 at 12:33:09PM -0600, Jon Derrick wrote:
> During probe, the port driver will disable error reporting and assumes
> it will be enabled later by the AER driver's pci_walk_bus() sequence.
> This may not be the case for host-bridge enabled root ports, who will
> enable first error
Current implementation of cephfs fallocate isn't correct as it doesn't
really reserve the space in the cluster, which means that a subsequent
call to a write may actually fail due to lack of space. In fact, it is
currently possible to fallocate an amount space that is larger than the
free space
Current implementation of cephfs fallocate isn't correct as it doesn't
really reserve the space in the cluster, which means that a subsequent
call to a write may actually fail due to lack of space. In fact, it is
currently possible to fallocate an amount space that is larger than the
free space
Hi,
On Tue, Oct 9, 2018 at 9:12 AM Stephen Boyd wrote:
>
> Quoting Doug Anderson (2018-10-08 16:52:36)
> > Hi,
> >
> > On Mon, Oct 8, 2018 at 4:43 PM Stephen Boyd wrote:
> > > > + mas->irq = platform_get_irq(pdev, 0);
> > > > + if (mas->irq < 0) {
> > > > + ret =
Hi,
On Tue, Oct 9, 2018 at 9:12 AM Stephen Boyd wrote:
>
> Quoting Doug Anderson (2018-10-08 16:52:36)
> > Hi,
> >
> > On Mon, Oct 8, 2018 at 4:43 PM Stephen Boyd wrote:
> > > > + mas->irq = platform_get_irq(pdev, 0);
> > > > + if (mas->irq < 0) {
> > > > + ret =
IAD Register is yet readable trough the "iad" sys file.
A write to the "iad" sys file enables or disables the current
measurement, but it was not possible to get the measured value by
reading it.
Fix: %u in snprintf for unsigned values (vdd and vad)
Fix: Avoid possibles overflows (Usage of the
IAD Register is yet readable trough the "iad" sys file.
A write to the "iad" sys file enables or disables the current
measurement, but it was not possible to get the measured value by
reading it.
Fix: %u in snprintf for unsigned values (vdd and vad)
Fix: Avoid possibles overflows (Usage of the
On Tue, 2018-10-09 at 19:48 +0530, Rajneesh Bhardwaj wrote:
> Add myself and David as the new maintainers for Intel Telemetry driver
> since Souvik no longer works with Intel. David and I work on power
> management and debug related drivers which are pretty close to this one
> in terms of
On Tue, 2018-10-09 at 19:48 +0530, Rajneesh Bhardwaj wrote:
> Add myself and David as the new maintainers for Intel Telemetry driver
> since Souvik no longer works with Intel. David and I work on power
> management and debug related drivers which are pretty close to this one
> in terms of
On Tue, Oct 9, 2018 at 4:16 AM Michal Hocko wrote:
>
> On Thu 04-10-18 09:51:37, Dan Williams wrote:
> > On Thu, Oct 4, 2018 at 12:48 AM Michal Hocko wrote:
[..]
> > So the reason front-back randomization is not enough is due to the
> > in-order initial freeing of pages. At the start of that
On Tue, Oct 9, 2018 at 4:16 AM Michal Hocko wrote:
>
> On Thu 04-10-18 09:51:37, Dan Williams wrote:
> > On Thu, Oct 4, 2018 at 12:48 AM Michal Hocko wrote:
[..]
> > So the reason front-back randomization is not enough is due to the
> > in-order initial freeing of pages. At the start of that
On Tue, Oct 9, 2018 at 4:28 AM Michal Hocko wrote:
>
> On Thu 04-10-18 09:44:35, Dan Williams wrote:
> > Hi Michal,
> >
> > On Thu, Oct 4, 2018 at 12:53 AM Michal Hocko wrote:
> > >
> > > On Wed 03-10-18 19:15:18, Dan Williams wrote:
> > > > Changes since v1:
> > > > * Add support for shuffling
On Tue, Oct 9, 2018 at 4:28 AM Michal Hocko wrote:
>
> On Thu 04-10-18 09:44:35, Dan Williams wrote:
> > Hi Michal,
> >
> > On Thu, Oct 4, 2018 at 12:53 AM Michal Hocko wrote:
> > >
> > > On Wed 03-10-18 19:15:18, Dan Williams wrote:
> > > > Changes since v1:
> > > > * Add support for shuffling
On Tue, Oct 9, 2018 at 1:48 AM Jiri Kosina wrote:
>
> From: Jiri Kosina
>
> SIMPLE_DEV_PM_OPS() already implies const for the type; drop the extra
> modifier.
>
> Fixes: eb1aac4c8744f75460c34d71b0c73bebf3e8ee5c ("HID: google: add support
> tablet mode switch for Whiskers")
> Signed-off-by: Jiri
From: Nayna Jain
This patch removes the code duplication in ima_init_policy() by defining
a new function named add_rules(). The new function adds the rules to the
initial IMA policy, the custom policy or both based on the policy mask
(IMA_DEFAULT_POLICY, IMA_CUSTOM_POLICY).
Signed-off-by: Nayna
On Tue, Oct 9, 2018 at 1:48 AM Jiri Kosina wrote:
>
> From: Jiri Kosina
>
> SIMPLE_DEV_PM_OPS() already implies const for the type; drop the extra
> modifier.
>
> Fixes: eb1aac4c8744f75460c34d71b0c73bebf3e8ee5c ("HID: google: add support
> tablet mode switch for Whiskers")
> Signed-off-by: Jiri
From: Nayna Jain
This patch removes the code duplication in ima_init_policy() by defining
a new function named add_rules(). The new function adds the rules to the
initial IMA policy, the custom policy or both based on the policy mask
(IMA_DEFAULT_POLICY, IMA_CUSTOM_POLICY).
Signed-off-by: Nayna
"write-reliability" setting must be performed on all required partitions
in one command.
Introduce new command "write_reliability set_register" to allow setting
of write-reliability for all required partitions.
This command is a one-time programmable action. It cannot not be undone
by
"write-reliability" setting must be performed on all required partitions
in one command.
Introduce new command "write_reliability set_register" to allow setting
of write-reliability for all required partitions.
This command is a one-time programmable action. It cannot not be undone
by
[PATCH 1-3] just introduce further parsing and human-readable output of eMMC
5.0+ fields in the extcsd:
mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
mmc-utils: treat FIRMWARE_VERSION as binary field instead of string
mmc-utils: interpret DEVICE_VERSION when printing extcsd
[PATCH
---
mmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mmc.c b/mmc.c
index f2c714c..660b62e 100644
--- a/mmc.c
+++ b/mmc.c
@@ -26,7 +26,7 @@
#include "mmc_cmds.h"
-#define MMC_VERSION"0.1"
+#define MMC_VERSION"0.2"
#define BASIC_HELP 0
#define ADVANCED_HELP
The "write_reliability set" command is dangerous since it will only set
write-reliability on one partition per command and this command is a
one-time programmable action. This makes it impossible to set
write-reliability on multiple partitions.
Remove the command so it cannot be used in the
The "write_reliability set" command is dangerous since it will only set
write-reliability on one partition per command and this command is a
one-time programmable action. This makes it impossible to set
write-reliability on multiple partitions.
Remove the command so it cannot be used in the
[PATCH 1-3] just introduce further parsing and human-readable output of eMMC
5.0+ fields in the extcsd:
mmc-utils: interpret OPTIMAL_*_SIZE fields in extcsd
mmc-utils: treat FIRMWARE_VERSION as binary field instead of string
mmc-utils: interpret DEVICE_VERSION when printing extcsd
[PATCH
---
mmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mmc.c b/mmc.c
index f2c714c..660b62e 100644
--- a/mmc.c
+++ b/mmc.c
@@ -26,7 +26,7 @@
#include "mmc_cmds.h"
-#define MMC_VERSION"0.1"
+#define MMC_VERSION"0.2"
#define BASIC_HELP 0
#define ADVANCED_HELP
The FIRMWARE_VERSION field is 8-bytes in size and contains non-printable
characters.
Treat this field as binary and print individual byte values in hex
Signed-off-by: James Nuss
---
mmc.h | 9 -
mmc_cmds.c | 11 +--
2 files changed, 17 insertions(+), 3 deletions(-)
diff
The enhanced and extended attributes must be set on all required partitions
in a single command instead of one command per partition.
Remove the enhanced and extended attribute setting parameters from the
"gp create" and "enh_area set" commands and create new commands:
* "enh_area set_partitions"
The enhanced and extended attributes must be set on all required partitions
in a single command instead of one command per partition.
Remove the enhanced and extended attribute setting parameters from the
"gp create" and "enh_area set" commands and create new commands:
* "enh_area set_partitions"
The FIRMWARE_VERSION field is 8-bytes in size and contains non-printable
characters.
Treat this field as binary and print individual byte values in hex
Signed-off-by: James Nuss
---
mmc.h | 9 -
mmc_cmds.c | 11 +--
2 files changed, 17 insertions(+), 3 deletions(-)
diff
The DEVICE_VERSION is a 2-byte field
Print the individual byte values in hex
Signed-off-by: James Nuss
---
mmc.h | 2 ++
mmc_cmds.c | 3 +++
2 files changed, 5 insertions(+)
diff --git a/mmc.h b/mmc.h
index 86e209a..f25869e 100644
--- a/mmc.h
+++ b/mmc.h
@@ -59,6 +59,8 @@
#define
eMMC 5.0 introduced OPTIMAL_READ_SIZE, OPTIMAL_WRITE_SIZE and OPTIMAL
TRIM_UNIT_SIZE fields in the extcsd
Interpret these fields when reading out the extcsd with human-readable
results
Signed-off-by: James Nuss
---
mmc.h | 3 +++
mmc_cmds.c | 18 ++
2 files changed, 21
eMMC 5.0 introduced OPTIMAL_READ_SIZE, OPTIMAL_WRITE_SIZE and OPTIMAL
TRIM_UNIT_SIZE fields in the extcsd
Interpret these fields when reading out the extcsd with human-readable
results
Signed-off-by: James Nuss
---
mmc.h | 3 +++
mmc_cmds.c | 18 ++
2 files changed, 21
The DEVICE_VERSION is a 2-byte field
Print the individual byte values in hex
Signed-off-by: James Nuss
---
mmc.h | 2 ++
mmc_cmds.c | 3 +++
2 files changed, 5 insertions(+)
diff --git a/mmc.h b/mmc.h
index 86e209a..f25869e 100644
--- a/mmc.h
+++ b/mmc.h
@@ -59,6 +59,8 @@
#define
On 10/09/2018 11:39 AM, Lukasz Luba wrote:
> This patch add some comment related to performance impact,
> which can be really big (x3 times slower context switch).
>
> Signed-off-by: Lukasz Luba
> ---
> lib/Kconfig.debug | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
On 10/09/2018 11:39 AM, Lukasz Luba wrote:
> This patch add some comment related to performance impact,
> which can be really big (x3 times slower context switch).
>
> Signed-off-by: Lukasz Luba
> ---
> lib/Kconfig.debug | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
Hello Stephen,
On 10/8/2018 8:14 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-04 05:02:26)
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks
Hello Stephen,
On 10/8/2018 8:14 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-04 05:02:26)
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks
301 - 400 of 1434 matches
Mail list logo
