Re: [PATCH v2] Documentation: typec.rst: Use literal-block element with ascii art

On Wed, Apr 25, 2018 at 04:47:01PM +0300, Jani Nikula wrote: > On Fri, 06 Apr 2018, Heikki Krogerus wrote: > > Using reStructuredText literal-block element with ascii-art. > > That prevents the ascii art from being processed as > > reStructuredText. > > > >

Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On Mon, Apr 23, 2018 at 02:17:28PM -0700, Randy Dunlap wrote: > On 04/23/18 12:53, Greg KH wrote: > > On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: > >> On 04/23/18 07:46, Bryant G. Ly wrote: > >>> This driver is a logical device which provi

Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver

On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: > On 04/23/18 07:46, Bryant G. Ly wrote: > > This driver is a logical device which provides an > > interface between the hypervisor and a management > > partition. > > > > This driver is to be used for the POWER Virtual > > Management

Re: [PATCH] Documentation: fix reST markup error in driver-api/usb/typec.rst

On Sun, Apr 08, 2018 at 10:47:12AM +0800, changbin...@intel.com wrote: > From: Changbin Du > > There is an format error in driver-api/usb/typec.rst that breaks sphinx > docs building. > > reST markup error: >

Re: make xmldocs failed with error after 4.17 merge period

On Fri, Apr 06, 2018 at 11:15:55AM +0300, Heikki Krogerus wrote: > On Fri, Apr 06, 2018 at 09:57:34AM +0200, Greg KH wrote: > > On Fri, Apr 06, 2018 at 10:51:09AM +0300, Heikki Krogerus wrote: > > > On Fri, Apr 06, 2018 at 12:38:42PM +0900, Masanari Iida wrote: > > > &g

Re: make xmldocs failed with error after 4.17 merge period

On Fri, Apr 06, 2018 at 10:51:09AM +0300, Heikki Krogerus wrote: > On Fri, Apr 06, 2018 at 12:38:42PM +0900, Masanari Iida wrote: > > After merge following patch during 4.17 merger period, > > make xmldocs start to fail with error. > > > > [bdecb33af34f79cbfbb656661210f77c8b8b5b5f] > > usb:

Re: [PATCH] [v2] docs: clarify security-bugs disclosure policy

On Wed, Mar 07, 2018 at 01:46:24PM -0800, Dave Hansen wrote: > > From: Dave Hansen > > I think we need to soften the language a bit. It might scare folks > off, especially the: > >We prefer to fully disclose the bug as soon as possible. > > which is not

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

On Wed, Feb 21, 2018 at 12:42:30PM -0800, Jae Hyun Yoo wrote: > On 2/21/2018 9:58 AM, Greg KH wrote: > > On Wed, Feb 21, 2018 at 08:15:59AM -0800, Jae Hyun Yoo wrote: > > > This commit adds driver implementation for PECI bus into linux > > > driver framework. > >

Re: [PATCH v2 1/8] [PATCH 1/8] drivers/peci: Add support for PECI bus driver core

On Wed, Feb 21, 2018 at 08:15:59AM -0800, Jae Hyun Yoo wrote: > This commit adds driver implementation for PECI bus into linux > driver framework. > > Signed-off-by: Jae Hyun Yoo > --- Why is there no other Intel developers willing to review and sign off on this

Re: [PATCH] Staging: netlogic: platform_net: Fixed '(' at the EOL

On Tue, Jan 16, 2018 at 07:33:03PM +0530, Naveen Panwar wrote: > Hi Guys, > > I submitted a new patch with the suggestions from Al Viro, did you guys > check it? I do not see any patch from my in my queue :( -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Thu, Jan 11, 2018 at 07:56:51PM +1100, Benjamin Herrenschmidt wrote: > On Thu, 2018-01-11 at 08:30 +0100, Greg KH wrote: > > 4.13? Why that kernel? It too is obsolete and insecure and > > unsupported. > > Haha, it's n-1. come on :-) And, if you use it in a devic

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Thu, Jan 11, 2018 at 12:28:48AM -0800, Joel Stanley wrote: > On Wed, Jan 10, 2018 at 11:30 PM, Greg KH <gre...@linuxfoundation.org> wrote: > > On Wed, Jan 10, 2018 at 01:46:34PM -0800, Jae Hyun Yoo wrote: > >> Thanks for your pointing it out and I totally agre

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Wed, Jan 10, 2018 at 01:46:34PM -0800, Jae Hyun Yoo wrote: > On 1/10/2018 12:27 PM, Greg KH wrote: > > On Wed, Jan 10, 2018 at 11:30:05AM -0800, Jae Hyun Yoo wrote: > > > On 1/10/2018 11:17 AM, Greg KH wrote: > > > > On Wed, Jan 10, 2018 at 11:14:34AM -0800, Jae

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Wed, Jan 10, 2018 at 11:30:05AM -0800, Jae Hyun Yoo wrote: > On 1/10/2018 11:17 AM, Greg KH wrote: > > On Wed, Jan 10, 2018 at 11:14:34AM -0800, Jae Hyun Yoo wrote: > > > On 1/10/2018 2:17 AM, Greg KH wrote: > > > > On Tue, Jan 09, 2018 at 02:31:20PM -0800, Jae

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Wed, Jan 10, 2018 at 11:14:34AM -0800, Jae Hyun Yoo wrote: > On 1/10/2018 2:17 AM, Greg KH wrote: > > On Tue, Jan 09, 2018 at 02:31:20PM -0800, Jae Hyun Yoo wrote: > > > From: Jae Hyun Yoo <jae.hyun@intel.com> > > > > > > Hello, > > &

Re: [PATCH linux dev-4.10 3/6] drivers/misc: Add driver for Aspeed PECI and generic PECI headers

On Tue, Jan 09, 2018 at 02:31:23PM -0800, Jae Hyun Yoo wrote: > This commit adds driver implementation for Aspeed PECI. Also adds > generic peci.h and peci_ioctl.h files to provide compatibility > to peci drivers that can be implemented later e.g. Nuvoton's BMC > SoC family. We don't add code

Re: [PATCH linux dev-4.10 3/6] drivers/misc: Add driver for Aspeed PECI and generic PECI headers

On Tue, Jan 09, 2018 at 02:31:23PM -0800, Jae Hyun Yoo wrote: > +#pragma pack(push, 1) > +struct peci_xfer_msg { > + unsigned char client_addr; > + unsigned char tx_len; > + unsigned char rx_len; > + unsigned char tx_buf[MAX_BUFFER_SIZE]; > + unsigned char

Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers

On Tue, Jan 09, 2018 at 02:31:20PM -0800, Jae Hyun Yoo wrote: > From: Jae Hyun Yoo > > Hello, > > This patch set provides support for PECI of AST2400/2500 which can give us > PECI > functionalities such as temperature monitoring, platform manageability, > processor

Re: [PATCH v3] arm64: v8.4: Support for new floating point multiplication instructions

On Fri, Jan 05, 2018 at 09:22:54AM +0800, gengdongjiu wrote: > Hi will/catalin > > On 2017/12/13 18:09, Suzuki K Poulose wrote: > > On 13/12/17 10:13, Dongjiu Geng wrote: > >> ARM v8.4 extensions add new neon instructions for performing a > >> multiplication of each FP16 element of one vector

Re: device attribute documentation

On Thu, Dec 14, 2017 at 10:09:44AM -0700, Jonathan Corbet wrote: > On Thu, 14 Dec 2017 15:30:13 +0100 (CET) > Julia Lawall wrote: > > [CC += Greg in case he disagrees] > > > My intern, Aishwarya Pant, is looking into how to improve the > > documentation of device

Re: [PATCH v2] usb: core: Add "quirks" parameter for usbcore

On Wed, Dec 06, 2017 at 06:26:21PM +0800, Kai-Heng Feng wrote: > Trying quirks in usbcore needs to rebuild the driver or the entire > kernel if it's builtin. It can save a lot of time if usbcore has similar > ability like "usbhid.quirks=" and "usb-storage.quirks=". > > Rename the original quirk

Re: [PATCH] usb: core: Add "quirks" parameter for usbcore

On Wed, Dec 06, 2017 at 05:09:32PM +0800, Kai-Heng Feng wrote: > +/* Works only for digits and letters, but small and fast */ > +#define TOLOWER(x) ((x) | 0x20) What is wrong with the in-kernel version of tolower()? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] mod_devicetable.h: Fix docs build warnings

On Mon, Jul 24, 2017 at 01:54:17PM -0600, Jonathan Corbet wrote: > Commit 0afef45654ae908536278ecb143ded5bbc713391 (staging: fsl-mc: add > support for device table matching) added kerneldoc comments for two > nonexistent structure fields, leading to these warnings in the docs build: > >

Re: [PATCH v2 6/8] usb: gadget: f_acm: add an ioctl to get the current line coding

On Tue, Jun 13, 2017 at 09:52:12AM +0300, Tal Shorer wrote: > The user can issue USB_F_GET_LINE_CODING to get the current line coding > as set by the host (or the default if unset yet). > > Signed-off-by: Tal Shorer > --- > Documentation/ioctl/ioctl-number.txt | 1 + >

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 06:20:17PM +, Kershner, David A wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Tuesday, June 6, 2017 11:06 AM > > To: Kershner, David A <david.kersh...@unisys.com> > &

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 08:52:27AM -0700, Joe Perches wrote: > On Tue, 2017-06-06 at 17:39 +0200, Greg KH wrote: > > On Tue, Jun 06, 2017 at 08:33:49AM -0700, Joe Perches wrote: > > > On Tue, 2017-06-06 at 16:53 +0200, Greg KH wrote: > > > > On Tue, Jun 06, 2017 at 0

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 08:33:49AM -0700, Joe Perches wrote: > On Tue, 2017-06-06 at 16:53 +0200, Greg KH wrote: > > On Tue, Jun 06, 2017 at 04:49:09PM +0200, Greg KH wrote: > > > I noticed that in drivers/staging/unisys/visorbus/visorbus_main.c, you > > > have 2 tabs

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 04:54:30PM +0200, Greg KH wrote: > On Tue, Jun 06, 2017 at 04:53:22PM +0200, Greg KH wrote: > > On Tue, Jun 06, 2017 at 04:49:09PM +0200, Greg KH wrote: > > > On Mon, Jun 05, 2017 at 04:07:29PM -0400, David Kershner wrote: > > > > This patchse

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 04:53:22PM +0200, Greg KH wrote: > On Tue, Jun 06, 2017 at 04:49:09PM +0200, Greg KH wrote: > > On Mon, Jun 05, 2017 at 04:07:29PM -0400, David Kershner wrote: > > > This patchset moves drivers/staging/unisys/include to > > > include/linux/

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 04:49:09PM +0200, Greg KH wrote: > On Mon, Jun 05, 2017 at 04:07:29PM -0400, David Kershner wrote: > > This patchset moves drivers/staging/unisys/include to > > include/linux/visorbus, and moves drivers/staging/unisys/visorbus to > > drivers/virt/visor

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Mon, Jun 05, 2017 at 04:07:29PM -0400, David Kershner wrote: > This patchset moves drivers/staging/unisys/include to > include/linux/visorbus, and moves drivers/staging/unisys/visorbus to > drivers/virt/visorbus. Um, are you thinking it is ready to be moved? Have you asked for another review?

Re: [PATCH v4 0/3] USB Audio Gadget refactoring

On Mon, Jun 05, 2017 at 12:22:13PM +0300, Felipe Balbi wrote: > > Hi, > > Ruslan Bilovol writes: > >> Ruslan Bilovol writes: > >>> I came to this patch series when wanted to do two things: > >>> - use UAC1 as virtual ALSA sound card on

Re: [PATCH v4 1/2] tiocsti-restrict : Add owner user namespace to tty_struct

On Wed, May 03, 2017 at 12:32:07PM -0700, Kees Cook wrote: > On Mon, Apr 24, 2017 at 6:57 AM, Serge E. Hallyn wrote: > > Quoting Matt Brown (m...@nmatt.com): > >> This patch adds struct user_namespace *owner_user_ns to the tty_struct. > >> Then it is set to current_user_ns() in

Re: [PATCH v9 7/8] thunderbolt: Networking doc

On Thu, Nov 10, 2016 at 11:47:57AM +, Levy, Amir (Jer) wrote: > On Wed, Nov 9 2016, 06:00 PM, Greg KH wrote: > > On Wed, Nov 09, 2016 at 04:20:07PM +0200, Amir Levy wrote: > > > Adding Thunderbolt(TM) networking documentation. > > > > > > Signed-off-by

Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Thu, Nov 10, 2016 at 11:39:19AM +, Levy, Amir (Jer) wrote: > > And how about getting some internal-Intel kernel developers to review and > > sign-off on this code? Don't make the community do the review when you > > have access to resources like this. You have an internal mailing list for

Re: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Wed, Nov 09, 2016 at 04:20:00PM +0200, Amir Levy wrote: > This driver enables Thunderbolt Networking on non-Apple platforms > running Linux. > > Thunderbolt Networking provides peer-to-peer connections to transfer > files between computers, perform PC migrations, and/or set up small >

Re: [PATCH v9 7/8] thunderbolt: Networking doc

On Wed, Nov 09, 2016 at 04:20:07PM +0200, Amir Levy wrote: > Adding Thunderbolt(TM) networking documentation. > > Signed-off-by: Amir Levy > --- > Documentation/00-INDEX | 2 + > Documentation/thunderbolt/networking.txt | 132 >

Re: [PATCH] USB: update intro of documentation

On Fri, Oct 21, 2016 at 03:17:14PM -0600, Jonathan Corbet wrote: > On Thu, 20 Oct 2016 15:15:00 +0200 > Oliver Neukum wrote: > > > It does no good to mention The 2.4 kernel series and neglect > > USB 3.x and XHCI. Also with type C and micro/mini USB we better > > not talk about

Re: [PATCH] doc-rst: DocBook to reST migration of the uio-howto.tmpl

On Tue, Oct 18, 2016 at 05:52:58PM +0200, Markus Heiser wrote: > The migration is done with the dbxml2rst project with small additional > handmade. The uio-howto is chunked along its chapters into smal parts. "small"? :) And why small parts? Is that the new "desired" way? > > [1]

Re: [PATCH v8 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking

On Fri, Sep 30, 2016 at 01:55:55AM -0400, David Miller wrote: > From: Amir Levy > Date: Wed, 28 Sep 2016 17:44:22 +0300 > > > This driver enables Thunderbolt Networking on non-Apple platforms > > running Linux. > > Greg, any idea where this should get merged once fully

Re: [PATCH v7 5/8] thunderbolt: Networking state machine

On Tue, Sep 27, 2016 at 04:43:38PM +0300, Amir Levy wrote: > This patch builds the peer to peer communication path. > Communication is established by a negotiation process whereby messages are > sent back and forth between the peers until a connection is established. > This includes the

Re: [PATCH v7 4/8] thunderbolt: Communication with the ICM (firmware)

On Tue, Sep 27, 2016 at 04:43:37PM +0300, Amir Levy wrote: > This patch provides the communication protocol between the > Intel Connection Manager(ICM) firmware that is operational in the > Thunderbolt controller in non-Apple hardware. > The ICM firmware-based controller is used for establishing

Re: [PATCH v7 3/8] thunderbolt: Kconfig for Thunderbolt Networking

On Tue, Sep 27, 2016 at 04:43:36PM +0300, Amir Levy wrote: > Update to the Kconfig Thunderbolt description to add > Thunderbolt networking as an option. > The menu item "Thunderbolt support" now offers: > "Apple Hardware Support" (existing) > and/or > "Thunderbolt Networking" (new) > >

Re: [PATCH v2 3/3] tools: move pcmcia crc32hash tool from Documentation

On Wed, Sep 21, 2016 at 06:51:13PM -0600, Shuah Khan wrote: > Move pcmcia crc32hash tool from Documentation to tools/pcmcia and > remove it from Documentation Makefile. Update location information > for this tool. Create a new Makefile to build pcmcia. It can be built > from top level directory or

Re: [PATCH v2 1/4] samples: move misc-devices/mei example code from Documentation

On Wed, Sep 21, 2016 at 01:47:30PM -0600, Shuah Khan wrote: > Move misc-devices/mei examples to samples/mei and remove it from > Documentation Makefile. Delete misc-devices/Makefile. > > Create a new Makefile to build samples/mei. It can be built from top > level directory or from mei directory:

Re: [PATCH v4 22/29] Documentation/HOWTO: add cross-references to other documents

On Mon, Sep 19, 2016 at 08:07:56AM -0300, Mauro Carvalho Chehab wrote: > Add cross references for the documents mentioned at HOWTO and > are under the Documentation/ directory, using the ReST notation. > > It should be noticed that HOWTO also mentions the /README file. > We opted to not touch it,

Re: [PATCH v4 17/29] Documentation/stable_kernel_rules.txt: convert it to ReST markup

On Mon, Sep 19, 2016 at 08:07:51AM -0300, Mauro Carvalho Chehab wrote: > - use ReST markups for section headers; > - add cross-references to the options; > - mark code blocks; > - a few minor changes to make Sphinx happy. > > Signed-off-by: Mauro Carvalho Chehab > --- >

Re: [PATCH 3/3] drivers: Add visorbus to the drivers/virt directory

On Tue, Aug 30, 2016 at 04:29:07PM +, Sell, Timothy C wrote: > E.g., so even though no obvious error-recovery occurs above in-response to > kzalloc() failures, the fact that -CONTROLVM_RESP_ERROR_KMALLOC_FAILED is > provided to bus_epilog() is in-fact sufficient to report the error. > > Is

Re: [PATCH V5] leds: trigger: Introduce a USB port trigger

On Fri, Sep 09, 2016 at 05:34:40PM +0800, Peter Chen wrote: > On Thu, Sep 08, 2016 at 06:08:24PM +0200, Rafał Miłecki wrote: > > From: Rafał Miłecki > > > > This commit adds a new trigger responsible for turning on LED when USB > > device gets connected to the selected USB

Re: [PATCH v6 7/8] thunderbolt: Networking doc

On Mon, Aug 01, 2016 at 03:23:52PM +0300, Amir Levy wrote: > Adding Thunderbolt(TM) networking documentation. > > Signed-off-by: Amir Levy > --- > Documentation/00-INDEX | 2 + > Documentation/thunderbolt-networking.txt | 135 >

Re: [PATCH v6 4/8] thunderbolt: Communication with the ICM (firmware)

On Mon, Aug 01, 2016 at 03:23:49PM +0300, Amir Levy wrote: > Firmware-based (a.k.a ICM - Intel Connection Manager) controller is > used for establishing and maintaining the Thunderbolt Networking > connection. We need to be able to communicate with it. > > Signed-off-by: Amir Levy

Re: [PATCH v6 3/8] thunderbolt: Kconfig for Thunderbolt(TM) networking

On Mon, Aug 01, 2016 at 03:23:48PM +0300, Amir Levy wrote: > Updating the Kconfig Thunderbolt(TM) description. Why are you inserting a (TM) in here? Do you see that in any other kernel Kconfig file? Please don't start adding it here, it's not needed from what I can tell. thanks, greg k-h --

Re: [PATCH v6 0/8] thunderbolt: Introducing Thunderbolt(TM) networking

On Mon, Aug 01, 2016 at 03:23:45PM +0300, Amir Levy wrote: > This is version 6 of Thunderbolt(TM) driver for non-Apple hardware. > > Changes since v5: > - Removed the padding of short packets in receive > - Replaced RW semaphore with mutex > - Cleanup > > These patches were pushed to GitHub

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

On Fri, Aug 26, 2016 at 05:38:05PM +0200, Rafał Miłecki wrote: > On 25 August 2016 at 14:49, Greg KH <gre...@linuxfoundation.org> wrote: > > On Thu, Aug 25, 2016 at 10:03:52AM +0200, Rafał Miłecki wrote: > >> +static void usbport_trig_activate(struc

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

On Thu, Aug 25, 2016 at 10:03:52AM +0200, Rafał Miłecki wrote: > +static void usbport_trig_activate(struct led_classdev *led_cdev) > +{ > + struct usbport_trig_data *usbport_data; > + int err; > + > + usbport_data = kzalloc(sizeof(*usbport_data), GFP_KERNEL); > + if (!usbport_data)

Re: [PATCH V3] leds: trigger: Introduce an USB port trigger

On Thu, Aug 25, 2016 at 07:14:52AM +0200, Rafał Miłecki wrote: > On 24 August 2016 at 23:04, Greg KH <gre...@linuxfoundation.org> wrote: > > On Wed, Aug 24, 2016 at 11:29:51AM +0200, Rafał Miłecki wrote: > >> On 24 August 2016 at 11:22, Greg KH <gre...@linuxfoundatio

Re: [PATCH V3] leds: trigger: Introduce an USB port trigger

On Wed, Aug 24, 2016 at 11:26:27AM +0200, Rafał Miłecki wrote: > On 24 August 2016 at 11:21, Greg KH <gre...@linuxfoundation.org> wrote: > > On Wed, Aug 24, 2016 at 12:03:29AM +0200, Rafał Miłecki wrote: > >> From: Rafał Miłecki <ra...@milecki.pl> > >&

Re: [PATCH V3] leds: trigger: Introduce an USB port trigger

On Wed, Aug 24, 2016 at 12:03:29AM +0200, Rafał Miłecki wrote: > From: Rafał Miłecki > > This commit adds a new trigger responsible for turning on LED when USB > device gets connected to the specified USB port. This can can useful for > various home routers that have USB

Re: [PATCH 3/3] drivers: Add visorbus to the drivers/virt directory

On Mon, Aug 22, 2016 at 10:02:43AM -0400, 'Greg KH' wrote: > On Mon, Aug 22, 2016 at 10:46:10AM +, Sell, Timothy C wrote: > > > -Original Message- > > > From: 'Greg KH' [mailto:gre...@linuxfoundation.org] > > > Sent: Monday, August 22, 2016 4:16 AM > &

Re: [PATCH 3/3] drivers: Add visorbus to the drivers/virt directory

On Mon, Aug 22, 2016 at 10:46:10AM +, Sell, Timothy C wrote: > > -Original Message- > > From: 'Greg KH' [mailto:gre...@linuxfoundation.org] > > Sent: Monday, August 22, 2016 4:16 AM > > To: Sell, Timothy C <timothy.s...@unisys.com> > > Cc: co

Re: [PATCH 3/3] drivers: Add visorbus to the drivers/virt directory

On Mon, Aug 22, 2016 at 02:48:18AM +, Sell, Timothy C wrote: > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Sunday, August 21, 2016 2:05 PM > > To: Kershner, David A <david.kersh...@unisys.com> > > Cc: co

Re: [PATCH 1/3] include: linux: visorbus: Add visorbus to include/linux directory

On Fri, Jun 10, 2016 at 11:23:54PM -0400, David Kershner wrote: > Update include/linux to include the s-Par associated common include > header files needed for the s-Par visorbus. > > Since we have now moved the include directories over to > include/linux/visorbus this patch makes all of the

Re: [PATCH 3/3] drivers: Add visorbus to the drivers/virt directory

On Fri, Jun 10, 2016 at 11:23:56PM -0400, David Kershner wrote: > visorbus is currently located at drivers/staging/visorbus, > this patch moves it to drivers/virt. > > Signed-off-by: David Kershner > Reviewed-by: Tim Sell > --- >

Re: [PATCH v5 4/8] thunderbolt: Communication with the ICM (firmware)

On Fri, Jul 29, 2016 at 02:02:24PM -0700, Stephen Hemminger wrote: > On Thu, 28 Jul 2016 11:15:17 +0300 > Amir Levy wrote: > > > +static LIST_HEAD(controllers_list); > > +static DECLARE_RWSEM(controllers_list_rwsem); > > Why use a semaphore when simple spinlock or mutex

Re: [PATCH 0058/1529] Fix typo

On Sat, May 21, 2016 at 01:44:37PM +0200, Andrea Gelmini wrote: > Signed-off-by: Andrea Gelmini > --- > Documentation/usb/authorization.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Same here, no changelog text == no acceptance. -- To unsubscribe from

Re: new driver for drivers/virt/?

orbus" is a driver to host a virtual bus presented to a Linux guest > > in a hypervisor environment (refer to > > drivers/staging/unisys/Documentation/overview.txt for more details), > > Greg KH and Jes Sorensen have suggested the possibility that drivers/virt/ > > mig

Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86

On Wed, May 18, 2016 at 12:03:58PM -0400, Jes Sorensen wrote: > Greg KH <gre...@linuxfoundation.org> writes: > > On Tue, May 17, 2016 at 07:49:53PM -0400, Jes Sorensen wrote: > >> > Ok, but still no need to put it under arch/ anything, it should go in > >&g

Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86

On Tue, May 17, 2016 at 07:49:53PM -0400, Jes Sorensen wrote: > Greg KH <gre...@linuxfoundation.org> writes: > > On Tue, May 17, 2016 at 10:01:55AM -0400, Jes Sorensen wrote: > >> Greg KH <gre...@linuxfoundation.org> writes: > >> > On Tue, May 17, 2016

Re: [PATCH 4/5] staging: unisys: visorbus: Have visorbus use include/linux/visorbus

On Tue, May 17, 2016 at 03:28:00AM -0400, David Kershner wrote: > Since we have now moved the include directories over to > include/linux/visorbus this patch makes all of visorbus > use the new include folders. > > Signed-off-by: David Kershner > --- >

Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86

On Tue, May 17, 2016 at 03:27:56AM -0400, David Kershner wrote: > This patchset moves the visorbus driver (fromdrivers/staging/unisys/visorbus) > and its dependent headers files (from drivers/staging/unisys/include) > out of staging into the main kernel tree. > > The visorbus driver is a bus

Re: [PATCH 3/5] Documentation: Move visorbus documentation from staging to Documentation/

On Tue, May 17, 2016 at 03:27:59AM -0400, David Kershner wrote: > This patch simple does a git mv of the > drivers/staging/unisys/Documentation directory to Documentation. Renames > overview.txt to visorbus.txt and renames sysfs-platform-visorchipset to > the correct name sysfs-bus-visorbus. > >

Re: [kernel-hardening] [PATCH] doc: self-protection: provide initial details

On Mon, May 16, 2016 at 07:27:28PM -0700, Kees Cook wrote: > This document attempts to codify the intent around kernel self-protection > along with discussion of both existing and desired technologies, with > attention given to the rationale behind them, and the expectations of > their usage. > >

Re: [PATCH 0/6] Intel Secure Guard Extensions

On Mon, Apr 25, 2016 at 08:34:07PM +0300, Jarkko Sakkinen wrote: > Intel(R) SGX is a set of CPU instructions that can be used by > applications to set aside private regions of code and data. The code > outside the enclave is disallowed to access the memory inside the > enclave by the CPU access

Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging

On Thu, Mar 03, 2016 at 05:22:22PM -0500, David Miller wrote: > From: Arnd Bergmann > Date: Wed, 2 Mar 2016 20:06:46 +0100 > > > The icn, act2000 and pcbit drivers are all for very old hardware, > > and it is highly unlikely that anyone is actually still using them > > on modern

Re: [PATCH] usbip: move usbip_protocol.txt to Documentation

On Wed, Feb 24, 2016 at 07:23:08PM +0100, Christian Lamparter wrote: > The usbip_protocol.txt, a document which describes usbip's > inner workings is currently located in the projects source > directory (drivers/usb/usbip/...). This patch moves it to > Documentation/usb. > > This discussion was