Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf

On Mon, 15 Jun 2020 14:55:52 +0200 Borislav Petkov wrote: > Can you please resend your patchset once a week like everyone else and > not flood inboxes with it? Boris, Haven't you automated your inbox yet? I have patchwork reading my INBOX and it's smart enough to understand new series, and the

Re: [PATCH v8 2/5] seq_buf: Export seq_buf_printf

ars it was a reply to a private email you sent to me. I didn't realize it was off list. Anyway: Acked-by: Steven Rostedt (VMware) -- Steve ___ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org

Re: [PATCH v7 2/5] seq_buf: Export seq_buf_printf() to external modules

On Fri, 8 May 2020 18:09:35 +0200 Borislav Petkov wrote: > On Fri, May 08, 2020 at 05:30:31PM +0530, Vaibhav Jain wrote: > > I am referring to Kernel Loadable Modules with MODULE_LICENSE("GPL") > > here. > > And what does "external" refer to? Because if it is out-of-tree, we > don't export

Re: [PATCH v18 00/19] kunit: introduce KUnit, the Linux kernel unit testing framework

On Sun, 6 Oct 2019 10:18:11 -0700 Linus Torvalds wrote: > On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o wrote: > > > > Well, one thing we *can* do is if (a) if we can create a kselftest > > branch which we know is stable and won't change, and (b) we can get > > assurances that Linus *will*

Re: [RFC v3 11/19] kunit: add Python libraries for handing KUnit config and kernel

On Tue, 11 Dec 2018 15:09:26 +0100 Petr Mladek wrote: > > We have liburcu already, which is good. The main sticking points are: > > > > - printk has started adding a lot of %pX enhancements which printf > >obviously doesn't know about. > > I wonder how big problem it is and if it is

Re: [PATCH v3 5/5] dax: add tracepoints to dax_pmd_insert_mapping()

t; shared WRITE|ALLOW_RETRY|KILLABLE|USER address 0x10505000 vm_start > 0x1020 vm_end 0x1070 pgoff 0x200 max_pgoff 0x1400 NOPAGE > > Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com> > Reviewed-by: Jan Kara <j...@suse.cz> > --- Acked-by: Steven Rostedt <r

Re: [PATCH v3 4/5] dax: add tracepoints to dax_pmd_load_hole()

RETRY|KILLABLE|USER address 0x1040 vm_start > 0x1020 vm_end 0x1060 pgoff 0x200 max_pgoff 0x1400 NOPAGE > > Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com> > Reviewed-by: Jan Kara <j...@suse.cz> > --- Acked-by: Steven Rostedt <rost...@goodmis.org&

Re: [PATCH v3 2/5] dax: add tracepoint infrastructure, PMD tracing

|KILLABLE|USER address 0x10505000 vm_start > 0x1020 vm_end 0x1070 pgoff 0x200 max_pgoff 0x1400 NOPAGE > > Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel.com> > Suggested-by: Dave Chinner <da...@fromorbit.com> > Reviewed-by: Jan Kara <j...@suse.cz> Ac

Re: [PATCH v3 1/5] tracing: add __print_flags_u64()

llowing when > compiling for i386: > > ./include/linux/pfn_t.h:13:22: warning: large integer implicitly truncated > to unsigned type [-Woverflow] > #define PFN_SG_CHAIN (1ULL << (BITS_PER_LONG_LONG - 1)) > ^ > > Signed-off-by: Ross Zwisler <ross.zwis...@linux.intel

Re: [PATCH v2 6/6] dax: add tracepoints to dax_pmd_insert_mapping()

On Thu, 1 Dec 2016 08:44:32 -0700 Ross Zwisler wrote: > Actually I think it may be ideal to stick it as the 2nd entry after 'dev'. > dev_t is: > > typedef __u32 __kernel_dev_t; > typedef __kernel_dev_tdev_t; > > So those two 32 bit values should

Re: [PATCH v2 3/6] dax: add tracepoint infrastructure, PMD tracing

On Wed, 30 Nov 2016 16:45:30 -0700 Ross Zwisler wrote: > --- /dev/null > +++ b/include/trace/events/fs_dax.h > @@ -0,0 +1,68 @@ > +#undef TRACE_SYSTEM > +#define TRACE_SYSTEM fs_dax > + > +#if !defined(_TRACE_FS_DAX_H) || defined(TRACE_HEADER_MULTI_READ) > +#define

Re: [PATCH v2 1/6] tracing: add __print_flags_u64()

On Wed, 30 Nov 2016 16:45:28 -0700 Ross Zwisler wrote: > Add __print_flags_u64() and the helper trace_print_flags_seq_u64() in the > same spirit as __print_symbolic_u64() and trace_print_symbols_seq_u64(). > These functions allow us to print symbols associated with