From: Christoph Hellwig <hch@lst.de>
To: Martin Wilck <mwilck@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-nvme@lists.infradead.org, jthumshirn@suse.com,
arnd@arndb.de
Subject: Re: [PATCH] string.h: un-fortify memcpy_and_pad
Date: Mon, 11 Sep 2017 13:57:25 +0200 [thread overview]
Message-ID: <20170911115725.GB21472@lst.de> (raw)
In-Reply-To: <1505123078.4683.5.camel@suse.de>
> Hello Stephen and Christoph,
>
> my broken patch 01f33c336e2d is in Linus' tree and causing compiler
> warnings there. Could you please take care that this fix is pulled in
> on top of it? Or should I take another action myself?
string.h is a bit of a maintainers no mans land. Given that the
problematic commit came in through the nvme tree I've applied your
patch and will sned it to Jens with the next batch of nvme updates
tonight.
next prev parent reply other threads:[~2017-09-11 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 8:21 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2017-09-06 12:32 ` Martin Wilck
2017-09-06 12:36 ` [PATCH] string.h: un-fortify memcpy_and_pad Martin Wilck
2017-09-11 9:44 ` Martin Wilck
2017-09-11 11:57 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 7:28 [PATCH v4 2/3] string.h: add memcpy_and_pad() Arnd Bergmann
2017-09-05 18:23 ` [PATCH] string.h: un-fortify memcpy_and_pad Martin Wilck
2017-09-05 19:26 ` Arnd Bergmann
2017-09-06 13:02 ` Arnd Bergmann
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=20170911115725.GB21472@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=jthumshirn@suse.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mwilck@suse.de \
--cc=sagi@grimberg.me \
--cc=sfr@canb.auug.org.au \
/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