From: Simon Horman <horms@kernel.org>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: amir73il@gmail.com, bhe@redhat.com, clm@fb.com,
dhowells@redhat.com, dsterba@suse.com, dyoung@redhat.com,
jlayton@kernel.org, josef@toxicpanda.com,
kexec@lists.infradead.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
netfs@lists.linux.dev, vgoyal@redhat.com
Subject: Re: [RESEND PATCH 2/4] fscache: Remove duplicate included header
Date: Mon, 3 Jun 2024 19:01:21 +0100 [thread overview]
Message-ID: <20240603180121.GF491852@kernel.org> (raw)
In-Reply-To: <20240526212108.1462-2-thorsten.blum@toblux.com>
On Sun, May 26, 2024 at 11:21:09PM +0200, Thorsten Blum wrote:
> Remove duplicate included header file linux/uio.h
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
Reviewed-by: Simon Horman <horms@kernel.org>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: amir73il@gmail.com, bhe@redhat.com, clm@fb.com,
dhowells@redhat.com, dsterba@suse.com, dyoung@redhat.com,
jlayton@kernel.org, josef@toxicpanda.com,
kexec@lists.infradead.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
netfs@lists.linux.dev, vgoyal@redhat.com
Subject: Re: [RESEND PATCH 2/4] fscache: Remove duplicate included header
Date: Mon, 3 Jun 2024 19:01:21 +0100 [thread overview]
Message-ID: <20240603180121.GF491852@kernel.org> (raw)
In-Reply-To: <20240526212108.1462-2-thorsten.blum@toblux.com>
On Sun, May 26, 2024 at 11:21:09PM +0200, Thorsten Blum wrote:
> Remove duplicate included header file linux/uio.h
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-06-03 18:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 21:26 [PATCH 1/4] btrfs: Remove duplicate included header Thorsten Blum
2024-05-02 21:26 ` Thorsten Blum
2024-05-02 21:26 ` [PATCH 2/4] fscache: " Thorsten Blum
2024-05-02 21:26 ` Thorsten Blum
2024-05-26 21:21 ` [RESEND PATCH " Thorsten Blum
2024-05-26 21:21 ` Thorsten Blum
2024-06-03 18:01 ` Simon Horman [this message]
2024-06-03 18:01 ` Simon Horman
2024-05-02 21:26 ` [PATCH 3/4] overlayfs: " Thorsten Blum
2024-05-02 21:26 ` Thorsten Blum
2024-05-10 11:23 ` Miklos Szeredi
2024-05-10 11:23 ` Miklos Szeredi
2024-05-02 21:26 ` [PATCH 4/4] crash: " Thorsten Blum
2024-05-02 21:26 ` Thorsten Blum
2024-05-05 7:03 ` Baoquan He
2024-05-05 7:03 ` Baoquan He
2024-05-26 21:23 ` [RESEND PATCH " Thorsten Blum
2024-05-26 21:23 ` Thorsten Blum
2024-05-02 22:50 ` [PATCH 1/4] btrfs: " David Sterba
2024-05-02 22:50 ` David Sterba
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=20240603180121.GF491852@kernel.org \
--to=horms@kernel.org \
--cc=amir73il@gmail.com \
--cc=bhe@redhat.com \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=dyoung@redhat.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kexec@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=netfs@lists.linux.dev \
--cc=thorsten.blum@toblux.com \
--cc=vgoyal@redhat.com \
/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.