On Tue, Dec 11, 2018 at 08:01:43AM -0600, Bjorn Helgaas wrote:
> Hi David,
>
> I see you're still working on this, but if you do end up going this
> direction eventually, would you mind splitting this into two patches:
> 1) rename the quirk to make it more generic (but not changing any
> behavior)
On 12/11/18 4:34 PM, Li, Aubrey wrote:
>> Is there a reason we shouldn't do:
>>
>> if (!cpu_feature_enabled(X86_FEATURE_AVX512F))
>> update_avx512_state(fpu);
>>
>> ?
>>
> Why _!_ ?
Sorry, got it backwards. I think I was considering having you do a
if (!cpu_feature_enab
* Kuninori Morimoto [181212 00:12]:
>
> Hi Tony, again
>
> > > The issue I have with that it does not then follow the binding doc :)
> > >
> > > See this part in Documentation/devicetree/bindings/graph.txt:
> > >
> > > "If a single port is connected to more than one remote device, an
> > > '
On Thu, Dec 6, 2018 at 3:50 PM Kees Cook wrote:
>
> Commit f149b3155744 ("signal: Never allocate siginfo for SIGKILL or SIGSTOP")
> means that the seccomp selftest cannot check si_pid under SIGSTOP anymore.
> Since it's believed[1] there are no other userspace things depending on the
> old behavio
On Sun, Dec 9, 2018 at 10:24 AM Tycho Andersen wrote:
>
> This patch introduces a means for syscalls matched in seccomp to notify
> some other task that a particular filter has been triggered.
>
> The motivation for this is primarily for use with containers. For example,
> if a container does an i
On Tue, Dec 11, 2018 at 2:24 PM Serge E. Hallyn wrote:
>
> On Sun, Dec 09, 2018 at 11:24:14AM -0700, Tycho Andersen wrote:
> > The idea here is just to give a demonstration of how one could safely use
> > the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular
> > policy is (as no
On Tue, 2018-12-11 at 19:17 +0100, Christian Zigotzky wrote:
> X5000 (P5020 board): U-Boot loads the kernel and the dtb file. Then the
> kernel starts but it doesn't find any hard disks (partitions). That
> means this is also the bad commit for the P5020 board.
What are the disks hanging off ? A
On Mon, Dec 10, 2018 at 7:41 PM wrote:
>
> From: Yulei Zhang
>
> Early this year we spot there may be two issues in kernel
> kfifo.
>
> One is reported by Xiao Guangrong to linux kernel.
> https://lkml.org/lkml/2018/5/11/58
> In current kfifo implementation there are missing memory
> barrier in t
* Tony Lindgren [181212 00:43]:
> The other McBSP instance is dedicated for SoC audio:
>
> CPCAP PMIC codec1-endpoint---McBSP3 on SoC
Sorry this should be McBSP2, not McBSP3 above for
the SoC dedicated audio port.
Tony
Is it okay to tag this commit with `Cc: sta...@vger.kernel.org` so
that it'll get applied to the stable trees once merged into Linux's
tree, if it's not too late? Otherwise I'll follow up on the stable
merges separately. Thanks for making the changes anyway.
On Thu, Nov 22, 2018 at 5:12 AM Petr Ml
On 12/11/18 5:43 PM, Kees Cook wrote:
On Thu, Dec 6, 2018 at 3:50 PM Kees Cook wrote:
Commit f149b3155744 ("signal: Never allocate siginfo for SIGKILL or SIGSTOP")
means that the seccomp selftest cannot check si_pid under SIGSTOP anymore.
Since it's believed[1] there are no other userspace thi
Here are some dac related fixes for adt7316. I'm testing with an adt7516
over i2c to an orange pi pc. I've attempted to test any functionality that
these patches are touching.
Jeremy Fertic (11):
staging: iio: adt7316: fix register and bit definitions
staging: iio: adt7316: invert the logic of
Change two register addresses and one bit definition to match the
datasheet.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/addac/adt7316.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/iio/addac/adt7316.c
b/drivers/staging/iio/addac/adt7316.c
i
Hi Enric,
On 2018년 12월 12일 04:09, Enric Balletbo i Serra wrote:
> There are multiple ChromeOS EC sub-drivers spread in different
> subsystems, as all of them are related to the Chrome stuff add
> Benson and myself as a maintainers for all these sub-drivers.
>
> Signed-off-by: Enric Balletbo i Ser
ADT7316_DA_EN_VIA_DAC_LDCA is set when the dac and ldac registers are being
used to update the dacs instead of the ldac pin. ADT7516_SEL_AIN3 is an adc
input that shares the ldac pin. Only set these bits if an ldac pin is not
being used.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/addac
The dac internal vref settings are part of the ldac config register rather
than the dac config register. Change the variable being used so the read
returns the correct result.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/addac/adt7316.c | 4 ++--
1 file changed, 2 insertions(+), 2 deleti
Change LDCA to LDAC.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/addac/adt7316.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/iio/addac/adt7316.c
b/drivers/staging/iio/addac/adt7316.c
index 58b462ad0c83..020d695ded97 100644
--- a/driv
Based on the output of adt7316_show_all_DAC_update_modes() and
adt7316_show_DAC_update_mode(), adt7316_store_DAC_update_mode() should
expect the user to enter an integer input from 0 to 3. The user input is
currently expected to account for the actual bit positions in the register.
For example, cho
With adt7516/7/9, internal vref is available for dacs a and b, dacs c and
d, or all dacs. The driver doesn't currently support internal vref for all
dacs. Change the else if to an if so both bits are checked rather than
just one or the other.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/
The dac high resolution option enables or disables 10 bit dac resolution
for the adt7316/7 and adt7516/7 when they're set to output voltage
proportional to temperature. Remove the "1 (12 bits)" output from the show
function since that is not an option for this mode. Return "1 (10 bits)"
if the devi
The calculation of the current dac value is using the wrong bits of the
dac lsb register. Create two macros to shift the lsb register value into
lsb position, depending on whether the dac is 10 or 12 bit. Initialize
data to 0 so, with an 8 bit dac, the msb register value can be bitwise
ORed with da
The only assignment to dac_bits is in adt7316_store_da_high_resolution().
This function enables or disables 10 bit dac resolution for the adt7316/7
and adt7516/7 when they're set to output voltage proportional to
temperature. Remove these assignments since they're unnecessary for the
dac high resol
The option to allow the external vref to bypass the reference buffer is
only available for adt7316/7/8. Remove the attributes for adt751x as
well as the chip->id checks from the show and store functions.
Signed-off-by: Jeremy Fertic
---
drivers/staging/iio/addac/adt7316.c | 14 --
1
The lsb calculation is not masking the correct bits from the user input.
Subtract 1 from (1 << offset) to correctly set up the mask to be applied
to user input.
The lsb register stores its value starting at the bit 7 position.
adt7316_store_DAC() currently assumes the value is at the other end of
On Tue, Dec 11, 2018 at 02:53:12PM +0100, Oscar Salvador wrote:
>v1 -> v2:
>- Keep branch to decrease refcount and print out
> the failed pfn/page
>- Modified changelog per Michal's feedback
>- move put_page() out of the if/else branch
>
>---
>>From f81da873be9a5b78
On 2018/12/12 8:14, Arjan van de Ven wrote:
> On 12/11/2018 3:46 PM, Li, Aubrey wrote:
>> On 2018/12/12 1:18, Dave Hansen wrote:
>>> On 12/10/18 4:24 PM, Aubrey Li wrote:
The tracking turns on the usage flag at the next context switch of
the task, but requires 3 consecutive context switch
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
MAINTAINERS
between commit:
cb4f131e1f2c ("MAINTAINERS: Patch monkey for the Hyper-V code")
from the char-misc.current tree and commit:
b255e500c8dc ("net: documentation: build a directory structure for drivers")
On 12/11/18 4:59 PM, Li, Aubrey wrote:
>> maybe instead of a 1/0 bit, it's useful to store the timestamp of the last
>> time we found the task to use avx? (need to find a good time unit)
>>
>>
> Are you suggesting kernel does not do any translation, just provide a fact
> to the user space tool and
On 2018/12/12 上午6:49, Girija Kumar Kasinadhuni wrote:
There are two audio ports on these machines - headset and mic.
Looks like the two audio ports are headset and lineout.
There' s no sound when hp is inserted into the headset port,
though the hp is detected. Without pulseaudio, this issue is
On Tue, Dec 11, 2018 at 03:27:39PM +0100, Michal Hocko wrote:
>From: Michal Hocko
>
>do_migrate_range has been limiting the number of pages to migrate to 256
>for some reason which is not documented. Even if the limit made some
>sense back then when it was introduced it doesn't really serve a good
> Let's first figure out if it works.
I would still like to try applying your patches that went into
printk.git, but for now I wonder if we can get Steven's patch into
4.14 first, for at least we know it mitigated the issue if not
fundamentally addressed it, and we've agreed it's an innocuous chan
From: Will Deacon Sent: Friday, December 7, 2018 5:43 AM
> > hyperv-tlfs.h defines Hyper-V interfaces from the Hyper-V Top Level
> > Functional Spec (TLFS). The TLFS is distinctly oriented to x86/x64,
> > and Hyper-V has not separated out the architecture-dependent parts into
> > x86/x64 vs. ARM6
On Tue, Dec 11, 2018 at 10:09:07AM +, James Morse wrote:
> Hi Akashi,
>
> On 11/12/2018 06:17, AKASHI, Takahiro wrote:
> > On Fri, Dec 07, 2018 at 10:12:47AM +, James Morse wrote:
> >> On 06/12/2018 15:54, Will Deacon wrote:
> >>> On Thu, Dec 06, 2018 at 08:47:04AM -0600, Rob Herring wrote
Please drop this patch. However, it would be happy if this bug can be
fixed as soon as possible.
Nitzan, do you mind if you send your patch for review?
On Tue, Dec 11, 2018 at 3:39 PM Sagi Grimberg wrote:
>
> > I cannot reproduce the bug with the patch; in my failure scenarios, it
> > seems that
On Tue, Dec 11, 2018 at 2:43 PM Rob Herring wrote:
>
> On Tue, Nov 27, 2018 at 08:37:37PM -0800, Andrey Smirnov wrote:
> > Add bits and pieces needed to support IP block variant found on
> > i.MX8MQ SoCs.
> >
> > Cc: p.za...@pengutronix.de
> > Cc: Fabio Estevam
> > Cc: cphe...@gmail.com
> > Cc: l
On Fri, Dec 7, 2018 at 1:56 AM Guenter Roeck wrote:
>
> On Thu, Dec 06, 2018 at 11:02:27AM +0800, Kyle Tso wrote:
> > Current matching rules ensure that the voltage range of selected Source
> > Capability is entirely within the range defined in one of the Sink
> > Capabilities. This is reasonable
On Tue, Dec 11, 2018 at 12:12:38PM +0100, Sebastian Andrzej Siewior wrote:
> srcu_queue_delayed_work_on() disables preemption (and therefore CPU
> hotplug in RCU's case) and then checks based on its own accounting if a
> CPU is online. If the CPU is online it uses queue_delayed_work_on()
> otherwis
The Samsung Exynos's device drivers have the 'SASMUNG EXYNOS' prefix
in front of the specific device driver name. In order to keep the
consistent naming format, change the entry name of bus frequency driver
for Samsung Exynos and then reorder it alpabetically.
- old : BUS FREQUENCY DRIVER FOR SAMSU
Hello all,
Any comments about this patch?
Cheers,
Dongsheng
On 2018/11/30 10:19, Wang, Dongsheng wrote:
> On 2018/11/30 10:04, Wang, Dongsheng wrote:
>> On 2018/11/30 5:22, Kees Cook wrote:
>>> On Tue, Nov 27, 2018 at 8:38 PM Wang, Dongsheng
>>> wrote:
Hello Kees,
On 2018/11/28 6
Hi,
On Tue, Dec 11, 2018 at 04:37:54PM +0800, joeyli wrote:
> Hi Yu Chen,
>
> Thanks for your response!
>
> On Tue, Dec 11, 2018 at 11:12:21AM +0800, Yu Chen wrote:
> > Hi Joey,
> > On Mon, Dec 10, 2018 at 02:31:53PM +0800, joeyli wrote:
> > > Hi Chen Yu and ACPI experts,
> > >
> > > On Sat, May
From: guomin chen
Under normal circumstances,When do_exit exits, mm->owner will
be updated on exit_mm(). but when the kernel process calls
unuse_mm() and then exits,mm->owner cannot be updated. And it
will point to a task that has been released.
Below is my issue on vhost_net:
A, B are
在 2018年12月05日 05:33, Lendacky, Thomas 写道:
> On 11/29/2018 09:37 PM, Dave Young wrote:
>> + more people
>>
>> On 11/29/18 at 04:09pm, Lianbo Jiang wrote:
>>> When doing kexec_file_load, the first kernel needs to pass the e820
>>> reserved ranges to the second kernel. But kernel can not exactly
>>> m
> -Original Message-
> From: Scott Wood
> Sent: 2018年11月26日 9:19
> To: Andy Tang
> Cc: mturque...@baylibre.com; sb...@kernel.org; robh...@kernel.org;
> mark.rutl...@arm.com; b...@kernel.crashing.org; pau...@samba.org;
> m...@ellerman.id.au; linux-...@vger.kernel.org;
> devicet...@vger.k
Hello all,
Any comments about this patch?
Cheers
Dongsheng
On 2018/11/23 16:12, Wang, Dongsheng wrote:
> Hello Robert,
>
> Do you have any comments about this patch?
> Thanks.
>
>
> Cheers
> Dongsheng
>
> On 2018/11/13 18:46, Wang, Dongsheng wrote:
>> The new naming rule is added in acpica versi
> >> +tmode = le16_to_cpu(ctrl->wIndex);
> >> +
> >> +if (!set || (tmode & 0xff) != 0)
> >> +return -EINVAL;
> >> +
> >> +switch (tmode >> 8) {
> >> +case TEST_J:
> >> +case TEST_K:
> >> +case TEST_SE0_NAK:
Hi Mark,
These five patches are based on patch series spi: lpspi: Add Slave Mode support
for LPSPI. For the patch series make a big change, should I hold these five
patches until the patch series are applied in your git branch?
Thanks for your patience.
Regards,
Clark Wang
> -Original Mes
Hi Arnd,
Thank you for the patch!
> From: Arnd Bergmann, Sent: Tuesday, December 11, 2018 7:06 PM
> To: Greg Kroah-Hartman
> Cc: Arnd Bergmann ; Yoshihiro Shimoda
> ; Felipe Balbi
> ; Simon Horman ;
> Chris Brandt ;
> linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] u
Hi Tony
> > https://patchwork.kernel.org/patch/10712877/
>
> Hmm, so do you have multiple separate ports at the "&sound" node
> hardware? If so then yeah multiple ports make sense.
>
> But if you only a single physical (I2S?) port at the
> "&sound" node hardware, then IMO you should only ha
> -Original Message-
> From: Mark Brown
> Sent: Tuesday, December 11, 2018 22:26
> To: Clark Wang
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] spi: lpspi: Add cs-gpio support
>
> On Tue, Dec 04, 2018 at 06:24:59AM +, Clark Wang wrote:
>
> >
> -Original Message-
> From: Mark Brown
> Sent: Tuesday, December 11, 2018 22:28
> To: Clark Wang
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] spi: lpspi: enable runtime pm for lpspi
>
> On Tue, Dec 04, 2018 at 06:19:48AM +, Clark Wang wrote:
Commit-ID: 5b20c6fd6a60e182243da31c47f2ebff5b0e3d57
Gitweb: https://git.kernel.org/tip/5b20c6fd6a60e182243da31c47f2ebff5b0e3d57
Author: Yangtao Li
AuthorDate: Tue, 11 Dec 2018 11:37:44 -0500
Committer: Thomas Gleixner
CommitDate: Tue, 11 Dec 2018 18:13:35 -0800
timekeeping: Convert to
On Thu, 29 Nov 2018 15:28:17 -0800, Atish Patra wrote:
> From: Sudeep Holla
>
> The current ARM DT topology description provides the operating system
> with a topological view of the system that is based on leaf nodes
> representing either cores or threads (in an SMT system) and a
> hierarchical
On Tue, Dec 11, 2018 at 4:12 PM Rick Edgecombe
wrote:
>
> This adds two new flags VM_IMMEDIATE_UNMAP and VM_HAS_SPECIAL_PERMS, for
> enabling vfree operations to immediately clear executable TLB entries to freed
> pages, and handle freeing memory with special permissions.
>
> In order to support v
On (12/11/18 18:49), Tetsuo Handa wrote:
>
> We can save lines/size by removing print_prefix() with buf == NULL.
> This patch makes no functional change.
>
> Signed-off-by: Tetsuo Handa
Looks good to me,
Reviewed-by: Sergey Senozhatsky
Shouldn't this also have "Suggested-by: Petr Mladek" ?
On Mon, Dec 03, 2018 at 09:23:42AM -0800, Atish Patra wrote:
> On 12/3/18 8:55 AM, Sudeep Holla wrote:
> > On Thu, Nov 29, 2018 at 03:28:18PM -0800, Atish Patra wrote:
> > > cpu-map binding can be used to described cpu topology for both
> > > RISC-V & ARM. It makes more sense to move the binding to
On Tue, Dec 11, 2018 at 4:12 PM Rick Edgecombe
wrote:
>
> This adds a more efficient x86 architecture specific implementation of
> arch_vunmap, that can free any type of special permission memory with only 1
> TLB
> flush.
>
> In order to enable this, _set_pages_p and _set_pages_np are made non-s
On Wed, Dec 12, 2018 at 01:37:40AM +, He, Bo wrote:
> We reproduced the issue panic in hung_task with the patch "Improve
> diagnostics for failed RCU grace-period start", but unfortunately maybe it's
> due to the loglevel, the show_rcu_gp_kthreads doesn't print any logs, we will
> improve th
> On Dec 11, 2018, at 3:39 PM, Borislav Petkov wrote:
>
>> On Tue, Dec 11, 2018 at 11:12:41PM +, Lendacky, Thomas wrote:
>> It does seem overloaded in that sense, but the feature means that LFENCE
>> is serializing and so can be used in rdtsc_ordered. In the same sense,
>> barrier_nospec is lo
> On Dec 11, 2018, at 3:35 PM, Thorsten Glaser wrote:
>
> Andy Lutomirski dixit:
>
>> What happens if someone adds a struct like:
>>
>> struct nasty_on_x32 {
>> __kernel_long_t a;
>> void * __user b;
>> };
>>
>> On x86_64, that's two 8-byte fields. On x86_32, it's two four-byte
>> fields. On x32
On (12/11/18 19:26), Tetsuo Handa wrote:
> @@ -688,12 +701,21 @@ static ssize_t msg_print_ext_header(char *buf, size_t
> size,
> struct printk_log *msg, u64 seq)
> {
> u64 ts_usec = msg->ts_nsec;
> + char from[18];
[..]
> +#ifdef CONFIG_PRINTK_FROM
>
The function __lock_acquire checks that the nest lock is held passed
in as an argument. The issue with this is that __lock_acquire is used
for internal bookkeeping on lock_release. This produces a false
positive lockdep warning on unlock. Since you explicitly don't need to
hold the nest lock on unl
I'm not sure if I'm breaking any detection with this patch since I
haven't looked at that lockdep code before. I do know that the unlock
order for locks with a nest lock should not matter, though.
Specifically, you should be able to unlock the nest lock followed by
all the locks nested underneath i
Quoting Rob Herring :
On Mon, Dec 10, 2018 at 8:17 PM tom burkart wrote:
Quoting Rob Herring :
> On Mon, Nov 26, 2018 at 10:06 PM tom burkart wrote:
>>
>> Quoting Rob Herring :
>>
>> > On Thu, Nov 22, 2018 at 3:49 AM Tom Burkart wrote:
>> >>
>> >> This patch implements the device tree chan
On (12/12/18 11:25), Sergey Senozhatsky wrote:
> On (12/11/18 19:26), Tetsuo Handa wrote:
> > @@ -688,12 +701,21 @@ static ssize_t msg_print_ext_header(char *buf, size_t
> > size,
> > struct printk_log *msg, u64 seq)
> > {
> > u64 ts_usec = msg->ts_nsec;
> > +
On Thu, Nov 29, 2018 at 03:28:18PM -0800, Atish Patra wrote:
> cpu-map binding can be used to described cpu topology for both
> RISC-V & ARM. It makes more sense to move the binding to document
> to a common place.
>
> The relevant discussion can be found here.
> https://lkml.org/lkml/2018/11/6/19
On Fri, 30 Nov 2018 12:59:09 +0530, Rohit kumar wrote:
> LPASS_Audio_Wrapper_AON clock is on by default. Remove
> it from lpass clock list to avoid voting for it.
>
> Signed-off-by: Rohit kumar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp-pil.txt | 5 ++---
> 1 file changed, 2
On Fri, 30 Nov 2018 15:58:44 +0800, Chen-Yu Tsai wrote:
> The CSI controller found on the H3 (and H5) is a reduced version of the
> one found on the A31. It only has 1 channel, instead of 4 channels for
> time-multiplexed BT.656. Since the H3 is a reduced version, it cannot
> "fallback" to a compat
Commit-ID: 51c3fbd89d7554caa3290837604309f8d8669d99
Gitweb: https://git.kernel.org/tip/51c3fbd89d7554caa3290837604309f8d8669d99
Author: Dan Williams
AuthorDate: Tue, 11 Dec 2018 07:49:39 -0800
Committer: Thomas Gleixner
CommitDate: Tue, 11 Dec 2018 18:28:20 -0800
x86/mm: Fix decoy addr
Andy Lutomirski dixit:
>That’s the thing, though: the whole generic kernel compat
>infrastructure assumes there are at most two ABIs: native and, if
>enabled and relevant, compat. x32 breaks this entirely.
MIPS had o32, n32, n64 since like forever.
ARM has old ABI, EABI and now 64-bit.
Other ar
On Sun, Dec 02, 2018 at 12:40:08PM +0100, Lubomir Rintel wrote:
> The Brownstone board is compatible with "mrvl,mmp2". The actual DTS
> already contains the string -- add it to the binding doc as well.
>
> Signed-off-by: Lubomir Rintel
> ---
> Documentation/devicetree/bindings/arm/mrvl/mrvl.txt
> -Original Message-
> From: Eduardo Valentin
> Sent: 2018年11月30日 1:21
> To: Daniel Lezcano
> Cc: Andy Tang ; rui.zh...@intel.com;
> linux...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3] thermal: qoriq: add multiple sensors support
>
> On Wed, Nov 21, 2018 at
On Tue, Dec 11, 2018 at 03:10:52PM -0800, Andy Lutomirski wrote:
Good evening, I hope the day has gone well for everyone.
> > > > On Dec 11, 2018, at 8:52 AM, Sean Christopherson
> > > > wrote:
> > > >
> > > > This isn't fundamentally different than forcing all EENTER
> > > > calls through the
On 2018-12-11 18:26, Paul Moore wrote:
> On Tue, Dec 11, 2018 at 5:41 PM Richard Guy Briggs wrote:
> > On 2018-12-11 17:31, Paul Moore wrote:
> > > On Mon, Dec 10, 2018 at 5:18 PM Richard Guy Briggs
> > > wrote:
>
> ...
>
> > > > Richard Guy Briggs (4):
> > > > audit: give a clue what CONFIG
On Mon, Dec 10, 2018 at 7:36 PM Adam Thomson
wrote:
>
> On 10 December 2018 09:01, Adam Thomson wrote:
>
> > On 06 December 2018 03:02, Kyle Tso wrote:
> >
> > > Current matching rules ensure that the voltage range of selected
> > > Source Capability is entirely within the range defined in one of
Hi,
On Tue, 11 Dec 2018 13:56:49 +0100 Marcin Wojtas wrote:
> Recent changes in the mvneta driver reworked allocation
> and handling of the ingress buffers to use entire pages.
> Apart from that in SW BM scenario the HW must be informed
> via PRXDQS about the biggest possible incoming buffer
> th
This patch implements the pps echo functionality for pps-gpio, that
sysfs claims is available already.
Configuration is done via device tree bindings.
This patch was originally written by Lukas Senger as part of a masters
thesis project and modified for inclusion into the linux kernel by Tom
Burk
This patch implements the device tree changes required for the pps
echo functionality for pps-gpio, that sysfs claims is available
already.
This patch was originally written by Lukas Senger as part of a masters
thesis project and modified for inclusion into the linux kernel by Tom
Burkart.
Signed
Hi all,
please find attached the PPS-GPIO PPS ECHO implementation patch. The
driver claims to have echo functionality in the sysfs interface but this
functionality is not present. This patch provides this functionality.
Part 1 of the patch change the original driver from the number
based GPIO ABI
This patch changes the GPIO access for the pps-gpio driver from the
integer based ABI to the descriptor based ABI.
Reviewed-by: Philipp Zabel
Signed-off-by: Tom Burkart
---
drivers/pps/clients/pps-gpio.c | 67 +++---
include/linux/pps-gpio.h | 3 +-
2
The fscrypt.git tree has been updated with for the problem. Apologies
for not testing the !CONFIG_FS_VERITY case.
- Ted
On 2018/12/11 下午12:04, Michael S. Tsirkin wrote:
On Tue, Dec 11, 2018 at 11:06:43AM +0800, Jason Wang wrote:
On 2018/12/11 上午9:34, Michael S. Tsirkin wrote:
On Mon, Dec 10, 2018 at 05:44:52PM +0800, Jason Wang wrote:
When we try to do rx busy polling in tx path in commit 441abde4cd84
("net:
On Tue, Dec 11, 2018 at 6:38 PM David Gibson
wrote:
>
> On Tue, Dec 11, 2018 at 08:01:43AM -0600, Bjorn Helgaas wrote:
> > Hi David,
> >
> > I see you're still working on this, but if you do end up going this
> > direction eventually, would you mind splitting this into two patches:
> > 1) rename t
On Wed, Dec 12, 2018 at 3:36 AM Rob Herring wrote:
>
> On Tue, Dec 11, 2018 at 10:03 AM Masahiro Yamada
> wrote:
> >
> > On Wed, Dec 12, 2018 at 12:13 AM Rob Herring wrote:
> >
> > >
> > > > > +$(obj)/%.example.dts: $(src)/%.yaml FORCE
> > > > > + $(call if_changed,chk_binding)
> > > > > +
On Wed, Dec 12, 2018 at 5:24 AM Rob Herring wrote:
>
> This adds the build infrastructure for checking DT binding schema
> documents and validating dts files using the binding schema.
>
> Check DT binding schema documents:
> make dt_binding_check
>
> Build dts files and check using DT binding sche
***Background:
People reported that KASLR may randomly choose some positions
which are located in movable memory regions. This will break memory
hotplug feature and make the movable memory chosen by KASLR can't be
removed.
***Solutions:
Get the information of memory hot-remove, then KASLR will kno
Memory information in SRAT is necessary to fix the conflict between
KASLR and memory-hotremove.
ACPI SRAT (System/Static Resource Affinity Table) shows the details
about memory ranges, including ranges of memory provided by hot-added
memory devices. SRAT is introduced by Root System Description
Po
Memory information in SRAT is necessary to fix the conflict between
KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
When booting form KEXEC/EFI/BIOS, the methods to compute RSDP
are different. When booting from EFI, EFI table points to RSDP.
So parse the EFI table and find the RSDP.
To fix the conflict between KASLR and memory-hotremove, memory
Memory information in SRAT table is necessary to fix the conflict
between KASLR and memory-hotremove. So RSDP and SRAT should be parsed.
When booting form KEXEC/EFI/BIOS, the methods to compute RSDP
are different. When booting from BIO
KASLR randomly chooses some positions which may locate in movable
memory regions. It will break memory hotplug feature and make the
movable memory chosen by KASLR practically immovable.
The solution is to limit KASLR to choose memory regions in immovable
node according to SRAT tables.
When CONFIG_
SRAT should be parsed by RSDP to fix the conflict between KASLR
and memory-hotremove, then find the immovable memory regions and store
them in an array called immovable_mem[]. With immovable_mem[], KASLR
can avoid to extract kernel to specific regions.
Signed-off-by: Chao Fan
---
arch/x86/boot/c
Introduce kstrtoull() from lib/kstrtox.c to boot directory so that code
in boot/ can use kstrtoull() and the old simple_strtoull() can be
replaced.
Signed-off-by: Chao Fan
---
arch/x86/boot/string.c | 137 +
arch/x86/boot/string.h | 2 +
2 files changed,
On Fri, Dec 07, 2018 at 05:47:31PM +0800, Chao Yu wrote:
> On 2018/12/1 4:33, Jaegeuk Kim wrote:
> > On 11/29, Sahitya Tummala wrote:
> >>
> >> On Tue, Nov 27, 2018 at 09:42:39AM +0800, Chao Yu wrote:
> >>> On 2018/11/27 8:30, Jaegeuk Kim wrote:
> On 11/26, Sahitya Tummala wrote:
> > When
On 2018/12/12 11:01, Rong Chen wrote:
>
>
> On 12/11/2018 06:12 PM, Chao Yu wrote:
>> Hi all,
>>
>> The commit only clean up codes which are unused currently, so why we can
>> improve performance with it? could you retest to make sure?
>
> Hi Chao,
>
> the improvement is exist in 0day environme
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Kai-Heng Feng
> Sent: Sunday, December 2, 2018 9:55 PM
> To: Kirsher, Jeffrey T
> Cc: net...@vger.kernel.org; Kai-Heng Feng
> ; intel-wired-...@lists.osuosl.org;
> da...@davemloft.net; linux-kernel@vger.kernel.org
>
On Tue, Dec 11, 2018 at 02:53:12PM +0100, Oscar Salvador wrote:
>v1 -> v2:
>- Keep branch to decrease refcount and print out
> the failed pfn/page
>- Modified changelog per Michal's feedback
>- move put_page() out of the if/else branch
>
>---
>>From f81da873be9a5b78
On 2018/12/12 11:17, Sahitya Tummala wrote:
> On Fri, Dec 07, 2018 at 05:47:31PM +0800, Chao Yu wrote:
>> On 2018/12/1 4:33, Jaegeuk Kim wrote:
>>> On 11/29, Sahitya Tummala wrote:
On Tue, Nov 27, 2018 at 09:42:39AM +0800, Chao Yu wrote:
> On 2018/11/27 8:30, Jaegeuk Kim wrote:
>>
On Wed, 12 Dec 2018, Borislav Petkov wrote:
> On Tue, Dec 11, 2018 at 10:46:16PM +, Lendacky, Thomas wrote:
> > + /*
> > +* At this point, an STIBP mode other than "off" has been set.
> > +* If STIBP support is not being forced, check if STIBP always-on
> > +* is preferred.
> > +
On Wed, Dec 12, 2018 at 11:03:57AM +0800, Jason Wang wrote:
>
> On 2018/12/11 下午12:04, Michael S. Tsirkin wrote:
> > On Tue, Dec 11, 2018 at 11:06:43AM +0800, Jason Wang wrote:
> > > On 2018/12/11 上午9:34, Michael S. Tsirkin wrote:
> > > > On Mon, Dec 10, 2018 at 05:44:52PM +0800, Jason Wang wrote:
Hi,
Cc-ing Peter, Waiman
Hmm, so, how it looks to me
On (12/11/18 20:59), Dmitry Safonov wrote:
> >> [ 87.218483] -> #2 (&port_lock_key){-.-.}:
> >> [ 87.219282]lock_acquire+0x28c/0x2e7
> >> [ 87.219901]_raw_spin_lock_irqsave+0x35/0x49
> >> [ 87.220601]serial8250
v1->v2: delete comments in f2fs.h: "/* bio ordering for NODE/DATA */"
Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 2 --
fs/f2fs/super.c | 5 +
2 files changed, 1 insertion(+), 6 deletions(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
1 - 100 of 1692 matches
Mail list logo
