On Thu, Feb 23, 2017 at 03:56:21PM -0700, Logan Gunthorpe wrote:
>
>
> On 23/02/17 03:43 PM, Bjorn Helgaas wrote:
> > This path seems a little generic. I don't see other cases where a
> > product brand name ("Switchtec") appears at the top level of
> > /sys/class/...
>
> Ok, well we are certain
This patch adds a few read-only sysfs attributes which provide
some device information that is exposed from the devices. Primarily
component and device names and versions. These are documented in
Documentation/ABI/testing/sysfs-class-switchtec.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephe
This patch introduces a couple of special IOCTLs which are provided to:
* Inform userspace of firmware partition locations
* Pass event counts and allow userspace to wait on events
* Translate between PFF numbers used by the switch to
port numbers.
Signed-off-by: Logan Gunthorpe
Signed-off-by:
Changes since v3:
* Removed stdev_is_alive and moved pci deinit functions
into the device release function which only occurs after all
cdev instances are closed. (per Bjorn)
* Reduced locking in read/write functions (per Bjorn)
* Use pci_alloc_irq_vectors to vastly improve ISR initialization (
Microsemi's "Switchtec" line of PCI switch devices is already well
supported by the kernel with standard PCI switch drivers. However, the
Switchtec device advertises a special management endpoint with a separate
PCI function address and class code. This endpoint enables some additional
functionalit
This adds standard documentation for the sysfs switchtec attributes and
a RST formatted text file which documents the char device interface.
Jonathan Corbet has indicated he will move this to a new user-space
developer documentation book once it's created.
Signed-off-by: Logan Gunthorpe
Signed-of
Hey Bjorn,
Thanks for the thorough review. It definitely helped a lot to make the
code as good as it can be.
I've made all of the changes you suggested. I'm just going to do a bit
more testing and then post a v4. See my responses to all of your
feedback bellow.
Logan
On 23/02/17 05:35 PM, Bjorn
On Fri, Feb 24, 2017 at 10:21:35AM -0700, Jonathan Corbet wrote:
> On Fri, 24 Feb 2017 10:36:20 +0200
> Krzysztof Kozlowski wrote:
>
> > What happened with this patch? I am asking because on top of
> > next-20170224 I found some more sysrq.txt obsolete paths... including
&g
On Fri, 24 Feb 2017 10:36:20 +0200
Krzysztof Kozlowski wrote:
> What happened with this patch? I am asking because on top of
> next-20170224 I found some more sysrq.txt obsolete paths... including
> the ones fixed here. I am not sure whether I am fixing something
> already fixed?
W
On Fri, Feb 24, 2017 at 09:04:21AM -0600, Tom Lendacky wrote:
> I looked at doing that but you get into this cyclical situation unless
> you specifically map each setup data elemement as decrypted. This is ok
> for early_memremap since we have early_memremap_decrypted() but a new
> memremap_decrypt
On 2/24/2017 4:21 AM, Borislav Petkov wrote:
On Thu, Feb 23, 2017 at 03:34:30PM -0600, Tom Lendacky wrote:
Hmm... maybe I'm missing something here. This doesn't have anything to
do with kexec or efi_reuse_config. This has to do with the fact that
I said kexec because kexec uses the setup_dat
On Thu, Feb 23, 2017 at 03:34:30PM -0600, Tom Lendacky wrote:
> Hmm... maybe I'm missing something here. This doesn't have anything to
> do with kexec or efi_reuse_config. This has to do with the fact that
I said kexec because kexec uses the setup_data mechanism to pass config
tables to the seco
On Thu, 23 Feb, at 11:27:55AM, Tom Lendacky wrote:
>
> I can do that, I'll change the return type to an int. For the
> !efi_enabled I can return -ENOTSUPP and for when an entry isn't
> found I can return -EINVAL. Sound good?
Sounds good to me!
--
To unsubscribe from this list: send the line "un
Em Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski escreveu:
> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
>
> Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Mauro Carvalho Chehab
> ---
> Documentation/media/
Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
sysrq.txt leaving old paths in the kernel docs.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/media/v4l-drivers/bttv.rst | 2 +-
Documentation/s390/Debugging390.txt | 2 +-
Documentation/sysctl
pened with this patch? I am asking because on top of
next-20170224 I found some more sysrq.txt obsolete paths... including
the ones fixed here. I am not sure whether I am fixing something
already fixed?
Best regards,
Krzysztof
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index e632
Add the new SuperH interfaces RST into the documentation tree by adding
a new arch-guide.
Signed-off-by: Steve Kowalik
---
Documentation/00-INDEX | 2 ++
Documentation/arch-guide/conf.py | 10 ++
Documentation/arch-guide/index.rst | 14 ++
Documentation/index.r
Convert the SuperH interfaces guide to RST, and add a new arch-guide to
place it into. I'm not hugely happy with the wording, but I've been sitting
on this long enough, and should get more eyes on it.
Steve Kowalik (2):
Documentation: convert sh interfaces to RST
Documentation: Add arch-guide
Convert the SuperH interfaces DocBook to RST.
Signed-off-by: Steve Kowalik
---
Documentation/DocBook/Makefile | 2 +-
Documentation/DocBook/sh.tmpl | 105
Documentation/sh/interfaces.rst | 63
3 files changed, 64 insertions(
19 matches
Mail list logo
