On Fri, Apr 21, 2017 at 04:58:02PM +0200, Peter Zijlstra wrote:
> Commit:
>
> 2bacec8c318c ("sched: touch softlockup watchdog after idling")
>
> introduced the touch_softlockup_watchdog_sched() call without
> justification and I feel sched_clock management is not the right
> place, it should
e820 map is updated with information from the zeropage (i.e. pvh_bootparams)
by default_machine_specific_memory_setup(). With the way things are done
now, we end up with a duplicated e820 map.
Signed-off-by: Boris Ostrovsky
---
v2:
* Drop sanitize_e820_map() since it
On Thu, Apr 20, 2017 at 04:51:42PM -0300, Lauro Ramos Venancio wrote:
> @@ -612,7 +604,16 @@ static void init_overlap_sched_group(struct sched_domain
> *sd,
>
> sibling = *per_cpu_ptr(sdd->sd, i);
>
> - /* See the comment near build_group_mask(). */
> +
On 11/06/2016 05:39 PM, Dmitry Vyukov wrote:
> Hello,
>
> This is notes from the discussion we had at Linux Plumbers this week
> regarding providing a formal description of system calls (user API).
>
> The idea come up in the context of syzkaller, syscall fuzzer, which
> has descriptions for
Commit:
2bacec8c318c ("sched: touch softlockup watchdog after idling")
introduced the touch_softlockup_watchdog_sched() call without
justification and I feel sched_clock management is not the right
place, it should only be concerned with producing semi coherent time.
If this causes watchdog
On Fri, 2017-04-21 at 16:18 +0200, Artem Savkov wrote:
> Calling pnfs_put_lset on an IS_ERR pointer results in a NULL pointer
> dereference like the one below. fl_pnfs_update_layout()'s output is
> checked after each call so it doesn't seem that it should try to
> handle
> these errors on it's
For the (older) CPUs that still need the refined TSC calibration, also
update the sched_clock rate.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/tsc.c |5 +
1 file changed, 5 insertions(+)
--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@
On Fri, 2017-04-21 at 08:09 -0700, Eric Dumazet wrote:
> On Fri, 2017-04-21 at 06:29 -0700, Eric Dumazet wrote:
>
> > Thanks for this report.
> >
> > Interesting to see how many drivers got the netpoll stuff wrong :/
> >
> > Can you try :
> >
> > diff --git
On 2017-04-21 10:22, Marek Vasut wrote:
> On 04/21/2017 06:19 PM, Stefan Agner wrote:
>> On 2017-04-21 06:08, Marek Vasut wrote:
>>> On 04/21/2017 05:15 AM, Stefan Agner wrote:
On 2017-04-20 19:03, Marek Vasut wrote:
> On 04/21/2017 03:07 AM, Stefan Agner wrote:
>> Add support for
On Fri, 2017-04-21 at 06:29 -0700, Eric Dumazet wrote:
> Thanks for this report.
>
> Interesting to see how many drivers got the netpoll stuff wrong :/
>
> Can you try :
>
> diff --git a/drivers/net/ethernet/realtek/r8169.c
> b/drivers/net/ethernet/realtek/r8169.c
> index
>
It is currently impossible to see what is going on with objtool when
building, so call echo-cmd to see the actions:
gcc -Wp,-MD,arch/x86/entry/.entry_64.o.d -nostdinc -isystem ...
./tools/objtool/objtool check "arch/x86/entry/entry_64.o";
Signed-off-by: Jiri Slaby
Cc:
On Fri, Apr 21, 2017 at 10:04:35AM -0600, Baicar, Tyler wrote:
> This is basically what I already had in v14...you asked to move it into a
> different if-statement? https://lkml.org/lkml/2017/4/12/397
Well, clearly I've been smoking some nasty potent sh*t. :-\
/me goes and looks at the spec:
The patch
ASoC: mediatek: add I2C dependency for CS42XX8
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
regulator: anatop: make regulator name property required
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
Viresh Kumar writes:
> On 20-04-17, 22:14, Robert Jarzmik wrote:
>> Viresh Kumar writes:
>>
>> > Compiling the DT file with W=1, DTC warns like follows:
>> >
>> > Warning (unit_address_vs_reg): Node /opp_table0/opp@10 has a
>> > unit
---
v2:
Changes were rebased on source files from Linux next-20170421.
These were recombined as requested by Doug Ledford.
drivers/infiniband/hw/mlx4/main.c | 14 +-
drivers/infiniband/hw/mlx4/qp.c | 6 +++---
drivers/infiniband/hw/mlx5/qp.c | 21 +++--
drivers/in
On 4/21/17 10:47 AM, Eric Dumazet wrote:
> On Fri, 2017-04-21 at 08:27 -0600, David Ahern wrote:
>> On 4/20/17 10:09 AM, Andrey Konovalov wrote:
>>> On Thu, Apr 20, 2017 at 5:39 PM, Andrey Konovalov
>>> wrote:
On Thu, Apr 20, 2017 at 5:35 PM, David Ahern
flush_tlb_page() passes a bogus range to flush_tlb_others() and
expects the latter to fix it up. native_flush_tlb_others() has the
fixup but Xen's version doesn't. Move the fixup to
flush_tlb_others().
AFAICS the only real effect is that, without this fix, Xen would
flush everything instead of
On Fri, Apr 21, 2017 at 3:07 PM, Daniel Baluta wrote:
> The new PLL configuration code triggers a harmless warning:
>
> sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
> sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used
> uninitialized
On Fri, Apr 21, 2017 at 12:38 PM, Stefan Agner wrote:
> On 2017-04-21 10:22, Marek Vasut wrote:
>> On 04/21/2017 06:19 PM, Stefan Agner wrote:
>>> On 2017-04-21 06:08, Marek Vasut wrote:
On 04/21/2017 05:15 AM, Stefan Agner wrote:
> On 2017-04-20 19:03, Marek Vasut
On Tue, Apr 18, 2017 at 04:17:35PM -0500, Tom Lendacky wrote:
> Add support to the early boot code to use Secure Memory Encryption (SME).
> Since the kernel has been loaded into memory in a decrypted state, support
> is added to encrypt the kernel in place and update the early pagetables
On 21/04/17 20:42, Linus Torvalds wrote:
> On Fri, Apr 21, 2017 at 10:25 AM, Linus Torvalds
> wrote:
>>
>> I'm assuming that the real cause is simply that "dev->reg_state" ends
>> up being NETREG_UNREGISTERING or something. Maybe the BUG_ON() could
>> be just
An tracing instance has several of the same capabilities as the top level
instance, but may be implemented slightly different. Instead of just writing
tests that duplicat the same test cases of the top level instance, allow a
test to be written for both the top level as well as for an instance.
On 4/21/2017 6:21 AM, Borislav Petkov wrote:
On Tue, Apr 18, 2017 at 05:05:15PM -0600, Tyler Baicar wrote:
The ACPI 6.1 spec added a timestamp to the HEST generic data
HEST?
I see the timestamp in
Table 18-343 Generic Error Data Entry
where those things are "One or more Generic Error Data
This is a prep patch to add a new error code to libiscsi. We want to
rework some kmap calls to be able to fail. When we do, we'd like to
use this error code.
This patch simply introduces ISCSI_TCP_INTERNAL_ERR and prints
"Internal Error." when it gets hit.
Signed-off-by: Logan Gunthorpe
From: Markus Elfring
Date: Fri, 21 Apr 2017 18:22:42 +0200
* Call the function "memset" directly in an if branch without using
an intermediate variable.
* Delete the local variable "clear" which became unnecessary with
this refactoring.
Signed-off-by: Markus
+Cc: Heikki,
On Fri, Apr 21, 2017 at 4:01 PM, Hans de Goede wrote:
> On some boards the Whiskey Cove PMIC is combined with an external USB
> Type-C controller, in this case extcon consumers should use the Type-C
> extcon state, except when the USB Type-C controller detects a
On 04/21/2017 11:15 AM, Andy Lutomirski wrote:
> I'm about to rewrite the function almost completely, but first I
> want to get a functional change out of the way. Currently, if
> flush_tlb_mm_range() does not flush the local TLB at all, it will
> never do individual page flushes on remote CPUs.
From: Markus Elfring
Date: Fri, 21 Apr 2017 19:14:11 +0200
Use space characters at some source code places according to
the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/mlx4/qp.c | 4 ++--
+Cc: Heikki.
It looks like you better Cc him with entire series.
On Fri, Apr 21, 2017 at 4:01 PM, Hans de Goede wrote:
> This allows a nice cleanup of cht_wc_extcon_pwrsrc_event, getting rid
> of all the gotos in there.
>
> This also is a preparation patch for adding USB
On Fri, Apr 21, 2017 at 10:25 AM, Linus Torvalds
wrote:
> On Fri, Apr 21, 2017 at 5:48 AM, Andrey Konovalov
> wrote:
>>
>> I've got the following error report while fuzzing the kernel with syzkaller.
>>
>> [ cut here
Kbuild works in objtree, not in srctree. So, __FILE__ is prefixed
with $(srctree)/ for out-of-tree build.
It would be nice to see the same log regardless
in-tree, or out-of-tree build.
1/2 adds a new macro KBUILD_FILE. This points the relative path
of the file we are building. This is
__FILE__ can be a long absolute path for out-of-tree build.
The output of WARN_ON() and friends depends on the location of
the object tree, like this:
WARNING: CPU: 1 PID: 1 at /path/to/build/directory/arch/arm64/kernel/foo.c:...
KBUILD_FILE is a relative from srctree, so we will always see the
Since Kbuild runs in the objtree, __FILE__ can be a very long path
depending of $(srctree).
Commit 9da0763bdd82 ("kbuild: Use relative path when building in a
subdir of the source tree") made the situation better for cases
where objtree is a child of srctree. ($(srctree) is "..")
For other
On 04/21/2017 10:45 AM, Andrew Cooper wrote:
> On 21/04/17 15:38, Juergen Gross wrote:
>> On 21/04/17 16:24, Boris Ostrovsky wrote:
+static bool __init xen_check_xsave(void)
{
- unsigned int ax, bx, cx, dx;
- unsigned int xsave_mask;
+ unsigned int err, eax, edx;
hsotg->uphy and hsotg->clk will be set or NULL, but not ERRPTR.
So IS_ERR_OR_NULL() is not required at all.
NULL pointer argument is OK for "usb_phy_set_suspend", "otg_set_host",
"otg_set_peripheral", "clk_prepare_enable" and "clk_disable_unprepare"
functions. So remove unnecessary checkings.
On Fri, Apr 21, 2017 at 7:16 AM, Kirill A. Shutemov
wrote:
> On Thu, Apr 20, 2017 at 02:46:51PM -0700, Dan Williams wrote:
>> On Sat, Mar 18, 2017 at 2:52 AM, tip-bot for Kirill A. Shutemov
>> wrote:
>> > Commit-ID:
On Fri, Apr 21, 2017 at 04:12:43PM +0200, Jiri Slaby wrote:
> Do not use a custom macro FUNC for starts of the global functions, use
> ENTRY instead.
>
> And while at it, annotate also ends of the functions by ENDPROC.
>
> Signed-off-by: Jiri Slaby
> Cc: "David S. Miller"
On Wed, Apr 19, 2017 at 11:38 PM, Jérémy Lefaure
wrote:
> When building object-list.o, gcc 6 raises a warning on the sprintf call
> in fscache_objlist_show:
>
> CC fs/fscache/object-list.o
> fs/fscache/object-list.c: In function ‘fscache_objlist_show’:
>
On Thu, Apr 20, 2017 at 9:52 PM, Kees Cook wrote:
> On Thu, Apr 20, 2017 at 3:15 AM, Arnd Bergmann wrote:
>> On Sun, Apr 16, 2017 at 9:52 PM, Kees Cook wrote:
> The original gcc-4.3 release was in early 2008. If we decide to still
On Fri, Apr 21, 2017 at 1:55 PM, Arnd Bergmann wrote:
> On Thu, Apr 20, 2017 at 9:52 PM, Kees Cook wrote:
>> On Thu, Apr 20, 2017 at 3:15 AM, Arnd Bergmann wrote:
>>> On Sun, Apr 16, 2017 at 9:52 PM, Kees Cook wrote:
When I2C is disabled, we get a link error:
drivers/platform/built-in.o: In function `cht_int33fe_remove':
intel_cht_int33fe.c:(.text+0x8ba): undefined reference to
`i2c_unregister_device'
drivers/platform/built-in.o: In function `cht_int33fe_probe':
intel_cht_int33fe.c:(.text+0x9ec): undefined
On 4/21/17 2:31 AM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilim...@oracle.com
wrote:
On 4/20/17 10:53 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell
wrote:
Hi all,
Today's
From: "Steven Rostedt (VMware)"
As the data pointer for individual ips will soon be removed and no longer
passed to the callback function probe handlers, convert the rest of the function
trigger counters over to the new ftrace_func_mapper helper functions.
Signed-off-by:
From: "Steven Rostedt (VMware)"
In order to eventually have each trace_array instance have its own unique
set of function probes (triggers), the trace array needs to hold the ops and
the filters for the probes.
This is the first step to accomplish this. Instead of having
From: "Steven Rostedt (VMware)"
As nothing outside the tracing directory uses the function probes mechanism,
I'm moving the prototypes out of the include/linux/ftrace.h and into the
local kernel/trace/trace.h header. I plan on making them hook to the
trace_array structure
From: "Steven Rostedt (VMware)"
Nothing uses "flags" in the ftrace_func_probe descriptor. Remove it.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/ftrace.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/trace/ftrace.c
+Dave,
On 4/21/2017 2:44 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 11:02 PM, santosh.shilim...@oracle.com
wrote:
On 4/21/17 2:31 AM, Arnd Bergmann wrote:
[...]
arm-soc/next/drivers:
ae3874cc931b ARM: keystone: Drop PM domain support for k2g
On Fri, Apr 21, 2017 at 10:22:52AM +0800, zhichang.yuan wrote:
> Hi, Dann,
>
>
>
> On 04/21/2017 04:57 AM, dann frazier wrote:
> > On Thu, Mar 30, 2017 at 9:26 AM, zhichang.yuan
> > wrote:
> >> On some platforms(such as Hip06/Hip07), the legacy ISA/LPC devices
Sorry about the top posting.
I did ask about it on the 9th of April and the reply was that the email
was 'acked'. Since I did not get a further email, I assumed it was lost.
Perhaps I misunderstood.
Thanks!
Chandra
On Fri, 21 Apr 2017, Greg KH wrote:
>
> Q: Why is top-posting such a bad
I'm about to rewrite the function almost completely, but first I
want to get a functional change out of the way. Currently, if
flush_tlb_mm_range() does not flush the local TLB at all, it will
never do individual page flushes on remote CPUs. This seems to be
an accident, and preserving it will
I have some less straightforward cleanups coming, but these three
are easy and might even be okay for 4.12 assuming that someone feels
like reviewing them.
Andy Lutomirski (3):
x86/mm: Remove flush_tlb() and flush_tlb_current_task()
x86/mm: Make flush_tlb_mm_range() more predictable
x86/mm:
Add cross target to CC if using clang. Also add custom gcc toolchain
path for fallback gcc tools.
Clang will fallback to using things like ld, as, and libgcc if
(respectively) one of the llvm linkers isn't available, the integrated
assembler is turned off, or an appropriately cross-compiled
nux coding style convention.
Signed-off-by: Markus Elfring <elfr...@users.sourceforge.net>
---
v2:
Changes were rebased on source files from Linux next-20170421.
These were recombined as requested by Doug Ledford.
drivers/infiniband/hw/mlx4/mad.c | 6 +++---
drivers/infiniband/hw/mlx4/main.
On Fri, 2017-04-21 at 20:17 +0200, SF Markus Elfring wrote:
> Several update suggestions were taken into account
> from static source code analysis.
Hello Markus,
Patches should either be useful to users of the Linux kernel, e.g. by adding
new functionality or by fixing a bug, or to kernel
From: Markus Elfring
Date: Fri, 21 Apr 2017 19:19:20 +0200
The kfree() function was called in up to five cases
by the create_kernel_qp() function during error handling
even if the passed data structure member contained a null pointer.
* Adjust jump targets
Allow the possibility to configure the charge and the current voltage of
the charger and also the NTC type for battery temperature measurement.
Signed-off-by: Enric Balletbo i Serra
---
Changes since v1:
- Requested by Rob Herring
- Rename ti,charge-* to
On 4/18/2017 4:22 PM, Tom Lendacky wrote:
Add support to check if SME has been enabled and if memory encryption
should be activated (checking of command line option based on the
configuration of the default state). If memory encryption is to be
activated, then the encryption mask is set and the
The iMX-TLV320AIC23 driver isn't from Freescale, but from a company named
Eukrea Electromatique, originally for their own boards. From the code I get
the impression it is a bit older, its DT options use a differing naming
scheme. Patch it up a bit:
- Remove Eukrea naming, i.MX is from Freescale,
Hi Markus,
On 15/04/17 05:04, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 14 Apr 2017 18:48:15 +0200
>
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus
> Patches should either be useful to users of the Linux kernel, e.g. by adding
> new functionality or by fixing a bug, or to kernel developers, e.g. by making
> their workflow easier.
Such an expectation is generally fine.
> I don't think this patch series falls in either category
I find that
On 04/21/2017 01:37 PM, Dan Carpenter wrote:
> We set "cmd->state = -ENODEV;" but "cmd" hasn't been initialized yet.
> It's weird that GCC doesn't catch this.
That is weird...
> diff --git a/drivers/block/mtip32xx/mtip32xx.c
> b/drivers/block/mtip32xx/mtip32xx.c
> index
From: Nikolay Aleksandrov
Date: Fri, 21 Apr 2017 22:56:26 +0300
> On 21/04/17 22:50, Nikolay Aleksandrov wrote:
>> On 21/04/17 22:36, David Miller wrote:
>>> From: Nikolay Aleksandrov
>>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>>
On
While this may appear as a humdrum one line change, it's actually quite
important. An sk_buff stores data in three places:
1. A linear chunk of allocated memory in skb->data. This is the easiest
one to work with, but it precludes using scatterdata since the memory
must be linear.
2. The
From: "Steven Rostedt (VMware)"
Add a link list to the trace_array to hold func probes that are registered.
Currently, all function probes are the same for all instances as it was
before, that is, only the top level trace_array holds the function probes.
But this lays the
From: "Steven Rostedt (VMware)"
In order to move the ops to the function probes directly, they need a way to
map function ips to their own data without depending on the infrastructure
of the function probes, as the data field will be going away.
New helper functions are
From: "Steven Rostedt (VMware)"
Have the stacktrace function trigger probe trigger stack traces within the
instance that they were added to in the set_ftrace_filter.
># cd /sys/kernel/debug/tracing
># mkdir instances/foo
># cd instances/foo
># echo schedule:stacktrace:1
From: "Steven Rostedt (VMware)"
Now that the function probes have their own ftrace_ops, there's no reason to
continue using the ftrace_func_hash to find which probe to call in the
function callback. The ops that is passed in to the function callback is
part of the probe_ops
From: "Steven Rostedt (VMware)"
Have the traceon/off function probe triggers affect only the instance they
are set in. This required making the trace_on/off accessible for other files
in the tracing directory.
Signed-off-by: Steven Rostedt (VMware)
---
From: "Steven Rostedt (VMware)"
As the data pointer for individual ips will soon be removed and no longer
passed to the callback function probe handlers, convert the snapshot
trigger counter over to the new ftrace_func_mapper helper functions.
Signed-off-by: Steven Rostedt
From: "Steven Rostedt (VMware)"
With the redesign of the registration and execution of the function probes
(triggers), data can now be passed from the setup of the probe to the probe
callers that are specific to the trace_array it is on. Although, all probes
still only
Tested 9 distros centos, Debian, Fedora, Gentoo, Opensuse, slackware, Ubuntu,
poky showed awk at /usr/bin/awk.
Here is another similar patch which has been approved
https://patchwork.kernel.org/patch/9650581/
centos-7:
lrwxrwxrwx 1 root root 4 Mar 15 19:58 /bin/awk -> gawk lrwxrwxrwx 1 root
On 04/18/2017 02:17 PM, Tom Lendacky wrote:
> @@ -55,7 +57,7 @@ static inline void copy_user_page(void *to, void *from,
> unsigned long vaddr,
> __phys_addr_symbol(__phys_reloc_hide((unsigned long)(x)))
>
> #ifndef __va
> -#define __va(x) ((void *)((unsigned
>
The patch
spi: Add can_dma like interface for spi_flash_read
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
On 04/21/2017 06:30 PM, Andrey Smirnov wrote:
> In anticipation of supporting chips that need it, extend the size of
> struct flash_info's 'jedec_id' field to make room 2 byte of extended
> device information as well as add code to fetch this data during
> jedec_probe().
>
> Cc: cphe...@gmail.com
On Fri, Apr 21, 2017 at 10:50 AM, Andrey Konovalov
wrote:
> Hi!
>
> We're investigating some approaches to improve isolation of syzkaller
> programs. One of the ideas is run each program in it's own user/net
> namespace. However, while I was experimenting with this, I
On 4/21/2017 11:55 AM, Borislav Petkov wrote:
On Tue, Apr 18, 2017 at 05:05:16PM -0600, Tyler Baicar wrote:
Add support for ARM Common Platform Error Record (CPER).
UEFI 2.6 specification adds support for ARM specific
processor error information to be reported as part of the
CPER records. This
On 21/04/17 15:38, Juergen Gross wrote:
> On 21/04/17 16:24, Boris Ostrovsky wrote:
>>> +static bool __init xen_check_xsave(void)
>>> {
>>> - unsigned int ax, bx, cx, dx;
>>> - unsigned int xsave_mask;
>>> + unsigned int err, eax, edx;
>>>
>>> - ax = 1;
>>> - cx = 0;
>>> - cpuid(1,
I'm about to rewrite the function almost completely, but first I
want to get a functional change out of the way. Currently, if
flush_tlb_mm_range() does not flush the local TLB at all, it will
never do individual page flushes on remote CPUs. This seems to be
an accident, and preserving it will
essary braces in mlx4_ib_add()
Delete unwanted spaces behind usages of the sizeof operator
Add spaces for better code readability
Less function calls in create_kernel_qp() after error detection
---
v2:
Changes were rebased on source files from Linux next-20170421.
Some of them were reco
On Fri, Apr 21, 2017 at 03:31:08PM +0100, David Howells wrote:
> Eric Biggers wrote:
>
> > - memzero_explicit(epayload->decrypted_data, epayload->decrypted_datalen);
> > - kfree(key->payload.data[0]);
> > + kzfree(key->payload.data[0]);
>
> Should kzfree() be using
On Friday, April 14, 2017 03:50:04 PM Christophe Leroy wrote:
> CONFIG_8xx is deprecated and should soon be removed in favor
> of CONFIG_PPC_8xx.
>
> Signed-off-by: Christophe Leroy
Patch queued for 4.12, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R
On 21/04/17 20:42, Nikolay Aleksandrov wrote:
> Andrey Konovalov reported a BUG caused by the ip6mr code which is caused
> because we call unregister_netdevice_many for a device that is already
> being destroyed. In IPv4's ipmr that has been resolved by two commits
> long time ago by introducing
From: Markus Elfring
Date: Fri, 21 Apr 2017 19:11:59 +0200
* Replace the source code "sizeof (" by "sizeof("
according to the Linux coding style convention.
* Adjust indentation at a few places.
Signed-off-by: Markus Elfring
---
+Cc: Heikki.
He might comment on this.
On Fri, Apr 21, 2017 at 4:01 PM, Hans de Goede wrote:
> Add support for USB TYPE-C cable detection on systems using a
> FUSB302 USB TYPE-C controller.
>
> Signed-off-by: Hans de Goede
> ---
>
2017-04-21 1:15 GMT+02:00 AZO :
> To Linux kernel input driver mainteners
>
> I mailed to mainteners a week ago.
> Please can anyone answer?
You should send the email directly to the maintainers in addition to
the mailing list. You can use the get_maintainer.pl script to know
On Tue, Mar 07, 2017 at 04:32:44PM -0800, Ricardo Neri wrote:
> insn_get_addr_ref returns the effective address as defined by the
Please end function names with parentheses.
> section 3.7.5.1 Vol 1 of the Intel 64 and IA-32 Architectures Software
> Developer's Manual. In order to compute the
Hello Andreas,
On 04/21/2017 08:16 PM, Andreas Dilger wrote:
> On Apr 21, 2017, at 7:13 AM, Michael Kerrisk (man-pages)
> wrote:
>>
>> On 04/21/2017 03:01 PM, David Howells wrote:
>>> Michael Kerrisk (man-pages) wrote:
>>
>>> (3) There's no
On 04/21/2017 08:37 AM, Christoph Hellwig wrote:
> On Fri, Apr 21, 2017 at 08:14:03AM -0600, Jens Axboe wrote:
>> From: Jens Axboe
>> Subject: [PATCH] mtip32xx: fix dereference of stack garbage
>>
>> We need to get the command payload from the request before
>> we attempt to
Since Kbuild runs in the objtree, __FILE__ can be a very long path
depending of $(srctree).
Commit 9da0763bdd82 ("kbuild: Use relative path when building in a
subdir of the source tree") made the situation better for cases
where objtree is a child of srctree. ($(srctree) is "..")
For other
We set "cmd->state = -ENODEV;" but "cmd" hasn't been initialized yet.
It's weird that GCC doesn't catch this.
Fixes: 4dda4735c581 ("mtip32xx: add a status field to struct mtip_cmd")
Signed-off-by: Dan Carpenter
---
Not tested, please review carefully.
diff --git
From: Cong Wang
Date: Fri, 21 Apr 2017 11:55:04 -0700
> On Fri, Apr 21, 2017 at 10:25 AM, Linus Torvalds
> wrote:
>> On Fri, Apr 21, 2017 at 5:48 AM, Andrey Konovalov
>> wrote:
>>>
>>> I've got the following error
On Thu, 20 Apr 2017, Mehmet Kayaalp wrote:
> > On Apr 20, 2017, at 7:13 PM, Henrique de Moraes Holschuh
> > wrote:
> > On Thu, 20 Apr 2017, Mehmet Kayaalp wrote:
> >> Include a random filled binary in vmlinux at the space reserved with
> >> CONFIG_SYSTEM_EXTRA_CERTIFICATE. This
1) Don't race in IPSEC dumps, from Yuejie Shi.
2) Verify lengths properly in IPSEC reqeusts, from Herbert Xu.
3) Fix out of bounds access in ipv6 segment routing code, from David
Lebrun.
4) Don't write into the header of cloned SKBs in smsc95xx driver, from
James Hughes.
5) Several
On 21/04/17 22:50, Nikolay Aleksandrov wrote:
> On 21/04/17 22:36, David Miller wrote:
>> From: Nikolay Aleksandrov
>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>
>>> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
Andrey Konovalov reported a BUG caused by the ip6mr
From: Nikolay Aleksandrov
Date: Fri, 21 Apr 2017 22:50:35 +0300
> On 21/04/17 22:36, David Miller wrote:
>> From: Nikolay Aleksandrov
>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>
>>> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
On Thu, Apr 20, 2017 at 9:09 AM, Alan Tull wrote:
> @@ -382,7 +377,13 @@ static int fpga_region_notify_pre_apply(struct
> fpga_region *region,
> if (of_property_read_bool(nd->overlay, "encrypted-fpga-config"))
> info->flags |=
On Friday, April 21, 2017 05:46:45 PM Andy Shevchenko wrote:
> Recently introduced helpers take pointers to uuid_{be|le} instead of
> reference.
>
> Using them makes code less ugly.
>
> Cc: "Rafael J. Wysocki"
> Signed-off-by: Andy Shevchenko
From: "Steven Rostedt (VMware)"
Pass the trace_array associated to a ftrace_probe_ops into the probe_ops
func(), init() and free() functions. The trace_array is the descriptor that
describes a tracing instance. This will help create the infrastructure that
will allow having
From: "Steven Rostedt (VMware)"
There are no users of unregister_ftrace_function_probe_all(). The only probe
function that is used is unregister_ftrace_function_probe_func(). Rename the
internal static function __unregister_ftrace_function_probe() to
501 - 600 of 1708 matches
Mail list logo