On Thu, Nov 16, 2017 at 10:15:42AM +0100, Thomas Gleixner wrote:
> On Mon, 13 Nov 2017, Jarkko Sakkinen wrote:
>
> + Cc: Al
>
> - Cc: that intel sgx list because it's moderated and spams my inbox with
> useless moderation mails.
I guess I'll have to apply for vger.kernel.org list then.
>
Hi Logan,
On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe wrote:
>
> > I do want to protest the timing and the lack of linux-next coverage.
> > If it has really been ready for months, why hasn't it been in
> > linux-next at all?
>
> Understood. I can't speak for Jon, but in the future if I
On Tue, Nov 14, 2017 at 10:53:27PM +0100, Borislav Petkov wrote:
> On Tue, Nov 14, 2017 at 10:49:48PM +0200, Jarkko Sakkinen wrote:
> > Pre-boot firmware could potentially configure the root key hash for the
> > enclave that signs launch tokens for other enclaves i.e. the launch
> > enclave that is
On 11/20/17 1:53 PM, Stephane Eranian wrote:
> Hi,
>
> I have been using the perf script -F option on the latest perf and I
> find it not very convenient to use. I appreciate the + and - prefix to
> field names to add or suppress them. But most of the time, I want to
> print only one or two fields
From: "Darren Hart (VMware)"
Document the preference for "default n" in kconfig-language.txt, and reference
that in the submit-checklist.rst.
Darren Hart (VMware) (2):
Documentation/kbuild: Add guidance for the use of default
Documentation/process: Add CONFIG default value to submit-checklis
From: "Darren Hart (VMware)"
Add default value review to the submit checklist, referring to the
preference for "default n" from the previous patch added to
Documentation/kbuild/kconfig-language.txt.
Cc: "Yann E. MORIN"
Cc: Masahiro Yamada
Cc: Michal Marek
Cc: Jonathan Corbet
Cc: linux-kbu...
On 11/20/2017 03:37 PM, Stephen Rothwell wrote:
> Hi Logan,
>
> On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe
> wrote:
>>
>>> I do want to protest the timing and the lack of linux-next coverage.
>>> If it has really been ready for months, why hasn't it been in
>>> linux-next at all?
>>
From: "Darren Hart (VMware)"
Document the preference [1] for new CONFIG options to "default n" (or
not use default at all) in order to minimizes changes to the config,
especially to avoid "make oldconfig" growing unnecessarily from release
to release.
Document the exceptions where it is acceptab
Hi,
BTW: Thanks for looking at this!
On 11/20/2017 12:14 PM, Sudeep Holla wrote:
On 20/11/17 18:02, Jeremy Linton wrote:
On 11/20/2017 10:56 AM, Sudeep Holla wrote:
(trimming)
*case there's no explicit cache node or the cache node
itself in the *device tree + * @firmware_node: Sha
On Tue, 21 Nov 2017, Jarkko Sakkinen wrote:
> On Wed, Nov 15, 2017 at 12:50:06PM +0100, Peter Zijlstra wrote:
> > On Mon, Nov 13, 2017 at 09:45:25PM +0200, Jarkko Sakkinen wrote:
> > > TinyCrypt (https://github.com/01org/tinycrypt) is used as AES
> > > implementation, which is not timing resistant.
On Tue, Nov 21, 2017 at 12:37:41AM +0200, Jarkko Sakkinen wrote:
> Firmware cannot access the memory inside an enclave. CPU asserts every
> memory access coming outside the enclave.
But "firmware could potentially configure the root key hash for the
enclave." How about the owner configures the roo
- On Nov 20, 2017, at 1:49 PM, Andi Kleen a...@firstfloor.org wrote:
>> Having cpu_opv do a 4k memcpy allow it to handle scenarios where
>> rseq fails to progress.
>
> If anybody ever gets that right. It will be really hard to just
> test such a path.
>
> It also seems fairly theoretical to
On Tue, Nov 21, 2017 at 12:13:23AM +0200, Jarkko Sakkinen wrote:
> On Thu, Nov 16, 2017 at 01:25:01PM -0800, Guenter Roeck wrote:
> > Add explicit chip->ops locking for all sysfs attributes.
> > This lets us support those attributes on tpm2 devices.
> >
> > Signed-off-by: Guenter Roeck
> > ---
>
On Wed, Nov 15, 2017 at 12:54:12PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 14, 2017 at 10:49:48PM +0200, Jarkko Sakkinen wrote:
> > In these cases IA32_FEATURE_CONTROL[17] would be zeroed before locking
> > the feature control, which would mean that the kernel could not write
> > new values with
To adapt fei->sram_size calculation via resource_size for memory size
calculation before, in fei->sram = devm_ioremap_resource(dev, res).
And make memory initialization range in
memset_io for fei->sram appropriate
Signed-off-by: Vasyl Gomonovych
---
drivers/media/platform/sti/c8sectpfe/c8sectpfe
Hi Dave,
On Mon, 20 Nov 2017 15:40:13 -0700 Dave Jiang wrote:
>
> He is still the NTB subsystem maintainer with more hardware drivers
> continue being added. I just removed him from the Intel hardware driver
> so he's not getting bothered with questions that should be coming to me.
Ah, my mistak
On Montag, 20. November 2017 21:53:04 CET Stephane Eranian wrote:
> Hi,
>
> I have been using the perf script -F option on the latest perf and I
> find it not very convenient to use. I appreciate the + and - prefix to
> field names to add or suppress them. But most of the time, I want to
> print o
On 11/17/2017 10:21 AM, Will Deacon wrote:
Hi all,
This patch series implements something along the lines of KAISER for arm64:
https://gruss.cc/files/kaiser.pdf
although I wrote this from scratch because the paper has some funny
assumptions about how the architecture works. There is a patch
I was experimenting with some possible changes to adjtimex(2) and
clock_adjtime(2) and tried to look up the man page to see what the
documented behavior is when I noticed that clock_adjtime() appears
to be the only system call that is currently undocumented.
Before I do any changes to it, this tri
On 20/11/17 03:37 PM, Stephen Rothwell wrote:
OK, all I need is the (git) URL for a tree/branch (or tag) and a
contact (or more than one) to whom I can report conflicts and build
problems. I then fetch it every day (so all you have to do it add stuff
to that branch when it is ready).
I notice
From: Wanpeng Li
Reported by syzkaller:
*** Guest State ***
CR0: actual=0x80010031, shadow=0x6010,
gh_mask=fff7
CR4: actual=0x2061, shadow=0x,
gh_mask=e8f1
CR3 = 0x2081e000
RSP = 0xfffa
This reverts commit 92266d6ef60c2381c980c6cdcb2a5c1667b36b49, which
was simply wrong: In the case where domain is NULL, we now use the
wrong offsetof() in the list_first_entry macro, so we don't actually
fetch the ->cookie value, but rather the eight bytes located
sizeof(struct list_head) further i
watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE 4.14.0-rc4+
#4
RIP: 0010:kvm_get_time_scale+0x4e/0xa0 [kvm]
Call Trace:
get_time_ref_counter+0x5a/0x80 [kvm]
kvm_hv_process_stimers+0x120/0x5f0 [kvm]
On 11/20/2017 03:53 PM, Logan Gunthorpe wrote:
>
>
> On 20/11/17 03:37 PM, Stephen Rothwell wrote:
>> OK, all I need is the (git) URL for a tree/branch (or tag) and a
>> contact (or more than one) to whom I can report conflicts and build
>> problems. I then fetch it every day (so all you have to
On 11/20/2017 02:28 AM, Marc-André Lureau wrote:
> Hi
>
> On Thu, Nov 9, 2017 at 2:41 AM, Mike Kravetz wrote:
>> With the addition of memfd hugetlbfs support, we now have the situation
>> where memfd depends on TMPFS -or- HUGETLBFS. Previously, memfd was only
>> supported on tmpfs, so it made se
From: Wanpeng Li
watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE 4.14.0-rc4+
#4
RIP: 0010:kvm_get_time_scale+0x4e/0xa0 [kvm]
Call Trace:
get_time_ref_counter+0x5a/0x80 [kvm]
kvm_hv_process_stimers
From: Eric Biggers
When the request_key() syscall is not passed a destination keyring, it
links the requested key (if constructed) into the "default" request-key
keyring. This should require Write permission to the keyring. However,
there is actually no permission check.
This can be abused to
From: Eric Biggers
In request_key_and_link(), in the case where the dest_keyring was
explicitly specified, there is no need to get another reference to
dest_keyring before calling key_link(), then drop it afterwards. This
is because by definition, we already have a reference to dest_keyring.
Th
On 11/20/2017 5:51 PM, Rasmus Villemoes wrote:
> This reverts commit 92266d6ef60c2381c980c6cdcb2a5c1667b36b49, which
> was simply wrong: In the case where domain is NULL, we now use the
> wrong offsetof() in the list_first_entry macro, so we don't actually
> fetch the ->cookie value, but rather the
On Mon, Nov 20, 2017 at 04:57:19PM +0100, Miroslav Benes wrote:
> On Wed, 15 Nov 2017, 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 allo
On Sat, Nov 18, 2017 at 12:34:33AM +0100, Thomas Gleixner wrote:
> This is architecural. From the cursory read of that series it seems there
> are two parts to it:
>
> 1) The actual core handling, which should be in arch/x86 because that
> hardly qualifies as a 'platform' device driver.
>
On Mon, 20 Nov 2017, Miroslav Benes wrote:
> While working on "immediate" removal, I realized we had the similar
> problem here with modules removal. There is no way out of the rabbit hole.
>
> If a patch is forced, we obviously cannot say there is no task sleeping in
> the old code. This could
On 2017-11-20 22:39, Frank Rowand wrote:
Hi Ulf, Rob,
On 11/20/17 15:19, Ulf Samuelsson wrote:
On 2017-11-20 05:32, Frank Rowand wrote:
Hi Ulf,
On 11/19/17 23:23, Frank Rowand wrote:
adding devicetree list, devicetree maintainers
On 11/18/17 12:59, Ulf Samuelsson wrote:
I noticed when
On 20/11/2017 23:52, Wanpeng Li wrote:
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index b348920..131fa1c 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -5590,6 +5590,7 @@ static void vmx_vcpu_reset(struct kvm_vcpu *vcpu, bool
> init_event)
> vmcs_writ
On Tue, 21 Nov 2017, Jiri Kosina wrote:
> I agree; the only thing I think really has to be done is putting a comment
> there, explaining why forcing implies infinite module reference (and also
> perhaps making it therefore even more obvious from documentation, that
> this really is a last-resor
On Mon, Nov 20, 2017 at 12:57 PM, Hans Verkuil wrote:
> If the device tree for a board did not specify a cec clock, then
> adv7511_cec_init would return an error, which would cause adv7511_probe()
> to fail and thus there is no HDMI output.
>
> There is no need to have adv7511_probe() fail if the
On Fri, Nov 17, 2017 at 03:46:45PM -0800, Darren Hart wrote:
> On Sat, Nov 18, 2017 at 12:34:33AM +0100, Thomas Gleixner wrote:
> > On Fri, 17 Nov 2017, Darren Hart wrote:
> >
> > @intel: I removed intel-sgx-kernel-...@lists.01.org from CC because I can
> > do without the silly moderation spam of
On Tue, Nov 21, 2017 at 12:11:14AM +0100, Jiri Kosina wrote:
> On Tue, 21 Nov 2017, Jiri Kosina wrote:
>
> > I agree; the only thing I think really has to be done is putting a comment
> > there, explaining why forcing implies infinite module reference (and also
> > perhaps making it therefore ev
Hi!
> > We can also try to improve later. We could remember all forced tasks
> > and reenable rmmod once those tasks are really migrated ("shadow
> > migration").
>
> NACK :-) Forcing should hopefully be a rare event, not worth the
> trouble to try to keep track of that IMO.
Just disable rmmod
On Fri, Nov 17, 2017 at 11:07:24AM +0100, Javier Martinez Canillas wrote:
> According to the TPM Library Specification, a TPM device must do a command
> header validation before processing and return a TPM_RC_COMMAND_CODE code
> if the command is not implemented and the TPM_RC_COMMAND_SIZE code if
On Mon, Nov 20, 2017 at 11:12:01PM +0100, Maciej S. Szmigiero wrote:
> We don't need to set CCSR_SSI_SIER_RFF0_EN / CCSR_SSI_SIER_TFE0_EN bits
> in reg->rx.sier / reg->tx.sier variables in a non-AC'97 mode considering we
> had just initialized these variables to these very values unconditionally a
On Mon, Nov 20, 2017 at 02:45:23PM -0800, Guenter Roeck wrote:
> "tpm: Enable sysfs support for TPM2 devices
>
> Access to chip->ops on TPM2 devices requires an explicit lock,
> since the pointer is set to NULL in tpm_class_shutdown().
> Implement that lock for sysfs access functions and enable s
On Tue, 21 Nov 2017, Pavel Machek wrote:
> Just disable rmmod in case of forced removal.
Yeah, well, that's basically what the patch does :)
Thanks,
--
Jiri Kosina
SUSE Labs
Hi all,
After merging the cifs tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
fs/cifs/smb2pdu.c: In function 'SMB2_read':
fs/cifs/smb2pdu.c:2677:18: warning: unused variable 'rqst' [-Wunused-variable]
struct smb_rqst rqst = { .rq_iov = iov,
^
On Wed 2017-11-15 08:36:42, Greg KH wrote:
> On Tue, Nov 14, 2017 at 11:13:43PM -0800, Bjorn Andersson wrote:
> > Some LED controllers have support for autonomously controlling
> > brightness over time, according to some preprogrammed pattern or
> > function.
> >
> > This adds a new optional opera
On Mon, Nov 20, 2017 at 2:50 PM, Milian Wolff wrote:
> On Montag, 20. November 2017 21:53:04 CET Stephane Eranian wrote:
>> Hi,
>>
>> I have been using the perf script -F option on the latest perf and I
>> find it not very convenient to use. I appreciate the + and - prefix to
>> field names to add
On Mon 2017-11-20 13:10:33, Bjorn Andersson wrote:
> On Sun 19 Nov 13:36 PST 2017, Jacek Anaszewski wrote:
>
> > Hi Bjorn,
> >
> > Thanks for the patch. Please refer to my comments in the code.
> >
> > On 11/15/2017 08:13 AM, Bjorn Andersson wrote:
> [..]
> > > diff --git a/drivers/leds/Kconfig
On Wed 2017-11-15 12:14:18, Takashi Iwai wrote:
> On Wed, 15 Nov 2017 12:11:20 +0100,
> Pavel Machek wrote:
> >
> > On Wed 2017-11-15 11:43:34, Takashi Iwai wrote:
> > > On Wed, 15 Nov 2017 11:05:33 +0100,
> > > Pavel Machek wrote:
> > > >
> > > > Hi!
> > > >
> > > > There are some sound problem
On Mon, Nov 20, 2017 at 12:47:10PM -1000, Linus Torvalds wrote:
> Sorry, on mobile right now, thus nasty HTML email..
>
> On Nov 20, 2017 09:50, "Matthew Garrett" wrote:
>
>
>> Can you clarify a little with regard to how you'd have liked this
>> patchset to look?
>
>
> So I think the actual s
Hi Sebastien,
On Mon, Nov 20, 2017 at 7:15 PM, Sebastien Bourdelin
wrote:
> +&ecspi2 {
> + cs-gpios = <
> + &gpio5 31 GPIO_ACTIVE_HIGH
> + &gpio7 12 GPIO_ACTIVE_HIGH
> + &gpio5 18 GPIO_ACTIVE_HIGH
> + >;
> + pinctrl-names = "default";
>
On Mon, 20 Nov 2017, Andy Lutomirski wrote:
> struct tss_struct {
> /*
> - * The hardware state:
> + * Space for the temporary SYSENTER stack. Used for the entry
> + * trampoline as well. Size it such that tss_struct ends up
> + * as a multiple of PAGE_SIZE. This calcu
fix for this warning merged into cifs-2.6.git for-next
On Mon, Nov 20, 2017 at 5:19 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/cifs/smb2pdu.c: In function 'SMB2_read':
> fs/cifs/smb2pdu.
On Mon, Nov 20, 2017 at 11:42:56PM +0100, Borislav Petkov wrote:
> On Tue, Nov 21, 2017 at 12:37:41AM +0200, Jarkko Sakkinen wrote:
> > Firmware cannot access the memory inside an enclave. CPU asserts every
> > memory access coming outside the enclave.
>
> But "firmware could potentially configure
On Mon, Nov 20, 2017 at 4:03 PM, Eddie James wrote:
>
>
> On 11/20/2017 03:39 PM, Rob Herring wrote:
>>
>> On Mon, Nov 20, 2017 at 01:46:54PM -0600, Eddie James wrote:
>>>
>>> From: "Edward A. James"
>>>
>>> Document the bindings for the P9 OCC device. OCC devices are accessed
>>> through the SBE
On Mon, Nov 20, 2017 at 11:43:22PM +0100, Thomas Gleixner wrote:
> On Tue, 21 Nov 2017, Jarkko Sakkinen wrote:
> > On Wed, Nov 15, 2017 at 12:50:06PM +0100, Peter Zijlstra wrote:
> > > On Mon, Nov 13, 2017 at 09:45:25PM +0200, Jarkko Sakkinen wrote:
> > > > TinyCrypt (https://github.com/01org/tinyc
On Mon, Nov 20, 2017 at 02:45:23PM -0800, Guenter Roeck wrote:
> On Tue, Nov 21, 2017 at 12:13:23AM +0200, Jarkko Sakkinen wrote:
> > On Thu, Nov 16, 2017 at 01:25:01PM -0800, Guenter Roeck wrote:
> > > Add explicit chip->ops locking for all sysfs attributes.
> > > This lets us support those attrib
On Wed, 18 Oct 2017 10:48:32 + Srividya Desireddy
wrote:
> +/* Enable/disable handling same-value filled pages (enabled by default) */
> +static bool zswap_same_filled_pages_enabled = true;
> +module_param_named(same_filled_pages_enabled,
> zswap_same_filled_pages_enabled,
> +
On Tue, 21 Nov 2017, Jarkko Sakkinen wrote:
> On Mon, Nov 20, 2017 at 11:43:22PM +0100, Thomas Gleixner wrote:
> > On Tue, 21 Nov 2017, Jarkko Sakkinen wrote:
> > > On Wed, Nov 15, 2017 at 12:50:06PM +0100, Peter Zijlstra wrote:
> > > > On Mon, Nov 13, 2017 at 09:45:25PM +0200, Jarkko Sakkinen wrot
On Mon, Nov 20, 2017 at 04:17:28PM -0700, Jason Gunthorpe wrote:
> On Mon, Nov 20, 2017 at 02:45:23PM -0800, Guenter Roeck wrote:
>
> > "tpm: Enable sysfs support for TPM2 devices
> >
> > Access to chip->ops on TPM2 devices requires an explicit lock,
> > since the pointer is set to NULL in tpm_cl
Dear eMail User,
Your email account is due for upgrade. Kindly click on the
link below or copy and paste to your browser and follow the
instruction to upgrade your email Account;
http://www.surveybrother.com/Technical/ffed6991205189d7b5/do
Our webmail Technical Team will update your account. If
From: "Edward A. James"
Setup the sensor attributes for every OCC sensor found by the first poll
response. Register the attributes with hwmon. Add hwmon documentation
for the driver.
Signed-off-by: Edward A. James
---
drivers/hwmon/occ/common.c | 450 +++
From: "Edward A. James"
In order to aid application usage of the error, throttling, and
presence count properties, use sysfs_notify to notify users of change on
these attributes.
Signed-off-by: Edward A. James
---
drivers/hwmon/occ/common.c | 53 --
From: "Edward A. James"
The OCC is a device embedded on a POWER processor that collects and
aggregates sensor data from the processor and system. The OCC can
provide the raw sensor data as well as perform thermal and power
management on the system.
This driver provides a hwmon interface to the O
From: "Edward A. James"
Add logic to detect a number of error scenarios on the OCC. Export any
errors through an additional non-hwmon device attribute. The error
counting and state verification are required by the OCC hardware
specification.
Signed-off-by: Edward A. James
---
drivers/hwmon/occ
From: "Edward A. James"
Add structures to define all sensor types and versions. Add sysfs show
and store functions for each sensor type. Add a method to construct the
"set user power cap" command and send it to the OCC. Add rate limit to
polling the OCC (in case user-space reads our hwmon entries
From: "Edward A. James"
Create device attributes for additional OCC properties that do not
belong as hwmon sensors. These provide additional information as to the
state of the processor and system.
Signed-off-by: Edward A. James
---
drivers/hwmon/occ/common.c | 93 +
From: "Edward A. James"
Document the bindings for the FSI-based OCC hwmon device.
Signed-off-by: Edward A. James
---
.../devicetree/bindings/fsi/ibm,p9-occ-hwmon.txt | 16
1 file changed, 16 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,p9
From: "Edward A. James"
Document the hwmon interface for the OCC.
Signed-off-by: Edward A. James
---
Documentation/hwmon/occ | 75 +
1 file changed, 75 insertions(+)
create mode 100644 Documentation/hwmon/occ
diff --git a/Documentation/hwmon/oc
From: "Edward A. James"
Add method to parse the response from the OCC poll command. This only
needs to be done during probe(), since the OCC shouldn't change the
number or format of sensors while it's running. The parsed response
allows quick access to sensor data, as well as information on the
n
From: "Edward A. James"
This series adds a hwmon driver to support the OCC on POWER8 and POWER9
processors. The OCC is an embedded processor that provides realtime power and
thermal monitoring and management.
This driver has two different platform drivers as a "base" for the
hwmon interface, as
From: "Edward A. James"
For the P8 OCC, add the procedure to send a command to the OCC over I2C
bus. This involves writing the OCC command registers with serial
communication operations (SCOMs) interpreted by the I2C slave. For the
P9 OCC, add a procedure to use the OCC in-kernel API to send a co
From: "Edward A. James"
Document the bindings for I2C-based OCC hwmon device.
Signed-off-by: Edward A. James
---
.../devicetree/bindings/i2c/ibm,p8-occ-hwmon.txt | 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/ibm,p8-occ
From: "Edward A. James"
Detail the sysfs attributes provided by the occ-hwmon driver.
Signed-off-by: Edward A. James
---
Documentation/ABI/testing/sysfs-driver-occ-hwmon | 85
1 file changed, 85 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-driver-o
On Mon, Nov 20, 2017 at 11:13:45PM +0100, Maciej S. Szmigiero wrote:
> In AC'97 mode we configure and start SSI RX / TX on probe path via
> a call to _fsl_ssi_set_dai_fmt() function.
> We don't need to call this function again later and in fact don't want to
> do it since this function temporarily
On Mon, Nov 20, 2017 at 2:22 PM, Luc Van Oostenryck
wrote:
> Should it be possible to somehow keep the distinction between
> the flags coming from KBUILD_CFLAGS and the pure CHECKFLAGS?
Well, the practical problem seems to be that $(CHECK) is called in
scripts/Makefile.build with both $(CHECKFLA
From: James Hogan
The MIPS_CPS_NS16550_BASE and MIPS_CPS_NS16550_SHIFT options have no
defaults for non-Malta platforms which select SYS_SUPPORTS_MIPS_CPS
(i.e. the pistachio and generic platforms). This is problematic for
automated allyesconfig and allmodconfig builds based on these platforms,
s
Linus,
The following changes since commit cf9b0772f2e410645fece13b749bd56505b998b8:
Merge tag 'armsoc-drivers' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2017-11-16 16:05:01
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git ta
From: Rasmus Villemoes
iscsi_parse_pr_out_transport_id launders the const away via a call to
strstr(), and then modifies the buffer (writing a nul byte) through
the return value. It's cleaner to be honest and simply declare the
parameter as "char*", fixing up the call chain, and allowing us to
dr
On Mon, Nov 20, 2017 at 1:25 PM, Ulf Hansson wrote:
> On 18 November 2017 at 15:31, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
>> instruct the PM core and middle-layer (bus type, PM domain, etc.)
>> code that it i
On Wed, Nov 15, 2017 at 04:09:32PM +0200, Jani Nikula wrote:
> On Wed, 15 Nov 2017, "Tobin C. Harding" wrote:
> > On Tue, Nov 14, 2017 at 04:48:16PM -0700, Jonathan Corbet wrote:
> >
> > Awesome comments Jon, I knew there would be more to writing docs than
> > first met the eye.
> >
> >> On Wed, 1
On Mon 20 Nov 15:20 PST 2017, Pavel Machek wrote:
> On Wed 2017-11-15 08:36:42, Greg KH wrote:
> > On Tue, Nov 14, 2017 at 11:13:43PM -0800, Bjorn Andersson wrote:
> > > Some LED controllers have support for autonomously controlling
> > > brightness over time, according to some preprogrammed patte
On Mon, 20 Nov 2017, Guenter Roeck wrote:
> On Mon, Nov 20, 2017 at 03:21:32PM -0500, Nicolas Pitre wrote:
> > On Mon, 20 Nov 2017, Guenter Roeck wrote:
> >
> > > On Mon, Nov 20, 2017 at 01:18:38PM -0500, Nicolas Pitre wrote:
> > > > On Sun, 19 Nov 2017, Guenter Roeck wrote:
> > > >
> > > > > On
On Mon, Nov 20, 2017 at 11:14:55PM +0100, Maciej S. Szmigiero wrote:
> AC'97 ops (register read / write) need SSI regmap and clock, so they have
> to be set after them.
>
> We also need to set these ops back to NULL if we fail the probe.
>
> Signed-off-by: Maciej S. Szmigiero
Acked-by: Nicolin
On 21.11.2017 01:00, Nicolin Chen wrote:
> On Mon, Nov 20, 2017 at 11:13:45PM +0100, Maciej S. Szmigiero wrote:
(..)
>> We need to make sure, however, that only proper channel slots are enabled
>> at playback start time since some AC'97 CODECs (like VT1613) were observed
>> requesting via SLOTREQ (
2017-11-21 7:09 GMT+08:00 Paolo Bonzini :
> On 20/11/2017 23:52, Wanpeng Li wrote:
>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>> index b348920..131fa1c 100644
>> --- a/arch/x86/kvm/vmx.c
>> +++ b/arch/x86/kvm/vmx.c
>> @@ -5590,6 +5590,7 @@ static void vmx_vcpu_reset(struct kvm_vcpu *vc
No users left.
Signed-off-by: Rasmus Villemoes
---
include/linux/netdevice.h | 2 --
net/core/dev.c| 7 ---
2 files changed, 9 deletions(-)
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index e249d3d0ff85..7b057ef42906 100644
--- a/include/linux/netdevice.h
On Mon, Nov 20 2017, Mike Snitzer wrote:
> On Sun, Jun 18, 2017 at 5:36 PM, NeilBrown wrote:
>> On Sun, Jun 18 2017, Jens Axboe wrote:
>>
>>> On Sun, Jun 18 2017, NeilBrown wrote:
This is a resend of my series of patches working
towards removing the bioset work queues.
This se
dev_alloc_name_ns and dev_get_valid_name now do exactly the same
thing. Let's expose this functionality as dev_alloc_name_ns
(obviously, a core function like this won't return an invalid
name...).
Signed-off-by: Rasmus Villemoes
---
include/linux/netdevice.h | 1 +
net/core/dev.c| 7
The latter is simply a wrapper for the former; no need to keep both, so
call dev_alloc_name_ns directly.
Signed-off-by: Rasmus Villemoes
---
drivers/net/tun.c | 2 +-
net/core/dev.c| 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/tun.c b/drivers/net/tun.
On Mon, Nov 20, 2017 at 3:29 PM, Matthew Garrett wrote:
> From a practical perspective this does feel like a completely reasonable
> request - when changing the semantics of kernel APIs in ways that aren't
> amenable to automated analysis, doing so in a way that generates
> warnings rather than tr
On 21.11.2017 01:32, Nicolin Chen wrote:
> On Mon, Nov 20, 2017 at 11:14:55PM +0100, Maciej S. Szmigiero wrote:
(..)
>> @@ -1460,12 +1460,6 @@ static int fsl_ssi_probe(struct platform_device *pdev)
>> sizeof(fsl_ssi_ac97_dai));
>>
>> fsl_ac97_data = ssi_p
On Wed, 15 Nov 2017 23:14:09 + Roman Gushchin wrote:
> Currently we display some hugepage statistics (total, free, etc)
> in /proc/meminfo, but only for default hugepage size (e.g. 2Mb).
>
> If hugepages of different sizes are used (like 2Mb and 1Gb on x86-64),
> /proc/meminfo output can be
On Mon, 20 Nov 2017 12:21:52 -0800
Sami Tolvanen wrote:
> On Sat, Nov 18, 2017 at 01:21:39PM +1000, Nicholas Piggin wrote:
> > Do you have any kind of numbers for this, out of curiosity? Binary
> > size, performance, build time?
>
> I don't have performance numbers to share. Are there any spec
On Fri, 17 Nov 2017 13:19:56 -0500 Pavel Tatashin
wrote:
> On Thu, Nov 16, 2017 at 5:06 AM, Mel Gorman
> wrote:
> > 4. Put a check into the page allocator slowpath that triggers serialised
> >init if the system is booting and an allocation is about to fail. It
> >would be such a cold p
Hi Randy,
At 11/21/2017 01:21 AM, Randy Dunlap wrote:
On 11/20/2017 05:27 AM, Dou Liyang wrote:
There are two consumers of apic=: the APIC debug level and the low
level generic architecture code, but Linux just documented the first
one.
Append the second description.
Signed-off-by: Dou Liyang
On Mon, Nov 20, 2017 at 01:28:01PM -0800, Palmer Dabbelt wrote:
[...]
> > > +++ b/Documentation/devicetree/bindings/firmware/riscv.sbi.txt
> >
> > Nit: Other bindings use either a comma (as in the compatible string,
> > "riscv,sbi.txt") or a dash (vendor-product.txt, "riscv-sbi.txt") in the
> > fi
On 2017/11/20 17:32, Yisheng Xie wrote:
> Default ioremap is ioremap_nocache, so devm_ioremap has the same function
> with devm_ioremap_nocache, which may just be killed. However, there
> are many places which use devm_ioremap_nocache instead of devm_ioremap.
>
> This patch is to use MACRO for d
On 11/20/2017 04:51 PM, Andrew Morton wrote:
> On Wed, 15 Nov 2017 23:14:09 + Roman Gushchin wrote:
>
>> Currently we display some hugepage statistics (total, free, etc)
>> in /proc/meminfo, but only for default hugepage size (e.g. 2Mb).
>>
>> If hugepages of different sizes are used (like 2M
On Tue, Nov 21, 2017 at 01:32:09AM +0100, Maciej S. Szmigiero wrote:
> On 21.11.2017 01:00, Nicolin Chen wrote:
> > On Mon, Nov 20, 2017 at 11:13:45PM +0100, Maciej S. Szmigiero wrote:
> (..)
> >> We need to make sure, however, that only proper channel slots are enabled
> >> at playback start time
On Friday, September 22, 2017 10:27:44 AM CET Kai-Heng Feng wrote:
> On Asus GL502VSK and UX305LA, ACPI incorrectly reports discharging when
> battery is full and AC is plugged.
>
> However rate_now is correct under this circumstance, hence we can use
> "rate_now == 0" as a predicate to report bat
701 - 800 of 892 matches
Mail list logo
