From: Markus Elfring
Date: Mon, 2 Oct 2017 22:34:56 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete two error messages for a failed memory allocation
Delete an unnecessary return statement
arch/arm/mach-s3c64xx/dev-backlight
From: Markus Elfring
Date: Mon, 2 Oct 2017 22:30:55 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Signed-off-by: Markus Elfring
---
arch/arm
From: Markus Elfring
Date: Mon, 2 Oct 2017 22:20:39 +0200
Omit extra messages for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/arm/mach-s3c64xx/dev-backlight.c | 9 +++--
1 file changed, 3 in
On Mon, Oct 02, 2017 at 12:08:49PM +, Quentin Schulz wrote:
> This board has an AXP813 PMIC so let's include its dtsi.
>
> Signed-off-by: Quentin Schulz
> ---
> arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boo
On Mon, Oct 02, 2017 at 12:08:54PM +, Quentin Schulz wrote:
> On AXP813/818, GPIO0 and GPIO1 can be used as LDO as (respectively)
> ldo_io0 and ldo_io1.
>
> Let's add the pinctrl properties to the said regulators.
>
> Signed-off-by: Quentin Schulz
> ---
> arch/arm/boot/dts/axp81x.dtsi | 14
On Mon, 2 Oct 2017, Don Zickus wrote:
> On Mon, Oct 02, 2017 at 07:32:57PM +, Thomas Gleixner wrote:
> > static void softlockup_reconfigure_threads(void)
>
> There is a second copy of , you will need to add identical locking there
> too.
Good catch, but then we might move it further out
AMDs new Secure Encrypted Virtualization (SEV) feature allows the memory
contents of a virtual machines to be transparently encrypted with a key
unique to the guest VM. The programming and management of the encryption
keys are handled by the AMD Secure Processor (AMD-SP), which exposes the
commands
Define Secure Encrypted Virtualization (SEV) key management command id
and structure. The command definition is available in SEV KM [1] spec
0.14.
[1] http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Borislav Petkov
Cc: Herbert Xu
Cc:
On Mon 02-10-17 13:24:25, Shakeel Butt wrote:
> On Mon, Oct 2, 2017 at 12:56 PM, Michal Hocko wrote:
> > On Mon 02-10-17 12:45:18, Shakeel Butt wrote:
> >> > I am sorry to cut the rest of your proposal because it simply goes over
> >> > the scope of the proposed solution while the usecase you are
On 02.10.2017 22:54, Linus Torvalds wrote:
On Mon, Oct 2, 2017 at 2:54 AM, Konstantin Khlebnikov
wrote:
This patch implements write-behind policy which tracks sequential writes
and starts background writeback when have enough dirty pages in a row.
This looks lovely to me.
I do wonder if you
On 10/02/2017 07:44 PM, Boris Ostrovsky wrote:
>
>> +
>> +static void xen_setup_vsyscall_time_info(void)
>> +{
>> +struct vcpu_register_time_memory_area t;
>> +struct pvclock_vsyscall_time_info *ti;
>> +int ret;
>
>
> In the previous version you'd return immediately if
> PVCLOCK_TS
Hi!
I'm looking into the constraint of moving interrupt affinities in interrupt
context only which we have for non remapped interrupts.
After staring into manuals and application notes for quite a while I came
to the conclusion that this is only required for level type interrupts. The
reason for
- Paul E. McKenney wrote:
> Actually, we should be able to do a little bit better than that.
> If PREEMPT=n but PREEMPT_COUNT=y, then preempt_count() will know
> about RCU read-side critical sections via preempt_disable().
>
> So maybe something like this?
>
> n.halted = is_idle_task(
Geert Uytterhoeven wrote:
> Now this has hit mainline, the "BIG_KEYS" Kconfig symbol appeared on my
> radar. Is there any reason this cannot be tristate?
It was tristate, but it got converted to bool:
commit 2eaf6b5dcafda2b8c22930eff7f48a364fce1741
KEYS: Make BIG_KEYS boolean
a
On 09/21, Joel Stanley wrote:
> @@ -160,6 +191,104 @@ static struct clk_hw *aspeed_calc_pll(const char *name,
> u32 val)
> mult, div);
> }
>
> +static int __init aspeed_clk_probe(struct platform_device *pdev)
Drop __init? Should be a section mismatch with __init here.
>
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that jus
Hi Steven,
On Mon, Oct 2, 2017 at 12:37 PM, Steven Rostedt wrote:
> On Mon, 2 Oct 2017 12:33:30 -0700
> Joel Fernandes wrote:
>
>
>> diff --git a/include/linux/irqflags.h b/include/linux/irqflags.h
>> index 5dd1272d1ab2..2a1af0dd9cc4 100644
>> --- a/include/linux/irqflags.h
>> +++ b/include/linu
On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote:
> Fengguang, assuming it's reliably recreatable, any chance you could
> recreate with the following patch?
Sorry, here's a version which actually compiles.
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
The property "post-power-on-delay-ms"" allows a platform to specify
the delay needed after power-on, but only via device trees. Thus
allow ACPI systems to also provide the same information.
Signed-off-by: Rajat Jain
---
drivers/hid/i2c-hid/i2c-hid.c | 5 +
1 file changed, 5 insertions(+)
di
Gentle ping?
Dinh
On 09/22/2017 01:42 PM, Dinh Nguyen wrote:
> The SoCFPGA Stratix10 reset controller has 32-bit registers. Thus, we
> cannot use BITS_PER_LONG in computing the register and bit offset. Instead,
> we should be using the width of the hardware register for the calculation.
>
> Sign
On 09/21, Joel Stanley wrote:
> The majority of the clocks in the system are gates paired with a reset
> controller that holds the IP in reset.
>
> This borrows from clk_hw_register_gate, but registers two 'gates', one
> to control the clock enable register and the other to control the reset
> IP.
On 09/21, Joel Stanley wrote:
> @@ -112,9 +115,137 @@ static const struct aspeed_gate_data aspeed_gates[]
> __initconst = {
> /* 31: reserved */
> };
>
> +static const struct clk_div_table ast2400_div_table[] = {
> + { 0x0, 2 },
> + { 0x1, 4 },
> + { 0x2, 6 },
> + { 0x3, 8
On Mon, Oct 02, 2017 at 05:11:07PM -0400, Paolo Bonzini wrote:
>
> - Paul E. McKenney wrote:
> > Actually, we should be able to do a little bit better than that.
> > If PREEMPT=n but PREEMPT_COUNT=y, then preempt_count() will know
> > about RCU read-side critical sections via preempt_disable(
On Mon, 2 Oct 2017 15:32:54 -0400 Jérôme Glisse wrote:
> From: Ralph Campbell
>
> Constify pointer parameter to avoid issue when use from code that
> only has const struct page pointer to use in the first place.
That's rather vague. Does such calling code exist in the kernel? This
affects t
The intention here is to set the same array element in src and dst.
Switch the order of these lines so that migrate->npages is only
incremented after we've used it.
Fixes: 8315ada7f095 ("mm/migrate: allow migrate_vma() to alloc new page on
empty entry")
Cc: Jérôme Glisse
Signed-off-by: Reza Arba
On Mon, Oct 02, 2017 at 02:40:42PM -0700, Andrew Morton wrote:
> On Mon, 2 Oct 2017 15:32:54 -0400 Jérôme Glisse wrote:
>
> > From: Ralph Campbell
> >
> > Constify pointer parameter to avoid issue when use from code that
> > only has const struct page pointer to use in the first place.
>
> Th
On Mon, Oct 02, 2017 at 04:44:02PM -0500, Reza Arbab wrote:
> The intention here is to set the same array element in src and dst.
> Switch the order of these lines so that migrate->npages is only
> incremented after we've used it.
I already posted a fix for this today from Mark. Either version is
On Mon, 2 Oct 2017 08:45:40 -0700 Dave Hansen wrote:
> On 09/27/2017 06:02 PM, Huang, Ying wrote:
> > I still think there may be a performance regression for some users
> > because of the change of the algorithm and the knobs, and the
> > performance regression can be resolved via setting the new
On Mon, Oct 02, 2017 at 11:42:05AM +0100, Will Deacon wrote:
> On Sun, Oct 01, 2017 at 11:06:46AM +1100, Tobin C. Harding wrote:
> > Use the %pP functionality to explicitly allow kernel
> > pointers to be logged for stack traces.
> >
> > Signed-off-by: Tobin C. Harding
> > ---
> > arch/arm64/ker
On 02.10.2017 23:00, Jens Axboe wrote:
On 10/02/2017 03:54 AM, Konstantin Khlebnikov wrote:
Traditional writeback tries to accumulate as much dirty data as possible.
This is worth strategy for extremely short-living files and for batching
writes for saving battery power. But for workloads where
From: Colin Ian King
The structures created from macros RTL_DEBUG_IMPL_MAC_SERIES,
RTL_DEBUG_IMPL_BB_SERIES, RTL_DEBUG_IMPL_RF_SERIES and
RTL_DEBUG_IMPL_CAM_SERIES are all local to the source and do
not need to be in global scope, so make them static.
Cleans up 37 sparse warnings of the form:
sy
Juergen Gross:
> When setting up the Xenstore watch for the memory target size the new
> watch will fire at once. Don't try to reach the configured target size
> by onlining new memory in this case, as the current memory size will
> be smaller in almost all cases due to e.g. BIOS reserved pages.
>
On Mon, 2 Oct 2017 11:38:07 +0100 Will Deacon wrote:
> > When I executed numactl -H(which read /sys/devices/system/node/nodeX/cpumap
> > and display cpumask_of_node for each node), but I got different result on
> > X86 and arm64. For each numa node, the former only displayed online CPUs,
> > and
On 09/19, Jeremy Linton wrote:
> There are a few arm64 specific users (cpufreq, psci, etc) which really
> want the cluster rather than the topology_physical_package_id(). Lets
> convert those users to topology_cod_id(). That way when we start
> differentiating the socket/cluster they will continue
The use case is when called by struct hmm_devmem_ops.fault() which passes a
const struct page * pointer and hmm_devmem_page_get_drvdata() is called to get
the private data.
Since HMM was only recently added, it only affects kernels after September 8,
2017.
> -Original Message-
> From: A
On Mon, Oct 2, 2017 at 2:26 PM, Josh Poimboeuf wrote:
>
> The bisect is pointing to a commit which is almost 5 months old, so this
> is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
> enough to realize it's dumping misaligned stack addresses:
Ahh, I didn't pick up on that "es
On 10/02/2017 03:10 PM, David Woodhouse wrote:
On Mon, 2017-10-02 at 14:52 -0400, Don Dutile wrote:
On 10/02/2017 08:35 AM, David Woodhouse wrote:
This would allow you to enable SR-IOV on a PF before its driver is
loaded, right? Even when that driver *is* going to need to perform
resource manag
From: Colin Ian King
The array rmi_f54_report_type_names is local to the source and does
not need to be in global scope, so make it static. Also make the array
const char * const
Cleans up sparse warning:
symbol 'rmi_f54_report_type_names' was not declared. Should it be static?
Signed-off-by: C
On Mon, Oct 02, 2017 at 11:05:25PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The array rmi_f54_report_type_names is local to the source and does
> not need to be in global scope, so make it static. Also make the array
> const char * const
>
> Cleans up sparse warning:
> symbol 'rmi_f54
On Oct 2, 2017, at 10:58 PM, Konstantin Khlebnikov
wrote:
>
> On 02.10.2017 22:54, Linus Torvalds wrote:
>> On Mon, Oct 2, 2017 at 2:54 AM, Konstantin Khlebnikov
>> wrote:
>>>
>>> This patch implements write-behind policy which tracks sequential writes
>>> and starts background writeback when
From: Colin Ian King
The structure pcc_mbox_driver is local to the source and does
not need to be in global scope, so make it static.
Cleans up sparse warning:
symbol 'pcc_mbox_driver' was not declared. Should it be static?
Signed-off-by: Colin Ian King
---
drivers/mailbox/pcc.c | 2 +-
1 fil
On Mon, Oct 2, 2017 at 12:29 AM, Nicolas Pitre wrote:
> On Sun, 1 Oct 2017, Christoph Hellwig wrote:
>
>> up_read(&mm->mmap_sem) in the fault path is a still a complete
>> no-go,
>>
>> NAK
>
> Care to elaborate?
>
> What about mm/filemap.c:__lock_page_or_retry() then?
As soon you up_read() in the
On Mon, Oct 02, 2017 at 12:54:53PM -0700, Linus Torvalds wrote:
> On Mon, Oct 2, 2017 at 2:54 AM, Konstantin Khlebnikov
> wrote:
> >
> > This patch implements write-behind policy which tracks sequential writes
> > and starts background writeback when have enough dirty pages in a row.
>
> This loo
Reviewed-by: Sagi Grimberg
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: 45723bfaf78f78e83e0949895a173ce08cb6ac47
commit: 45723bfaf78f78e83e0949895a173ce08cb6ac47 [38/38] rcu: Consolidate
rcu_nmi_{enter,exit}() into rcu_irq_{enter,exit}()
config: x86_64-acpi-redef (attached
On Wed, 27 Sep, at 01:58:20PM, Rik van Riel wrote:
>
> I like the simplicity of your approach! I hope it does not break
> stuff like netperf...
>
> I have been working on the patch below, which is much less optimistic
> about when to do an affine wakeup than before.
Running netperf for this pat
On 09/26/2017 05:40 AM, Stewart Smith wrote:
The simple fix is to bump the length of the array to 32 which "should be
enough for everyone(TM)".
Tested-by: Mauricio Faria de Oliveira
# uname -r
4.14.0-rc3
# dmesg
[0.00] opal: OPAL detected !
[0.00] crashkernel: memory value ex
On 02.10.2017 20:05, Stephen Warren wrote:
> On 09/29/2017 09:11 PM, Dmitry Osipenko wrote:
>> On 29.09.2017 22:30, Stephen Warren wrote:
>>> On 09/27/2017 02:34 AM, Jon Hunter wrote:
On 27/09/17 02:57, Dmitry Osipenko wrote:
> On 26.09.2017 17:50, Jon Hunter wrote:
>>
>> On 2
From: Madalin Bucur
Date: Mon, 2 Oct 2017 13:31:37 +0300
> The FMan MAC driver allocates a platform device for the Ethernet
> driver to probe on. Setting pdev->dev.of_node with the MAC node
> triggers the MAC driver probing of the new platform device. While
> this fails quickly and does not affec
On Mon, Oct 2, 2017 at 3:45 PM, Dave Chinner wrote:
>
> Yup, it's a good idea. Needs some tweaking, though.
Probably a lot. 256kB seems very eager.
> If we block on close, it becomes:
I'm not at all suggesting blocking at cl;ose, just doing that final
async writebehind (assuming we started any
From: Markus Mayer
This series lets the DPFE driver skip the DPFE firmware download if the
DCPU is already running. If it's running by the time Linux comes up, it
means the boot loader already downloaded the DPFE firmware.
Markus Mayer (2):
memory: brcmstb: dpfe: introduce is_dcpu_enabled()
From: Markus Mayer
In order to check whether or not the DCPU is running, we introduce
a function called is_dcpu_enabled().
Signed-off-by: Markus Mayer
---
drivers/memory/brcmstb_dpfe.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/drivers/memory/brc
From: Markus Mayer
We want to skip downloading the DPFE firmware from Linux if it was
already downloaded by the boot loader.
The driver now checks if the DCPU is already running and, if so,
whether it can process commands. If the DCPU processes commands
successfully, the driver skips the firmwar
On Mon, Aug 28, 2017 at 11:09:44AM -0600, Tyler Baicar wrote:
> Correctable errors do not need any software intervention, so
> avoid calling into the software recovery process for correctable
> errors.
>
> Signed-off-by: Tyler Baicar
> ---
> drivers/pci/pcie/aer/aerdrv_core.c | 3 ++-
> 1 file c
On Fri, 29 Sep 2017 14:30:58 +0200 Jürg Billeter wrote:
> PR_SET_PDEATHSIG sets a parent death signal that the calling process
> will get when its parent thread dies, even when the result of getppid()
> doesn't change because the calling process is reparented to a different
> thread in the same p
On Sat, Sep 30, 2017 at 01:31:15AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> It sometimes is useful to know what power states the kernel thinks
> it puts PCI devices into during system suspend, so add a dev_dbg()
> statement for that.
>
> Signed-off-by: Rafael J. Wysocki
Ac
On Tue, 3 Oct 2017, Richard Weinberger wrote:
> On Mon, Oct 2, 2017 at 12:29 AM, Nicolas Pitre
> wrote:
> > On Sun, 1 Oct 2017, Christoph Hellwig wrote:
> >
> >> up_read(&mm->mmap_sem) in the fault path is a still a complete
> >> no-go,
> >>
> >> NAK
> >
> > Care to elaborate?
> >
> > What about
On Mon, 2 Oct 2017 13:49:30 -0300
Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 02, 2017 at 03:14:05PM +0100, Will Deacon escreveu:
> > On Fri, Sep 29, 2017 at 05:19:40PM -0500, Kim Phillips wrote:
> > > On Thu, 28 Sep 2017 15:09:50 +0100
> > > Will Deacon wrote:
> > > > + if (arm_spe_even
Eric Biggers wrote:
> This is interesting work, though it adds complexity and makes a lot of
> subtle (and potentially breaking) changes to which permissions are required
> for various things. First I think you need to start out with a better
> statement of the problems you are trying to solve.
On Tue, Oct 3, 2017 at 1:29 AM, Bjorn Helgaas wrote:
> On Sat, Sep 30, 2017 at 01:31:15AM +0200, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> It sometimes is useful to know what power states the kernel thinks
>> it puts PCI devices into during system suspend, so add a dev_dbg()
>> st
Fix fix regression in silencing output from RUN_TESTS introduced by
commit <8230b905a6780c6> selftests: mqueue: Use full path to run tests
from Makefile
Signed-off-by: Shuah Khan
---
tools/testing/selftests/mqueue/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/t
Change to enable dochelp run from main make level to make it easier to
use it.
Signed-off-by: Shuah Khan
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index cf007a31d575..f99d1b36c437 100644
--- a/Makefile
+++ b/Makefile
@@ -1454,7 +1454,7 @
The patch below now only touches drivers/ide/ide-scan-pci.c.
It fixes a problem introduced via the PCI tree, so I'd be happy to
merge the fix as well, given an ack from you, Dave. Or you can merge
it yourself with my ack:
Acked-by: Bjorn Helgaas
It mentions that it fixes 30fdfb929e82 ("PCI: Ad
Enhance documentation help message to specify the default location for
the generated documents.
Signed-off-by: Shuah Khan
---
Documentation/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 85f7856f0092..5e65fa5c6ab7 100644
--- a
sysret_ss_attrs fails to compile leading x86 test run to fail on systems
configured to build using PIE by default. Add -no-pie fix it.
Relocation might still fail if relocated above 4G. For now this change
fixes the build and runs x86 tests.
tools/testing/selftests/x86$ make
gcc -m64 -o .../tools
Update to include details on make O=dir support and other changes improve
test results output.
Signed-off-by: Shuah Khan
---
Documentation/dev-tools/kselftest.rst | 34 --
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/Documentation/dev-tools/kself
On Sun, 1 Oct 2017, Christoph Hellwig wrote:
+struct aer_device_list {
+ struct device *dev;
+ struct hlist_node node;
+};
+
extern struct bus_type pcie_port_bus_type;
void aer_isr(struct work_struct *work);
void aer_print_error(struct pci_dev *dev, struct aer_err_info *info);
dif
On Sat, 30 Sep 2017, Sinan Kaya wrote:
On 9/30/2017 1:49 AM, Govindarajulu Varadarajan wrote:
This patch does a pci_bus_walk and adds all the devices to a list. After
unlocking (up_read) &pci_bus_sem, we go through the list and call
err_handler of the devices with devic_lock() held. This way, w
On Mon, Oct 02, 2017 at 04:08:46PM -0700, Linus Torvalds wrote:
> On Mon, Oct 2, 2017 at 3:45 PM, Dave Chinner wrote:
> >
> > Yup, it's a good idea. Needs some tweaking, though.
>
> Probably a lot. 256kB seems very eager.
>
> > If we block on close, it becomes:
>
> I'm not at all suggesting blo
On Mon, Oct 2, 2017 at 11:12 AM, Jiri Slaby wrote:
> All these are functions which are invoked from elsewhere, but they are
> not typical C functions. So we annotate them (as global) using the new
> SYM_CODE_START. All these were not balanced with any END, so mark their
> ends by SYM_CODE_END, app
Hi Thomas,
Thomas Gleixner writes:
> Both the perf reconfiguration and the powerpc watchdog_nmi_reconfigure()
> need to be done in two steps.
>
> 1) Stop all NMIs
> 2) Read the new parameters and start NMIs
>
> Right now watchdog_nmi_reconfigure() is a combination of both. To allow a
>
On Fri, Sep 1, 2017 at 9:44 AM, Thomas Gleixner wrote:
> On Fri, 1 Sep 2017, Nicholas Piggin wrote:
>
>> When failing to enter broadcast timer mode for an idle state that
>> requires it, a new state is selected that does not require broadcast,
>> but the broadcast variable remains set. This causes
Hi,
On Tue, Sep 26, 2017 at 10:45 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> None of the locomo drivers in the tree implements the suspend and
> resume callbacks from struct locomo_driver, so drop them and drop
> the corresponding callbacks from locomo_bus_type.
>
> Signed-off-by
Anything with bytes 1-31,127 will get -EACCES.
Especially \n is bad: instead of natural file-per-line, you need an
user-unfriendly feature of -print0 added to every producer and consumer;
a good part of users either don't know or don't feel the need to bother
with escaping this snowflake, thus int
Since commit 87d80de2800d087ea833cb79bc13f85ff34ed49f ("tracing: Remove
obsolete sched_switch tracer"), the sched_switch selftest is no longer used.
This patch removes the same.
Cc: Steven Rostedt
Signed-off-by: Joel Fernandes
---
This is a resend of the same patch:
https://patchwork.kernel.org/
Also eliminate duplicated debug code by moving it into the core driver.
Cc: Thomas Bogendoerfer
Cc: Chris Zankel
Signed-off-by: Finn Thain
---
drivers/net/ethernet/natsemi/jazzsonic.c | 17 ++
drivers/net/ethernet/natsemi/macsonic.c | 21 +---
drivers/net/ethernet/natsemi/sonic.c
Before expansion, dev->name is "eth%d", so log the slot number instead.
Log the MAC address after the interface gets a meaningful name.
Disambiguate the two identical "Card type %s is unsupported" messages.
Fix the duplicated driver name in the pr_warn() message.
Fixes: 3a3a7f3b7fbd ("net: mac8390
The patch which introduced the 8390 core module parameter 'msg_enable'
failed to do anything useful with it: it merely causes an ancient
version string to be logged.
Remove the other code that logs the same string. Use the msg_enable
module parameter as the default value for ei_local->msg_enable.
The only version of smc9194.c with Mac support is the one in the
linux-mac68k CVS repo. AFAIK that driver never made it to the mainline.
Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194
under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55.
(See pre-git era
This patch series fixes some logging bugs and adds some missing message
severity levels.
There are also cleanup patches for dead code and some Kconfig cruft.
Custom debug message logging is converted to netif_* calls to reduce
code duplication.
All up, about 150 lines of code are eliminated.
My
Log the MAC address after the interface gets a meaningful name.
Drop redundant debug messages for FIFO events recorded in the
interface statistics (consistent with mace.c).
Signed-off-by: Finn Thain
---
drivers/net/ethernet/apple/macmace.c | 10 +++---
1 file changed, 3 insertions(+), 7 dele
Add missing printk severity levels.
Don't print the valid silicon revision number (it's in the source).
Avoid KERN_CONT usage as per advice from checkpatch.
Avoid ifdef around printk calls.
Cc: Thomas Bogendoerfer
Cc: Chris Zankel
Signed-off-by: Finn Thain
---
drivers/net/ethernet/natsemi/jazz
Fix misplaced newlines in conditional log messages.
Add missing printk severity levels.
Log the MAC address after the interface gets a meaningful name.
Drop deprecated "out of memory" message as per checkpatch advice.
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 26 +
On Mon, 2 Oct 2017 18:05:43 +0200
Peter Zijlstra wrote:
> On Tue, Oct 03, 2017 at 12:46:05AM +0900, Masami Hiramatsu wrote:
> > On Mon, 2 Oct 2017 09:33:16 +0200
> > Peter Zijlstra wrote:
>
> > > > [ 87.018115] Call Trace:
> > > > [ 87.025046] trace_hardirqs_off+0xd/0xf
> > > > [ 87.0341
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 36 ---
1 file changed, 36 deletions(-)
diff --git a/drivers/net/ethernet/cirrus/mac89x0.c
b/drivers/net/ethernet/cirrus/mac89x0.c
index f910f0f386d6..8fc43c865621 100644
--- a/drivers/net/ethe
Signed-off-by: Finn Thain
---
drivers/net/ethernet/cirrus/mac89x0.c | 47 ---
1 file changed, 16 insertions(+), 31 deletions(-)
diff --git a/drivers/net/ethernet/cirrus/mac89x0.c
b/drivers/net/ethernet/cirrus/mac89x0.c
index 4393d9b89f33..278df230c5f6 100644
---
On Mon, Oct 02, 2017 at 02:58:08PM -0700, Linus Torvalds wrote:
> On Mon, Oct 2, 2017 at 2:26 PM, Josh Poimboeuf wrote:
> >
> > The bisect is pointing to a commit which is almost 5 months old, so this
> > is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
> > enough to realize i
Zhen Lei writes:
> When I executed numactl -H(which read /sys/devices/system/node/nodeX/cpumap
> and display cpumask_of_node for each node), but I got different result on
> X86 and arm64. For each numa node, the former only displayed online CPUs,
> and the latter displayed all possible CPUs. Unfo
Laurent Dufour writes:
> Hi Andrew,
>
> On 28/09/2017 22:38, Andrew Morton wrote:
>> On Thu, 28 Sep 2017 14:29:02 +0200 Laurent Dufour
>> wrote:
>>
Laurent's [0/n] provides some nice-looking performance benefits for
workloads which are chosen to show performance benefits(!) but, alas
Hi Richard,
2017-09-28 8:24 GMT+09:00 Richard Kuo :
> On Thu, Sep 21, 2017 at 12:17:50AM +0900, Masahiro Yamada wrote:
>> is created (or updated) when Kbuild descends
>> into the init/ directory. In parallel building from a pristine
>> source tree, there is no guarantee exists when
>> arch/hexa
On Mon, 02 Oct 2017 16:46:29 +0300
Kalle Valo wrote:
> We have a tree for wireless so usually it's better to submit wireless
> changes on their own but here I assume Dave will apply this to his tree.
> If not, please resubmit the wireless part in a separate patch.
Ok, I note that.
I'll wait Dave
On Sun, 01 Oct 2017 21:16:19 -0700
Joe Perches wrote:
> These sorts of changes are OK, but for many
> uses, it's more readable to use ARRAY_SIZE(foo)
> in each location rather than using a temporary.
You're right, I missed that one. I will send a v2.
Thank you for your review,
Jérémy
On Mon, 2 Oct 2017 15:22:24 -0400
bfie...@fieldses.org (J. Bruce Fields) wrote:
> Mainly I'd just like to know which you're asking for. Do you want me to
> apply this, or to ACK it so someone else can? If it's sent as a series
> I tend to assume the latter.
>
> But in this case I'm assuming it'
On Mon, 2 Oct 2017 16:07:36 +0300
Andy Shevchenko wrote:
> > + {&gainctrl_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev0), 26,
> > 192,
> > +32},
>
> For all such cases I would rather put on one line disregard checkpatch
> warning for better readability.
I agree that it woul
On Mon, 02 Oct 2017 14:27:52 +0200
"Rafael J. Wysocki" wrote:
> ACPICA is soewhat special code, though and I'm not taking or ACKing patches
> for it directly as a rule.
>
> For one, I'm not sure if ACPICA can use ARRAY_SIZE at all.
Why is it special code that can't use ARRAY_SIZE ? Is it because
On Tue, Oct 03, 2017 at 02:50:42AM +0200, Adam Borowski wrote:
> Anything with bytes 1-31,127 will get -EACCES.
>
> Especially \n is bad: instead of natural file-per-line, you need an
> user-unfriendly feature of -print0 added to every producer and consumer;
> a good part of users either don't kno
On Tue, Oct 3, 2017 at 4:42 AM, Maxime Ripard
wrote:
> On Mon, Oct 02, 2017 at 12:08:54PM +, Quentin Schulz wrote:
>> On AXP813/818, GPIO0 and GPIO1 can be used as LDO as (respectively)
>> ldo_io0 and ldo_io1.
>>
>> Let's add the pinctrl properties to the said regulators.
>>
>> Signed-off-by:
On Tue, Oct 3, 2017 at 12:24 AM, Maxime Ripard
wrote:
> Hi,
>
> On Fri, Sep 29, 2017 at 03:25:12AM +, Chen-Yu Tsai wrote:
>> +#include "axp81x.dtsi"
>> +
>> +®_aldo1 {
>> + regulator-always-on;
>> + regulator-min-microvolt = <180>;
>> + regulator-max-microvolt = <180>;
>> +
The user space application can directly trigger the allocations
from eventpoll_epi and eventpoll_pwq slabs. A buggy or malicious
application can consume a significant amount of system memory by
triggering such allocations. Indeed we have seen in production
where a buggy application was leaking the
On Mon, 2 Oct 2017 09:19:10 -0700
Linus Torvalds wrote:
> On Mon, Oct 2, 2017 at 8:46 AM, Masami Hiramatsu wrote:
> >
> > I'm considering to remove disabling-irq itself from jprobe.
> > (Frankly to say, I would like to remove jprobe itself...)
>
> Please please please...
>
> That would be love
501 - 600 of 713 matches
Mail list logo
