From: Jens Axboe <axboe@kernel.dk>
To: efremov@linux.com
Cc: linux-block <linux-block@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Willy Tarreau <w@1wt.eu>
Subject: Re: [GIT PULL] Floppy cleanups for next
Date: Mon, 16 Mar 2020 09:08:07 -0600 [thread overview]
Message-ID: <6f4fd061-a47e-7de5-df6e-c3002beedee0@kernel.dk> (raw)
In-Reply-To: <57ce0ee0-839c-a889-0bc0-ec46985e76d3@linux.com>
On 3/16/20 4:47 AM, Denis Efremov wrote:
> Hi Jens,
>
> The following changes since commit 5d50c8f405bf91d9d9a48628fde0f2f4ff069d7b:
>
> Merge branch 'for-5.7/io_uring' into for-next (2020-03-14 17:20:45 -0600)
>
> are available in the Git repository at:
>
> https://github.com/evdenis/linux-floppy tags/floppy-for-5.7
>
> Please pull
>
> ----------------------------------------------------------------
> Floppy patches for 5.7
>
> Cleanups from Willy Tarreau:
> - expansion of macros referencing global or local variables with
> equivalent code
> - removal of incomplete support for second FDC from ARM code
> - renaming the "fdc" global variable to "current_fdc" to differ
> between global and local context
>
> Changes were compile tested on arm, x86 arches. Changes introduce
> no binary difference on x86 arch (before and after the patches).
> On arm, incomplete support for second FDC removed. This set of
> patches with commit 2e90ca68 ("floppy: check FDC index for errors
> before assigning it") was tested with syzkaller and simple
> write/read/format tests for no new issues.
>
> Signed-off-by: Denis Efremov <efremov@linux.com>
Thanks - I hand applied the series, my for-next branch isn't really
stable, only the parent branches are.
--
Jens Axboe
next prev parent reply other threads:[~2020-03-16 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 10:47 [GIT PULL] Floppy cleanups for next Denis Efremov
2020-03-16 15:08 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 14:28 Denis Efremov
2020-05-12 15:23 ` Jens Axboe
2020-05-12 15:55 ` Denis Efremov
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=6f4fd061-a47e-7de5-df6e-c3002beedee0@kernel.dk \
--to=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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