public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 patches for the 6.1 merge window #2
Date: Fri, 14 Oct 2022 19:54:55 +0200	[thread overview]
Message-ID: <your-ad-here.call-01665770095-ext-6515@work.hours> (raw)

Hello Linus,

please pull couple more s390 changes for 6.1.

Thank you,
Vasily

The following changes since commit 03785a69ae47a17fe57fee31058fef7cd3042977:

  Merge tag 's390-6.1-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux (2022-10-09 13:51:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.1-2

for you to fetch changes up to bf18140d30541c2c1e5c0f57879634f3d0d04912:

  s390/vmur: generate uevent on unsolicited device end (2022-10-10 10:15:10 +0200)

----------------------------------------------------------------
s390 updates for the 6.1 merge window #2

- Generate a change uevent on unsolicited device end I/O interrupt for z/VM
  unit record devices supported by the vmur driver. This event can be used to
  automatically trigger processing of files as they arrive in the z/VM reader.

----------------------------------------------------------------
Peter Oberparleiter (2):
      s390/vmur: remove unnecessary BUG statement
      s390/vmur: generate uevent on unsolicited device end

 drivers/s390/char/vmur.c | 37 ++++++++++++++++++++++++++++++++++---
 drivers/s390/char/vmur.h |  2 ++
 2 files changed, 36 insertions(+), 3 deletions(-)

             reply	other threads:[~2022-10-14 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 17:54 Vasily Gorbik [this message]
2022-10-14 19:13 ` [GIT PULL] s390 patches for the 6.1 merge window #2 pr-tracker-bot

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=your-ad-here.call-01665770095-ext-6515@work.hours \
    --to=gor@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=torvalds@linux-foundation.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