* Mathieu Malaterre [171215 04:49]:
> Improve the DTS files by removing all the leading "0x" and zeros to fix the
> following dtc warnings:
>
> Warning (unit_address_format): Node /XXX unit name should not have leading
> "0x"
>
> and
>
> Warning (unit_address_format): Node /XXX unit name shoul
On Thu, 14 Dec 2017, Eric Biggers wrote:
> On Thu, Dec 14, 2017 at 04:34:12PM +0100, Thomas Gleixner wrote:
> > On Thu, 14 Dec 2017, Dmitry Vyukov wrote:
> > > On Thu, Dec 14, 2017 at 3:26 PM, Thomas Gleixner
> > > wrote:
> > > > On Tue, 12 Dec 2017, Greg KH wrote:
> > > >> Did this ever go anywh
* Andy Lutomirski wrote:
> On Fri, Dec 15, 2017 at 2:02 AM, Dmitry Vyukov wrote:
> > On Fri, Dec 15, 2017 at 10:58 AM, Wanpeng Li wrote:
> >> 2017-12-15 17:51 GMT+08:00 David Hildenbrand :
> >>>
> int main()
> {
> int fd = open("/dev/kvm", 0x80102ul);
> int vm = ioctl(f
This patch adds the entry point for CoreSight trace decoding, serving
as a jumping board for furhter expansions.
Co-authored-by: Tor Jeremiassen
Signed-off-by: Mathieu Poirier
---
tools/perf/util/Build | 5 ++
tools/perf/util/auxtrace.c | 2 +
tools/perf/util/cs-etm.c | 213 +
This patchset adds support for per-thread CoreSight trace decoding from the
"perf report" interface. It is largely modelled on what has been done for
intelPT traces and currently targets the ETMv4 architecture. Support for
cpu-wide scenarios and ETMv3/PTMv1.1 will follow shortly.
The trace deco
This patch adds the required interface to the openCSD library to support
dumping CoreSight trace packet using the "report --dump" command. The
information conveyed is related to the type of packets gathered by a
trace session rather than full decoding.
Co-authored-by: Tor Jeremiassen
Signed-off-
This patch adds functions to communicate with the openCSD trace decoder,
more specifically to access program memory, fetch trace packets and
reset the decoder.
Co-authored-by: Tor Jeremiassen
Signed-off-by: Mathieu Poirier
---
tools/perf/util/cs-etm-decoder/cs-etm-decoder.c | 60 +++
Once decoded from trace packets information on trace range needs
to be communicated to the perf synthesis infrastructure so that it
is available to the perf tools built-in rendering tools and scripts.
Co-authored-by: Tor Jeremiassen
Signed-off-by: Mathieu Poirier
---
tools/perf/util/cs-etm.c |
This patch adds support for complete packet decoding, allowing
traces collected during a trace session to be decoder from the
"report" infrastructure.
Co-authored-by: Tor Jeremiassen
Signed-off-by: Mathieu Poirier
---
tools/perf/util/cs-etm.c | 166 +-
From: Tor Jeremiassen
Adding maintainers for Coresight trace decoding via perf tools.
Signed-off-by: Tor Jeremiassen
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 82ad0eabce4f..865847aa84bd 100644
--- a/MAINTAINERS
+++ b/M
Add functionatlity to setup trace queues so that traces associated with
CoreSight auxtrace events found in the perf.data file can be classified
properly. The decoder and memory callback associated with each queue are
then used to decode the traces that have been assigned to that queue.
Co-authore
Adding functionality to create a CoreSight trace decoder capable
of decoding trace data pushed by a client application.
Co-authored-by: Tor Jeremiassen
Signed-off-by: Mathieu Poirier
---
tools/perf/util/cs-etm-decoder/cs-etm-decoder.c | 119
1 file changed, 119 insertio
From: Tor Jeremiassen
The auxtrace_info section contains metadata that describes the number of
trace capable CPUs, their ETM version and trace configuration, including
trace id values. This information is required by the trace decoder in
order to properly decode the compressed trace packets. This
The Open CoreSight Decoding Library (openCSD) is a free and open
library to decode traces collected by the CoreSight hardware
infrastructure.
This patch adds the required mechanic to recognise the presence
of the openCSD library on a system and set up miscellaneous flags
to be used in the compilat
[Folks, please review and comment; if no objections show up, into -next it goes]
The following primitives are defined in linux/bitfield.h:
* u32 le32_get_bits(__le32 val, u32 field) extracts the contents of the
bitfield specified by @field in little-endian 32bit object @val and
converts it to
From: Aleksandar Markovic
v10->v11:
- rebased to the latest code
v9->v10:
- added comment in code segment related to measuring frequency
- rebased to the latest code
v8->v9:
- cleaned up PIC initialization details
- added missing '\n' to pr_err() invocations
- removed
- On Dec 15, 2017, at 10:05 AM, Chris Lameter c...@linux.com wrote:
> On Thu, 14 Dec 2017, Peter Zijlstra wrote:
>
>> > But my company has extensive user space code that maintains a lot of
>> > counters and does other tricks to get full performance out of the
>> > hardware. Such a mechanism w
From: Miodrag Dinic
Add documentation for DT binding of Goldfish PIC driver. The compatible
string used by OS for binding the driver is "google,goldfish-pic".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
Acked-by: Rob Herring
---
.../interrupt-
From: Miodrag Dinic
Add device driver for a virtual programmable interrupt controller
The virtual PIC is designed as a device tree-based interrupt controller.
The compatible string used by OS for binding the driver is
"google,goldfish-pic".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Fe
From: Miodrag Dinic
Provide amendments to the MIPS generic platform framework so that
the new generic-based board Ranchu can be chosen to be built.
The Ranchu board is intended to be used by Android emulator. The name
"Ranchu" originates from Android development community. "Goldfish" and
"Ranchu
On 15 December 2017 at 16:19, Matt Fleming wrote:
> On Sat, 09 Dec, at 04:52:52PM, Vincent Legoll wrote:
>> No need to get into the submenu to disable all related
>> config entries.
>>
>> This makes it easier to disable all EFI config options
>> without entering the submenu. It will also enable on
On Fri, Dec 15, 2017 at 12:10:47PM +0100, Takashi Iwai wrote:
> > - struct cyclecounter *cc = &azx_dev->tc.cc;
> > - cc->read = azx_cc_read;
> > - cc->mask = CLOCKSOURCE_MASK(32);
> > - cc->mult = 125; /* saturation after 195 years */
> > - cc->shift = 0;
I want to get away from this
From: Aleksandar Markovic
This series is based on two patches from the series submitted some
time ago (30 Aug 2016):
https://www.linux-mips.org/archives/linux-mips/2016-08/msg00456.html
Both patches deal with MIPS Cluster Power Controller (CPC) support.
More specifically, they add device tree r
From: Paul Burton
Document a binding for the MIPS Cluster Power Controller (CPC) which
simply allows the device tree to specify where the CPC registers should
be mapped.
Signed-off-by: Paul Burton
Signed-off-by: Aleksandar Markovic
---
Documentation/devicetree/bindings/misc/mti,mips-cpc.txt |
If waking from an idle CPU due to an interrupt then it's possible that
the waker task will be pulled to wake on the current CPU. Unfortunately,
depending on the type of interrupt and IRQ configuration, there may not
be a strong relationship between the CPU an interrupt was delivered on
and the CPU
From: Paul Burton
Reading mips_cpc_base value from the DT allows each platform
to define it according to its needs. This is especially
convenient for MIPS_GENERIC kernel where this kind of information
should be determined in runtime.
Use mti,mips-cpc compatible string with just a reg property to
From: Miodrag Dinic
Add a new kernel parameter to override the default behavior related
to the decision whether to set up stack as non-executable in function
mips_elf_read_implies_exec().
The new parameter is used to control non executable stack and heap,
regardless of PT_GNU_STACK entry or CPU
On Fri, Dec 15, 2017 at 6:48 AM, Sven Eckelmann
wrote:
> On Freitag, 15. Dezember 2017 11:32:05 CET Sven Eckelmann wrote:
>> On Mittwoch, 6. Dezember 2017 11:58:14 CET Willem de Bruijn wrote:
>> [...]
>> > >> > ---
>> > >> > MAINTAINERS| 2 +-
>> > >> > inc
Hi,
According to the discussion in the mail thread
https://patchwork.kernel.org/patch/10099243/,
tcp_set_state tracepoint is renamed to sock_set_state tracepoint and is moved
to include/trace/events/sock.h.
Using this new tracepoint to trace TCP/DCCP/SCTP state transition.
v1-v2: Steven's patch
With changes in inet_ files, DCCP state transitions are traced with
sock_set_state tracepoint.
Signed-off-by: Yafang Shao
---
net/dccp/proto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dccp/proto.c b/net/dccp/proto.c
index 9d43c1f..2874faf 100644
--- a/net/dccp/prot
From: "Steven Rostedt (VMware)"
The TCP trace events (specifically tcp_set_state), maps emums to symbol
names via __print_symbolic(). But this only works for reading trace events
from the tracefs trace files. If perf or trace-cmd were to record these
events, the event format file does not convert
With changes in inet_ files, SCTP state transitions are traced with
sockt_set_state tracepoint.
Signed-off-by: Yafang Shao
---
net/sctp/endpointola.c | 2 +-
net/sctp/sm_sideeffect.c | 4 ++--
net/sctp/socket.c| 12 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff
As sk_state is a common field for struct sock, so the state
transition should not be a TCP specific feature.
So I rename tcp_set_state tracepoint to sock_set_state tracepoint with
some minor changes and move it into file trace/events/sock.h.
Two helpers are introduced to trace sk_state transition
Fix the following static checker warnings:
The patch c6688ef9f297: "usbip: fix stub_rx: harden CMD_SUBMIT path
to handle malicious input" from Dec 7, 2017, leads to the following
static checker warning:
drivers/usb/usbip/stub_rx.c:346 get_pipe()
warn: impossible condition
'(pdu->u.cmd_sub
On Fri, 2017-12-15 at 14:48 +0200, Adrian Hunter wrote:
> Some Cherry Trail boards have a dependency between the SDHCI host
> controller used for SD cards and an external PMIC accessed via I2C.
> Add a
> device link between the SDHCI host controller (consumer) and the I2C
> adapter (supplier).
>
>
Improve the DTS files using lower case to fix the following dtc warnings:
Warning (simple_bus_reg): Node /XXX@ simple-bus unit address format
error, expected ""
Converted using the following command:
find . -type f \( -iname *.dts -o -iname *.dtsi \) -exec sed -i -e
"s/@\([0-9a-fA-FxX\.;:#]+\)
The most important one is the bfa fix because it's easy to oops the
kernel with this driver (this includes the commit that corrects the
compiler warning in the original), a regression in the new timespec
conversion in aacraid and a regression in the Fibre Channel ELS
handling patch. The other thre
On Mon, Dec 11, 2017 at 03:10:22PM -0800, Randy Dunlap wrote:
> > +The XArray does not support storing :c:func:`IS_ERR` pointers; some
> > +conflict with data values and others conflict with entries the XArray
> > +uses for its own purposes. If you need to store special values which
> > +cannot be
On Fri, 15 Dec 2017 17:51:25 +0100,
Richard Cochran wrote:
>
> On Fri, Dec 15, 2017 at 12:10:47PM +0100, Takashi Iwai wrote:
>
> > > - struct cyclecounter *cc = &azx_dev->tc.cc;
>
> > > - cc->read = azx_cc_read;
> > > - cc->mask = CLOCKSOURCE_MASK(32);
>
> > > - cc->mult = 125; /* saturation af
On 12/14/17 11:39 PM, Peter Zijlstra wrote:
On Thu, Dec 14, 2017 at 07:16:00PM -0800, Alexei Starovoitov wrote:
On 12/14/17 12:49 PM, Peter Zijlstra wrote:
On Thu, Dec 14, 2017 at 12:20:41PM -0800, Teng Qin wrote:
This set of commits attempts to improve three scheduler related
Tracepoints: sch
On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote:
> Hi Dave,
>
> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote:
> > On Thu, Dec 14, 2017 at 07:08:27PM +0100, Geert Uytterhoeven wrote:
> >> On Thu, Dec 14, 2017 at 4:24 PM, Dave P Martin wrote:
[...]
> >> > Good work on t
On Fri, 2017-12-15 at 17:48 +0100, Aleksandar Markovic wrote:
> Checkpatch script outputs a small number of warnings if applied to
> this series. We did not correct the code, since we think the code is
> correct for those particular cases of checkpatch warnings.
What are those warnings? I don't s
On Fri, 15 Dec 2017, Mathieu Desnoyers wrote:
> Another aspect that worries me is applications using the gs segment selector
> for other purposes. Suddenly reserving the gs segment selector for use by a
> library like glibc may lead to incompatibilities with applications already
> using it.
fs/gs
Improve the DTS files by removing all the leading "0x" and zeros to fix the
following dtc warnings:
Warning (unit_address_format): Node /XXX unit name should not have leading "0x"
and
Warning (unit_address_format): Node /XXX unit name should not have leading 0s
Converted using the following com
On Tue, Dec 12, 2017 at 03:14:04PM -0600, Bjorn Helgaas wrote:
> [+cc Lorenzo]
>
> On Tue, Dec 12, 2017 at 03:53:28PM -0500, Jim Quinlan wrote:
> > On Tue, Dec 5, 2017 at 3:59 PM, Bjorn Helgaas wrote:
> > > On Tue, Nov 14, 2017 at 05:12:05PM -0500, Jim Quinlan wrote:
> > >> From: Florian Fainelli
On 12/15/2017 08:30 AM, Bruno Wolff III wrote:
On Fri, Dec 15, 2017 at 22:02:20 +0800,
weiping zhang wrote:
Yes, please help reproduce this issue include my debug patch. Reproduce means
we can see WARN_ON in device_add_disk caused by failure of bdi_register_owner.
I'm not sure why yet, but
On Freitag, 15. Dezember 2017 11:57:55 CET Willem de Bruijn wrote:
> > No, this is also bad because batman_adv.h is MIT license and packet.h is
> > GPL-2. So what other name would you suggest for packet.h?
> > batman_adv_packet.h?
>
> Sure, that sounds great. Thanks.
Really? Isn't include/uapi/l
On 15/12/17 16:17, Lorenzo Pieralisi wrote:
> [+Marc]
>
> On Thu, Dec 14, 2017 at 10:21:23AM +0800, cao@windriver.com wrote:
>> From: Zou Cao
>>
>> When PCIE host setup, 32 MSI irq descriptions are created, but its
>> msi_desc is NULL, msi_desc is bound in MSI irq requested by PCI device,
>>
arc_emac_rx() has some issues found by code review.
In case netdev_alloc_skb_ip_align() or dma_map_single() failure
rx fifo entry will not be returned to EMAC.
In case dma_map_single() failure previously allocated skb became
lost to driver. At the same time address of newly allocated skb
will not
HI Mathieu,
On Fri, Dec 15, 2017 at 3:13 PM, Mathieu Malaterre wrote:
> diff --git a/arch/arm/boot/dts/imx6q-display5.dtsi
> b/arch/arm/boot/dts/imx6q-display5.dtsi
> index 4084de43d4d9..09085fde3341 100644
> --- a/arch/arm/boot/dts/imx6q-display5.dtsi
> +++ b/arch/arm/boot/dts/imx6q-display5.d
On Thu, 14 Dec 2017 16:13:52 +0100
Michal Suchanek wrote:
> @@ -2312,7 +2328,8 @@ static int cdrom_ioctl_closetray(struct
> cdrom_device_info *cdi)
> if (!CDROM_CAN(CDC_CLOSE_TRAY))
> return -ENOSYS;
> - return cdi->ops->tray_move(cdi, 0);
> +
> + return tray_close(cd
On Fri, Dec 15, 2017 at 12:02:01AM -0800, syzbot wrote:
> Call Trace:
> __cache_free mm/slab.c:3494 [inline]
> kfree+0x1a3/0x250 mm/slab.c:3806
> blkcipher_walk_done+0x72b/0xde0 crypto/blkcipher.c:139
> encrypt+0x20e/0x540 arch/x86/crypto/salsa20_glue.c:79
> skcipher_crypt_blkcipher crypto/skc
Pavel
On 12/15/2017 03:09 AM, Pavel Machek wrote:
> Hi!
>
>> @@ -35,6 +37,7 @@ led-controller@2d {
>> led@0 {
>> reg = <0>;
>> label = "white:display_cluster";
>> +linux,default-trigger = "backlight";
>> };
>> }
>
> What is "display_cluster"? Is i
Without Rockchip IO domain support the internal level shifters will
be misconfigured if used with other voltage domains then the default.
Signed-off-by: Klaus Goger
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/
On Fri, Dec 15, 2017 at 12:18 PM, Sven Eckelmann
wrote:
> On Freitag, 15. Dezember 2017 11:57:55 CET Willem de Bruijn wrote:
>> > No, this is also bad because batman_adv.h is MIT license and packet.h is
>> > GPL-2. So what other name would you suggest for packet.h?
>> > batman_adv_packet.h?
>>
>>
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/add-VLAN-support-to-DSA-MT7530/20171215-214450
reproduce:
# apt-get install sparse
make ARCH=x86_64
Hello,
>> This looks fine to me. Ard?
>
> Doesn't this break existing configs?
Would adding a "default yes" on the new menuconfig be OK.
If yes, I'd respin it for a v2
--
Vincent Legoll
On 15/12/2017 16:55, Juergen Gross wrote:
> I'm fine with the general idea.
>
> I'm wondering whether you really want to require CONFIG_XEN for the
> KVM case, though.
>
> Wouldn't it be better to rename arch/x86/xen/enlighten_pvh.c to
> arch/x86/pvh.c and arch/x86/xen/xen-pvh.S to arch/x86/pvh-h
On Sat, Dec 16, 2017 at 12:28:42AM +0900, Masahiro Yamada wrote:
> Commit 1c199f2878f6 ("kbuild: document recursive dependency limitation
> / resolution") probably intended to show a hint along with "recursive
> dependency detected!" error, but it missed to add {...} guard, and the
> hint is displa
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
> On Behalf Of Gabriel C
> Sent: Sunday, December 10, 2017 4:44 AM
> To: Pavel Machek ; kernel list
> Cc: Kirsher, Jeffrey T ; intel-wired-
> l...@lists.osuosl.org; net...@vger.kernel.org
> Subj
Hi,
On Fri, Dec 15, 2017 at 3:44 AM, Klaus Goger
wrote:
> This patch series replaces all the license text in rockchip devicetree
> files text with a proper SPDX-License-Identifier.
> It follows the guidelines submitted[1] by Thomas Gleixner that are not
> yet merged.
>
> These series also fixes t
On Sat, Dec 16, 2017 at 12:38:02AM +0900, Masahiro Yamada wrote:
> No more users of this keyword. Drop it according to the notice by
> commit 6341e62b212a ("kconfig: use bool instead of boolean for type
> definition attributes").
>
> Signed-off-by: Masahiro Yamada
Provided you get 0-day test it
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf Of
> Keller, Jacob E
> Sent: Friday, December 15, 2017 9:29 AM
> To: Gabriel C ; Pavel Machek ; kernel list
>
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org
> Subject: Re: [In
I'm not in fact the maintainer covering this file..
On Fri, Dec 15, 2017 at 04:36:25PM +0100, Thomas Richter wrote:
> Commit ad67b74d2469 ("printk: hash addresses printed with %p")
> changed %p to hash pointers in order to avoid leaking
> kernel addresses.
>
> This breaks the tool perf probe.
>
On Thu, Dec 14, 2017 at 4:21 PM, Bjorn Helgaas wrote:
> [+cc Rajat, Keith, linux-kernel]
>
> On Thu, Dec 14, 2017 at 07:47:01PM +0100, Maik Broemme wrote:
>> I have a Samsung 960 PRO NVMe SSD (Non-Volatile memory controller:
>> Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961). It
>> wor
From: Markus Elfring
Date: Fri, 15 Dec 2017 18:29:49 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/pwm/pwm-puv3.c | 4 +---
1 file changed, 1 insertion(+), 3 del
i2c_new_dummy is typically called from the probe function of the
driver for the primary i2c client. It requires calls to
i2c_unregister_device in the error path of the probe function and
in the remove function.
This can be simplified by introducing a device-managed version.
Make at24 driver the fi
On Fri, Dec 15, 2017 at 04:56:30PM +0200, Jarkko Sakkinen wrote:
> On Thu, Dec 14, 2017 at 12:10:52PM -0700, Jason Gunthorpe wrote:
> > On Thu, Dec 14, 2017 at 08:08:58PM +0100, Javier Martinez Canillas wrote:
> >
> > > Although probably reverting the offending commits is the right thing to do
> >
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url:
https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/add-VLAN-support-to-DSA-MT7530/20171215-214450
config: x86_64-randconfig-g0-12151942 (attached as .config)
compiler
On Fri, Dec 15, 2017 at 10:21:24AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.88 release.
> There are 64 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On 12/15/2017 02:21 AM, Juan Zea wrote:
> usbip bind writes commands followed by random string when writing to
> match_busid attribute in sysfs, caused by using full variable size
> instead of string length.
>
> Signed-off-by: Juan Zea
> ---
> tools/usb/usbip/src/utils.c | 9 ++---
> 1 file
On Fri, Dec 15, 2017 at 10:43:58AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.106 release.
> There are 105 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On Fri, Dec 15, 2017 at 10:51:43AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.70 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Fri, 15 Dec 2017 18:31:56 +0100
Peter Zijlstra wrote:
> > --- a/kernel/trace/trace_uprobe.c
> > +++ b/kernel/trace/trace_uprobe.c
> > @@ -608,7 +608,7 @@ static int probes_seq_show(struct seq_file *m, void *v)
> >
> > /* Don't print "0x (null)" when offset is 0 */
> > if (tu->offset
On Fri, Dec 15, 2017 at 10:51:37AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.7 release.
> There are 52 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Hi,
On 12/13/2017 12:22 PM, Lorenzo Pieralisi wrote:
Nit: remove the period in $SUBJECT and capitalize with a coherent
policy for the patches touching the same code.
Ok, thanks.
On Fri, Dec 01, 2017 at 04:23:29PM -0600, Jeremy Linton wrote:
Propagate the topology information from the PPTT
On Fri, Dec 15, 2017 at 09:18:56 -0800,
Laura Abbott wrote:
You can see the trees Fedora produces at
https://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git
which includes the configs (you want to look at the ones withtout - debug)
Thanks. I found it a little while ago and am alr
Your Subject line here is incomplete, "replace tcp_set_state
tracepoint with" what?
Currently i2c_new_device and i2c_new_dummy return just NULL in error
case although they have more error details internally. Therefore move
the functionality into new functions returning detailed errors and
add wrappers for compatibilty with the current API.
This allows to use these functions with
Make use of recently introduced device-managed version of
i2c_new_dummy to simplify the code.
Signed-off-by: Heiner Kallweit
Reviewed-by: Bartosz Golaszewski
---
v2:
- small improvements regarding code readability
v3:
- no changes
v4:
- no changes
---
drivers/misc/eeprom/at24.c | 31 +++
i2c_new_dummy is typically called from the probe function of the
driver for the primary i2c client. It requires calls to
i2c_unregister_device in the error path of the probe function and
in the remove function.
This can be simplified by introducing a device-managed version.
Note the changed error
usbip driver is leaking socket pointer address in messages. Remove
the messages that aren't useful and print sockfd in the ones that
are useful for debugging.
Signed-off-by: Shuah Khan
---
drivers/usb/usbip/stub_dev.c | 3 +--
drivers/usb/usbip/usbip_common.c | 16 +---
drivers/
2017-12-16 1:43 GMT+08:00 David Miller :
>
> Your Subject line here is incomplete, "replace tcp_set_state
> tracepoint with" what?
Oh Sorry.
The subject should be
"replace tcp_set_state tracepoint with sock_set_state tracepoint"
Thanks
Yafang
From: Yafang Shao
Date: Sat, 16 Dec 2017 01:50:12 +0800
> 2017-12-16 1:43 GMT+08:00 David Miller :
>>
>> Your Subject line here is incomplete, "replace tcp_set_state
>> tracepoint with" what?
>
> Oh Sorry.
>
> The subject should be
>
> "replace tcp_set_state tracepoint with sock_set_state trac
Am 09.12.2017 01:34, schrieb Colin King:
> From: Colin Ian King
>
> The check for secs being less than zero is redundant for two reasons.
> Firstly, secs is unsigned so the check is always going to be false.
> Secondly, if secs was signed the proceeding calculation of secs is
> never going to b
From: "Steven Rostedt (VMware)"
The TCP trace events (specifically tcp_set_state), maps emums to symbol
names via __print_symbolic(). But this only works for reading trace events
from the tracefs trace files. If perf or trace-cmd were to record these
events, the event format file does not convert
Hi,
According to the discussion in the mail thread
https://patchwork.kernel.org/patch/10099243/,
tcp_set_state tracepoint is renamed to sock_set_state tracepoint and is moved
to include/trace/events/sock.h.
Using this new tracepoint to trace TCP/DCCP/SCTP state transition.
v1->v2: Steven's patch
As sk_state is a common field for struct sock, so the state
transition should not be a TCP specific feature.
So I rename tcp_set_state tracepoint to sock_set_state tracepoint with
some minor changes and move it into file trace/events/sock.h.
Two helpers are introduced to trace sk_state transition
With changes in inet_ files, DCCP state transitions are traced with
sock_set_state tracepoint.
Signed-off-by: Yafang Shao
---
net/dccp/proto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dccp/proto.c b/net/dccp/proto.c
index 9d43c1f..2874faf 100644
--- a/net/dccp/prot
With changes in inet_ files, SCTP state transitions are traced with
sockt_set_state tracepoint.
Signed-off-by: Yafang Shao
---
net/sctp/endpointola.c | 2 +-
net/sctp/sm_sideeffect.c | 4 ++--
net/sctp/socket.c| 12 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff
From: Kunihiko Hayashi
Date: Thu, 14 Dec 2017 19:05:10 +0900
> +static void ave_desc_write(struct net_device *ndev, enum desc_id id,
> +int entry, int offset, u32 val)
> +{
> + struct ave_private *priv = netdev_priv(ndev);
> + u32 addr = (id == AVE_DESCID_TX) ? pri
On 12/15/17 4:51 AM, Arnd Bergmann wrote:
When the down_read_trylock() fails, 'vma' has not been initialized
yet, which gcc now warns about:
mm/khugepaged.c: In function 'khugepaged':
mm/khugepaged.c:1659:25: error: 'vma' may be used uninitialized in this
function [-Werror=maybe-uninitialized
From: Markus Elfring
Date: Fri, 15 Dec 2017 18:55:11 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/pwm/pwm-atmel-tcb.c | 1 -
1 file changed, 1 deletion(-)
diff
> From: Joe Perches [j...@perches.com]
> Sent: Friday, December 15, 2017 6:12 PM
>
> On Fri, 2017-12-15 at 17:48 +0100, Aleksandar Markovic wrote:
> > Checkpatch script outputs a small number of warnings if applied to
> > this series. We did not correct the code, since we think the code is
> > cor
On 11/22/2017 05:29 AM, Miroslav Benes wrote:
> If a task sleeps in a set of patched functions uninterruptedly, it could
> block the whole transition indefinitely. Thus it may be useful to clear
> its TIF_PATCH_PENDING to allow the process to finish.
>
> Admin can do that now by writing to force
We want to be able to configure hwmod sysc data from ti-sysc driver using
platform data callbacks. So let's make struct omap_hwmod_sysc_fields into
struct sysc_data and have it available for both ti-sysc driver and hwmod
code.
Note that we can make it use s8 instead of u8 as the hwmod code uses th
Hi all,
Here are patches for review to update ti-sysc binding and driver to
get interconnect target module capabilities from device tree.
After this series I'll be posting another series to dynamically
allocate struct omap_hwmod_class_sysconfig based on device tree
data instead of the current pla
The ti-sysc binding does not yet describe the capabilities of the
interconnect target module. So to make the ti-sysc binding usable
for configuring the interconnect target module, we need to add few
more properties:
1. To detect between omap2 and omap4 timers, let's add compatibles
for them for
Let's configure few module quirks via device tree using the
properties for "ti,no-idle-on-init", "ti,no-reset-on-init"
and "ti,sysc-delay-us".
Let's also reorder the probe a bit so we have pdata available
earlier, and move the PM runtime calls to sysc_init_module()
from sysc_read_revision().
Sign
We can easily detect i2c based on it's non-standard module registers that
consist of two 32-bit registers accessed in 16-bit mode.
So far we don't have other 16-bit modules, so there's currently no need
to add a custom property for 16-bit register access.
Signed-off-by: Tony Lindgren
---
driver
701 - 800 of 1178 matches
Mail list logo
