On Tue, May 16, 2017 at 02:28:42PM -0500, Tom Lendacky wrote:
> It's most problematic when CONFIG_AMD_MEM_ENCRYPT is not defined since
> we never include an asm/ version from the linux/ path. I could create
> a mem_encrypt.h in include/asm-generic/ that contains the info that
> is in the !CONFIG_A
On Sun, 2017-05-14 at 21:51 +0200, Peter Rosin wrote:
> From: Peter Rosin
>
> Add a new minimalistic subsystem that handles multiplexer controllers.
> When multiplexers are used in various places in the kernel, and the
> same multiplexer controller can be used for several independent things,
> th
On Sun, 2017-05-14 at 21:51 +0200, Peter Rosin wrote:
> From: Peter Rosin
>
> The driver builds a single multiplexer controller using a number
> of gpio pins. For N pins, there will be 2^N possible multiplexer
> states. The GPIO pins can be connected (by the hardware) to several
> multiplexers, w
Hi Greg,
Thanks! I add linux-doc@vger.kernel.org and Johnathan
to CC for info.
-- Markus --
Am 17.05.2017 um 11:54 schrieb :
>
> This is a note to let you know that I've just added the patch titled
>
>doc-rst: fixed kernel-doc directives in usb/typec.rst
>
> to my usb git tree which can
Mauro Carvalho Chehab writes:
> The USB gadget documentation is not at DocBook anymore.
> The main file was converted to ReST, and stored at
> Documentation/driver-api/usb/gadget.rst, but there are
> still several plain text files related to gadget under
> Documentation/usb.
>
> So, be generic an
On 2017-05-11 10:32, Martin Kepplinger wrote:
> On 2017-05-08 18:11, Rob Herring wrote:
>> On Tue, May 02, 2017 at 05:00:59PM +0200, Martin Kepplinger wrote:
>>> The datasheet and application note does not mention an allowed range for
>>> the M09_REGISTER_THRESHOLD parameter. One of our customers n
On Sat, May 13, 2017 at 03:49:17PM +0200, Markus Heiser wrote:
> Even if this file is not yet included in any toctree, it is parsed by
> Sphinx since it is named '.rst'. This patch fixes the following two
> ERRORs from Sphinx build:
>
> Documentation/usb/typec.rst:116: ERROR: Error in "kernel-doc"
remove __ARCH_WANT_UNLOCKED_CTXSW macro because it's no longer
exist after 3.17.8 kernel release.
Signed-off-by: Karim Eshapa
---
Documentation/scheduler/sched-arch.txt | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/Documentation/scheduler/sched-arch.txt
b/
On Wed, May 17, 2017 at 08:03:03AM +1000, Balbir Singh wrote:
> On Sat, May 13, 2017 at 2:42 AM, Johannes Weiner wrote:
> > On Fri, May 12, 2017 at 12:25:22PM +1000, Balbir Singh wrote:
> >>
> >> It sounds like memcg accumlates both global and memcg reclaim driver
> >> counts -- is this what we wa
On Tue, May 16, 2017 at 09:16:35AM -0300, Mauro Carvalho Chehab wrote:
> DocBook is mentioned several times at the documentation. Update
> the obsolete references from it at the DocBook.
>
> Acked-by: SeongJae Park
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Bjorn Helgaas# for PCI/MSI-
On 5/15/2017 1:35 PM, Borislav Petkov wrote:
On Tue, Apr 18, 2017 at 04:19:21PM -0500, Tom Lendacky wrote:
Boot data (such as EFI related data) is not encrypted when the system is
booted because UEFI/BIOS does not run with SME active. In order to access
this data properly it needs to be mapped d
On Tue, Apr 18, 2017 at 04:21:21PM -0500, Tom Lendacky wrote:
> Provide support so that kexec can be used to boot a kernel when SME is
> enabled.
>
> Support is needed to allocate pages for kexec without encryption. This
> is needed in order to be able to reboot in the kernel in the same manner
>
On Mon, May 15, 2017 at 09:34:05AM -0400, Waiman Long wrote:
> The cgroup_procs_write_start() took a reference to the task structure
> which was not properly released within cgroup_procs_write() and so
> on. So a put_task_struct() call is added to cgroup_procs_write_finish()
> to match the get_task
Hello,
On Mon, May 15, 2017 at 09:34:06AM -0400, Waiman Long wrote:
> The kill_css() function may be called more than once under the condition
> that the css was killed but not physically removed yet followed by the
> removal of the cgroup that is hosting the css. This patch prevents any
> harmm f
On Sat, May 13, 2017 at 7:51 AM, Kees Cook wrote:
> Adjusts for ReST markup and moves under LSM admin guide.
>
> Cc: Paul Moore
> Signed-off-by: Kees Cook
> ---
> .../SELinux.txt => admin-guide/LSM/SELinux.rst}| 18
> --
> Documentation/admin-guide/LSM/index.rst
On 05/17/2017 03:23 PM, Tejun Heo wrote:
> Hello,
>
> On Mon, May 15, 2017 at 09:34:06AM -0400, Waiman Long wrote:
>> The kill_css() function may be called more than once under the condition
>> that the css was killed but not physically removed yet followed by the
>> removal of the cgroup that is h
On 5/16/2017 3:36 AM, Borislav Petkov wrote:
On Tue, Apr 18, 2017 at 04:19:30PM -0500, Tom Lendacky wrote:
The SMP MP-table is built by UEFI and placed in memory in a decrypted
state. These tables are accessed using a mix of early_memremap(),
early_memunmap(), phys_to_virt() and virt_to_phys().
Hello, Waiman.
On Mon, May 15, 2017 at 09:34:07AM -0400, Waiman Long wrote:
> The debug cgroup currently resides within cgroup-v1.c and is enabled
> only for v1 cgroup. To enable the debug cgroup also for v2, it
> makes sense to put the code into its own file as it will no longer
> be v1 specific.
On Wed, May 17, 2017 at 04:24:32PM -0400, Waiman Long wrote:
> On 05/17/2017 03:23 PM, Tejun Heo wrote:
> > Hello,
> >
> > On Mon, May 15, 2017 at 09:34:06AM -0400, Waiman Long wrote:
> >> The kill_css() function may be called more than once under the condition
> >> that the css was killed but not
Hello,
On Mon, May 15, 2017 at 09:34:08AM -0400, Waiman Long wrote:
> The reference count in the css_set data structure was used as a
> proxy of the number of tasks attached to that css_set. However, that
> count is actually not an accurate measure especially with thread mode
> support. So a new v
Hello,
On Mon, May 15, 2017 at 09:34:09AM -0400, Waiman Long wrote:
> Besides supporting cgroup v2 and thread mode, the following changes
> are also made:
> 1) current_* cgroup files now resides only at the root as we don't
> need duplicated files of the same function all over the cgroup
>
Hello, Waiman.
On Mon, May 15, 2017 at 09:34:10AM -0400, Waiman Long wrote:
> The current thread mode semantics aren't sufficient to fully support
> threaded controllers like cpu. The main problem is that when thread
> mode is enabled at root (mainly for performance reason), all the
> non-threaded
I came to this patch series when wanted to do two things:
- use UAC1 as virtual ALSA sound card on gadget side,
just like UAC2 is used so it's possible to do rate
resampling
- have both playback/capture support in UAC1
Since I wanted to have same behavior for both UAC1/UAC2,
obviously I've
This patch adds a new function 'f_uac1_acard'
(f_uac1 with virtual "ALSA card") that
uses recently created u_audio API. Comparing
to legacy f_uac1 function implementation it
doesn't require any real Audio codec to be
present on the device. In f_uac1_acard audio
streams are simply sinked to and sour
Simplify f_uac2 by removing platform driver/device
creation; use composite's usb_gadget device as
parent for sound card and for debug prints.
This removes extra layer of code without any functional
change.
Signed-off-by: Ruslan Bilovol
---
drivers/usb/gadget/function/f_uac2.c | 107 +
Abstract the peripheral side ALSA sound card code from
the f_uac2 function into a component that can be called
by various functions, so the various flavors can be split
apart and selectively reused.
Visible changes:
- add uac_params structure to pass audio paramteres for
g_audio_setup
- make
On Tue, May 16, 2017 at 08:02:17PM +0200, Luis R. Rodriguez wrote:
> On Wed, Jan 11, 2017 at 09:08:57PM +0100, Luis R. Rodriguez wrote:
> > On Tue, Jan 10, 2017 at 07:57:10PM +0100, Luis R. Rodriguez wrote:
> > > On Fri, Dec 16, 2016 at 09:05:00AM +0100, Luis R. Rodriguez wrote:
> > > > On Thu, Dec
On 05/16, Guenter Roeck wrote:
0day bot applied your patchset on top of commit 6eaaea1 ("hwmon: (pmbus)
Add client driver for IR35221"),
is it wrong or you have some prerequisite patches?
>>
>>Thanks for the info, seems we need to improve the kbuild bot by pulling the
>>latest tree bef
On 05/17/2017 08:05 PM, Ye Xiaolong wrote:
On 05/16, Guenter Roeck wrote:
0day bot applied your patchset on top of commit 6eaaea1 ("hwmon: (pmbus) Add client
driver for IR35221"),
is it wrong or you have some prerequisite patches?
Thanks for the info, seems we need to improve the kbuild bot b
This patch have minor updates in Documentation for arm64i as
relocatable kernel.
Also this patch updates documentation for using uncompressed
image "Image" which is used for ARM64.
Signed-off-by: Bharat Bhushan
---
Documentation/kdump/kdump.txt | 10 --
1 file changed, 8 insertions(+), 2
On Thu, May 11, 2017 at 02:53:43PM +0300, Gilad Ben-Yossef wrote:
> drbg_kcapi_sym_ctr() was using wait_for_completion_interruptible() to
> wait for completion of async crypto op but if a signal occurs it
> may return before DMA ops of HW crypto provider finish, thus
> corrupting the output buffer.
On 05/18/17 at 11:03am, Bharat Bhushan wrote:
> This patch have minor updates in Documentation for arm64i as
> relocatable kernel.
> Also this patch updates documentation for using uncompressed
> image "Image" which is used for ARM64.
>
> Signed-off-by: Bharat Bhushan
> ---
> Documentation/kdump
Add Takahiro and Pratyush, they should be able to review the arm64 part.
On 05/18/17 at 11:03am, Bharat Bhushan wrote:
> This patch have minor updates in Documentation for arm64i as
> relocatable kernel.
> Also this patch updates documentation for using uncompressed
> image "Image" which is used f
> -Original Message-
> From: Dave Young [mailto:dyo...@redhat.com]
> Sent: Thursday, May 18, 2017 11:29 AM
> To: Bharat Bhushan
> Cc: b...@redhat.com; vgo...@redhat.com; cor...@lwn.net;
> ke...@lists.infradead.org; linux-doc@vger.kernel.org; linux-
> ker...@vger.kernel.org; takahiro.aka.
34 matches
Mail list logo
