On 10/23/2018 11:50 AM, Kees Cook wrote:
> On Tue, Oct 23, 2018 at 9:48 AM, Casey Schaufler
> wrote:
>> On 10/12/2018 12:01 PM, Kees Cook wrote:
>>> On Friday, October 12, 2018 3:19 AM, John Johansen
>>> wrote:
It isn't perfect but it manages consistency across distros as best as
can b
The following changes since commit
5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.20
for you to fetch changes up to aea74de4b216cdacda797d54220b8ac19daa1bf7:
docs: Fix ty
On 10/12/2018 12:01 PM, Kees Cook wrote:
> On Friday, October 12, 2018 3:19 AM, John Johansen
> wrote:
>> It isn't perfect but it manages consistency across distros as best as
>> can be achieved atm.
> Yeah, this is why I'm okay with the current series: it provides as
> consistent a view as possib
On Tue, Oct 23, 2018 at 9:48 AM, Casey Schaufler wrote:
> On 10/12/2018 12:01 PM, Kees Cook wrote:
>> On Friday, October 12, 2018 3:19 AM, John Johansen
>> wrote:
>>> It isn't perfect but it manages consistency across distros as best as
>>> can be achieved atm.
>> Yeah, this is why I'm okay with
bow == backup on write
Similar to dm-snap, add the ability to take a snapshot of a device.
Unlike dm-snap, a separate volume is not required.
dm-bow can be in one of three states.
In state one, the free blocks on the device are identified by issuing
an FSTRIM to the filesystem.
In state two, an
It was found that two of the fields in the /proc//status file were
missing - CapAmb & Speculation_Store_Bypass. They are now added to the
proc.txt documentation file.
v2: Update the example as well.
Signed-off-by: Waiman Long
---
Documentation/filesystems/proc.txt | 6 +-
1 file changed, 5
Documentation for protected memory.
Topics covered:
* static memory allocation
* dynamic memory allocation
* write-rare
Signed-off-by: Igor Stoppa
CC: Jonathan Corbet
CC: Randy Dunlap
CC: Mike Rapoport
CC: linux-doc@vger.kernel.org
CC: linux-ker...@vger.kernel.org
---
Documentation/core-api/
On Tue, Oct 23, 2018 at 02:23:28PM -0700, Paul Lawrence wrote:
> It is planned to use this driver to enable restoration of a failed
> update attempt on Android devices using ext4.
Could you say a bit more about the reason for this new dm target so we
can understand better what parameters you are t
Here's the first set of patches that I'm working on for the Common
Clk Framework. Part of this patch series adds a new clk op,
pre_rate_req. This is designed to replace the clk notifier approach
that many clk drivers use right now to setup alt parents or temporary
dividers. This should allow for th
This adds documentation for the new clk op pre_rate_req.
Signed-off-by: Derek Basehore
---
Documentation/driver-api/clk.rst | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/driver-api/clk.rst b/Documentation/driver-api/clk.rst
index 593cca5058b1..917f6ac296
This makes the rockchip cpuclk use the pre_rate_req op to change to
the alt parent instead of the clk notifier. This has the benefit of
the clk not changing parents behind the back of the common clk
framework. It also changes the divider setting for the alt parent to
only divide when the alt parent
clk_calc_subtree was called at every step up the clk tree in
clk_calc_new_rates. Since it recursively calls itself for its
children, this means it would be called once on each clk for each
step above the top clk is.
This fixes this by breaking the subtree calculation into two parts.
The first part
This changes the clk_set_rate code to use lists instead of recursion.
While making this change, also add error handling for clk_set_rate.
This means that errors in the set_rate/set_parent/set_rate_and_parent
functions will not longer be ignored. When an error occurs, the clk
rates and parents are r
This adds a new clk_op, pre_rate_req. It allows clks to setup an
intermediate state when clk rates are changed. One use case for this
is when a clk needs to switch to a safe parent when its PLL ancestor
changes rates. This is needed when a PLL cannot guarantee that it will
not exceed the new rate b
From: Stephen Boyd
Enabling and preparing clocks can be written quite naturally with
recursion. We start at some point in the tree and recurse up the
tree to find the oldest parent clk that needs to be enabled or
prepared. Then we enable/prepare and return to the caller, going
back to the clk we
Hi,
On 10/23/18 2:34 PM, Igor Stoppa wrote:
> Documentation for protected memory.
>
> Topics covered:
> * static memory allocation
> * dynamic memory allocation
> * write-rare
>
> Signed-off-by: Igor Stoppa
> CC: Jonathan Corbet
> CC: Randy Dunlap
> CC: Mike Rapoport
> CC: linux-doc@vger.ker
On Tue, Oct 23, 2018 at 6:31 PM Derek Basehore wrote:
>
> This makes the rockchip cpuclk use the pre_rate_req op to change to
> the alt parent instead of the clk notifier. This has the benefit of
> the clk not changing parents behind the back of the common clk
> framework. It also changes the divi
17 matches
Mail list logo