mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org, jeyu@kernel.org,
	linux-kernel@vger.kernel.org
Cc: msekleta@redhat.com, Peter Rajnoha <prajnoha@redhat.com>
Subject: [PATCH 0/2] Fix return code and improve feature check for synthetic uevents
Date: Wed,  5 Dec 2018 12:27:43 +0100	[thread overview]
Message-ID: <20181205112745.12276-1-prajnoha@redhat.com> (raw)

Two small patches to aid handling of synthetic uevents back in userspace:

  - Return error code back to userspace on /sys/.../uevent file write
    failure so userspace knows and it can act accordingly.

  - Add new 'kernel/uevent_features' sysfs file to make it possible for
    userspace to check that the extended synthetic uevent arguments are
    supported without relying on kernel version check only.

Peter Rajnoha (2):
  kobject: return error code if writing /sys/.../uevent fails
  kobject: add kernel/uevent_features sysfs file

 drivers/base/bus.c  | 12 ++++++++----
 drivers/base/core.c |  8 +++++++-
 kernel/ksysfs.c     |  8 ++++++++
 kernel/module.c     |  6 ++++--
 4 files changed, 27 insertions(+), 7 deletions(-)

-- 
2.19.2


             reply	other threads:[~2018-12-05 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 11:27 Peter Rajnoha [this message]
2018-12-05 11:27 ` [PATCH 1/2] kobject: return error code if writing /sys/.../uevent fails Peter Rajnoha
2021-04-29 13:40   ` Phillip Susi
2021-04-29 17:27     ` Greg KH
2018-12-05 11:27 ` [PATCH 2/2] kobject: add kernel/uevent_features sysfs file Peter Rajnoha
2018-12-06 15:07   ` Greg KH
2018-12-05 16:30 ` [PATCH 0/2] Fix return code and improve feature check for synthetic uevents Greg KH
2018-12-06  8:40   ` Peter Rajnoha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181205112745.12276-1-prajnoha@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msekleta@redhat.com \
    --cc=rafael@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®