From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bart Van Assche <bvanassche@acm.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the mm tree with the kspp tree
Date: Wed, 31 Aug 2022 15:24:01 -0700 [thread overview]
Message-ID: <202208311523.D60D78A@keescook> (raw)
In-Reply-To: <20220901080504.73843b04@canb.auug.org.au>
On Thu, Sep 01, 2022 at 08:05:04AM +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> On Wed, 31 Aug 2022 10:51:08 -0700 Kees Cook <keescook@chromium.org> wrote:
> >
> > Thanks! Andrew, can you drop these patches from -mm please? I corrected
> > the filename convention in the above named patch.
>
> He did that yesterday, so all good.
Thanks! Yeah, I saw the drop right after I sent my email. :) Sorry for
the noise!
--
Kees Cook
prev parent reply other threads:[~2022-08-31 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 7:00 linux-next: manual merge of the mm tree with the kspp tree Stephen Rothwell
2022-08-31 17:51 ` Kees Cook
2022-08-31 22:05 ` Stephen Rothwell
2022-08-31 22:24 ` Kees Cook [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=202208311523.D60D78A@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.