From: Jens Axboe <axboe@kernel.dk>
To: Denis Efremov <efremov@linux.com>
Cc: linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL RESEND] Floppy cleanups for next
Date: Tue, 12 May 2020 11:36:37 -0600 [thread overview]
Message-ID: <c6d08f09-7415-c92e-0f94-1eb521f2ecb0@kernel.dk> (raw)
In-Reply-To: <565fc2e1-a790-241f-7a98-52a4c5ff8158@linux.com>
On 5/12/20 11:33 AM, Denis Efremov wrote:
> Rebased on for-5.8/drivers branch.
>
> The following changes since commit 92decf118f1da4c866515f80387f9cf4d48611d6:
>
> nvme: define constants for identification values (2020-05-09 16:18:36 -0600)
>
> are available in the Git repository at:
>
> https://github.com/evdenis/linux-floppy tags/floppy-for-5.8
>
> for you to fetch changes up to 0836275df4db20daf040fff5d9a1da89c4c08a85:
>
> floppy: suppress UBSAN warning in setup_rw_floppy() (2020-05-12 19:34:57 +0300)
>
> ----------------------------------------------------------------
> Floppy patches for 5.8
>
> Cleanups:
> - symbolic register names for x86,sparc64,sparc32,powerpc,parisc,m68k
> - split of local/global variables for drive,fdc
> - UBSAN warning suppress in setup_rw_floppy()
>
> Changes were compile tested on arm, sparc64, powerpc, m68k. Many patches
> introduce no binary changes by using defines instead of magic numbers.
> The patches were also tested with syzkaller and simple write/read/format
> tests on real hardware.
>
> Signed-off-by: Denis Efremov <efremov@linux.com>
Thanks, pulled.
--
Jens Axboe
prev parent reply other threads:[~2020-05-12 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:28 [GIT PULL] " Denis Efremov
2020-05-12 15:23 ` Jens Axboe
2020-05-12 15:55 ` Denis Efremov
2020-05-12 17:33 ` [GIT PULL RESEND] " Denis Efremov
2020-05-12 17:36 ` Jens Axboe [this message]
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=c6d08f09-7415-c92e-0f94-1eb521f2ecb0@kernel.dk \
--to=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome