From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for Dec 15 (fs/afs/)
Date: Fri, 15 Dec 2023 21:29:31 -0800 [thread overview]
Message-ID: <8a078303-f52b-4e3c-91da-315556e3738e@infradead.org> (raw)
In-Reply-To: <20231215150128.07763fb1@canb.auug.org.au>
On 12/14/23 20:01, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20231214:
>
on i386:
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
next prev parent reply other threads:[~2023-12-16 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 4:01 linux-next: Tree for Dec 15 Stephen Rothwell
2023-12-16 5:26 ` linux-next: Tree for Dec 15 (drivers/net/ethernet/intel/ice/ice_base.c) Randy Dunlap
2023-12-18 17:29 ` Tony Nguyen
2023-12-16 5:29 ` Randy Dunlap [this message]
2023-12-16 5:31 ` linux-next: Tree for Dec 15 (fs/afs/) Randy Dunlap
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=8a078303-f52b-4e3c-91da-315556e3738e@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).