On 2/13/19 8:32 PM, Andrew Lunn wrote:
>>> +For information describing the SFP cage in DT, please see the binding
>>> +documentation in the kernel source tree
>>> +``Documentation/devicetree/bindings/net/sff,sfp.txt``
>> oh, so SFP means "Small Form-factor Pluggable".
>>
>> I see that this source f
> > +For information describing the SFP cage in DT, please see the binding
> > +documentation in the kernel source tree
> > +``Documentation/devicetree/bindings/net/sff,sfp.txt``
> oh, so SFP means "Small Form-factor Pluggable".
>
> I see that this source file:
> ./drivers/net/ethernet/intel/i40e/
On 2/5/19 7:58 AM, Russell King wrote:
> Add some phylink documentation to the networking book detailing how
> to convert network drivers from phylib to phylink.
>
> Signed-off-by: Russell King
> ---
> Version 2 adds the "Modes of operation" section, as it appears mvpp2 is
> non-conformant (which
Commit 06300b21f4c7 ("kbuild: support building individual files for
external modules") introduced the '/' target. It works only for
external modules to build all .o files, but skip the modpost stage.
However, 'make /' looks a bit weird to me. 'make ./' is more sensible
if you want to build all obj
On Wed, Feb 13, 2019 at 7:47 PM Dave Chinner wrote:
>
> On Wed, Feb 13, 2019 at 12:35:16PM -0600, Vijay Chidambaram wrote:
> > On Wed, Feb 13, 2019 at 12:22 PM Amir Goldstein wrote:
> > > On Wed, Feb 13, 2019 at 7:06 PM Jayashree Mohan
> > > wrote:
> > AFAIK, any file system which persists thin
On Wed, Feb 13, 2019 at 12:35:16PM -0600, Vijay Chidambaram wrote:
> On Wed, Feb 13, 2019 at 12:22 PM Amir Goldstein wrote:
> > On Wed, Feb 13, 2019 at 7:06 PM Jayashree Mohan wrote:
> AFAIK, any file system which persists things out of order to increase
> performance does not provide strictly or
This slightly optimizes the kernel/configs.c build.
bin2c is not very efficient because it converts a data file into a
huge array to embed it into a *.c file.
Instead, we can use the .incbin directive.
Also, this simplifies the code; Makefile is cleaner, and the way to
get the offset/size of the
On 2/11/19 9:35 AM, Joel Fernandes (Google) wrote:
Introduce in-kernel headers and other artifacts which are made available
as an archive through proc (/proc/kheaders.txz file). This archive makes
it possible to build kernel modules, run eBPF programs, and other
tracing programs that need to ex
On Wed, Feb 13, 2019 at 9:43 AM Dave Martin wrote:
>
> On Wed, Feb 13, 2019 at 04:42:11PM +, Kevin Brodsky wrote:
> > (+Cc other people with MTE experience: Branislav, Ruben)
>
> [...]
>
> > >I'm wondering whether we can piggy-back on existing concepts.
> > >
> > >We could say that recolouring
On Tue, Feb 12, 2019 at 2:54 PM Kees Cook wrote:
>
> On Wed, Jan 23, 2019 at 4:06 AM liaoweixiong
> wrote:
> >
> > Why should we need pstore_block?
> > 1. Most embedded intelligent equipment have no persistent ram, which
> > increases costs. We perfer to cheaper solutions, like block devices.
> >
On Wed, Feb 13, 2019 at 7:51 AM liaoweixiong
wrote:
>
>
> On 2019-01-31 00:07, Rob Herring wrote:> On Wed, Jan 23, 2019 at
> 08:05:13PM +0800, liaoweixiong wrote:
> >> Create DT binding document for blkoops.
> >>
> >> Signed-off-by: liaoweixiong
> >> ---
> >> .../devicetree/bindings/pstore-block
On Wed, Feb 13, 2019 at 8:35 PM Vijay Chidambaram wrote:
>
> On Wed, Feb 13, 2019 at 12:22 PM Amir Goldstein wrote:
> >
> > On Wed, Feb 13, 2019 at 7:06 PM Jayashree Mohan wrote:
> > >
> > > Hi Amir!
> > >
> > > Thanks for putting across your thoughts on this. Your suggestions
> > > definitely m
On Wed, Feb 13, 2019 at 12:22 PM Amir Goldstein wrote:
>
> On Wed, Feb 13, 2019 at 7:06 PM Jayashree Mohan wrote:
> >
> > Hi Amir!
> >
> > Thanks for putting across your thoughts on this. Your suggestions
> > definitely make sense, and we'll compile these information and submit
> > a patch for re
On Wed, Feb 13, 2019 at 7:06 PM Jayashree Mohan wrote:
>
> Hi Amir!
>
> Thanks for putting across your thoughts on this. Your suggestions
> definitely make sense, and we'll compile these information and submit
> a patch for review.
>
> When it comes to strictly ordered metadata consistency, to the
On Wed, Feb 13, 2019 at 04:42:11PM +, Kevin Brodsky wrote:
> (+Cc other people with MTE experience: Branislav, Ruben)
[...]
> >I'm wondering whether we can piggy-back on existing concepts.
> >
> >We could say that recolouring memory is safe when and only when
> >unmapping of the page or remov
Hi Amir!
Thanks for putting across your thoughts on this. Your suggestions
definitely make sense, and we'll compile these information and submit
a patch for review.
When it comes to strictly ordered metadata consistency, to the best of
our knowledge only xfs claims to provide it explicitly. In ex
(+Cc other people with MTE experience: Branislav, Ruben)
On 13/02/2019 14:58, Dave Martin wrote:
On Tue, Feb 12, 2019 at 06:02:24PM +, Catalin Marinas wrote:
On Mon, Feb 11, 2019 at 12:32:55PM -0800, Evgenii Stepanov wrote:
On Mon, Feb 11, 2019 at 9:28 AM Kevin Brodsky wrote:
On 19/12/20
On 06.02.2019 00:49, Thierry Reding wrote:
> On Sat, Jan 05, 2019 at 10:05:22PM +0100, Uwe Kleine-König wrote:
>> Hello,
>>
>> On Thu, Jan 03, 2019 at 01:29:44PM +, claudiu.bez...@microchip.com wrote:
>>> From: Claudiu Beznea
>>>
>>> Add basic PWM modes: normal and complementary. These mode
On 06.02.2019 10:24, Uwe Kleine-König wrote:
> Hello Thierry,
>
> On Wed, Feb 06, 2019 at 12:01:26AM +0100, Thierry Reding wrote:
>> On Mon, Jan 07, 2019 at 11:10:40PM +0100, Uwe Kleine-König wrote:
>>> On Mon, Jan 07, 2019 at 09:30:55AM +, claudiu.bez...@microchip.com
>>> wrote:
On 05
On Tue, Feb 12, 2019 at 06:02:24PM +, Catalin Marinas wrote:
> On Mon, Feb 11, 2019 at 12:32:55PM -0800, Evgenii Stepanov wrote:
> > On Mon, Feb 11, 2019 at 9:28 AM Kevin Brodsky wrote:
> > > On 19/12/2018 12:52, Dave Martin wrote:
[...]
> > > > * A single C object should be accessed using
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/blkoops.c| 11 ++
fs/pstore/blkzone.c| 254 +
include/linux/pstore_blk.h | 1 +
3 files changed, 244 insertions(+), 22 d
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 227 +
MAINTAINERS| 1
blkoops is a sample for pstore/blk. It can only record oops, excluding
panics as no read/write apis for panic registered. It support settings
on Kconfg/device tree/module parameters. It can record oops log even
power failure if "PSTORE_BLKOOPS_PART_PATH" on Kconfig or
"partition-path" on dts or "pa
pstore_blk is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_blk?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fact, there is already a sample
Create DT binding document for blkoops.
Signed-off-by: liaoweixiong
---
.../devicetree/bindings/pstore/blkoops.txt | 29 ++
MAINTAINERS| 1 +
2 files changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindin
Why should we need pstore_block?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have b
On 2019-01-31 00:07, Rob Herring wrote:> On Wed, Jan 23, 2019 at
08:05:13PM +0800, liaoweixiong wrote:
>> Create DT binding document for blkoops.
>>
>> Signed-off-by: liaoweixiong
>> ---
>> .../devicetree/bindings/pstore-block/blkoops.txt | 32
>> ++
>
> /bindings/pstore/
27 matches
Mail list logo
