From: Marek Behun <marek.behun@nic.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Qu Wenruo <wqu@suse.com>,
matthias.bgg@kernel.org, u-boot@lists.denx.de,
linux-btrfs@vger.kernel.org, Matthias Brugger <mbrugger@suse.com>
Subject: Re: [PATCH] fs: btrfs: Select SHA256 in Kconfig
Date: Wed, 27 Jan 2021 14:57:11 +0100 [thread overview]
Message-ID: <20210127145711.44db831d@nic.cz> (raw)
In-Reply-To: <20210127134758.GA1993@twin.jikos.cz>
On Wed, 27 Jan 2021 14:47:58 +0100
David Sterba <dsterba@suse.cz> wrote:
> If it's a series then please mention u-boot in the cover letter, no need
> to change the patches, I'll go check CC if I'm too confused about the
> patch.
I would suggest using subject prefix [PATCH u-boot]
next prev parent reply other threads:[~2021-01-27 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:42 [PATCH] fs: btrfs: Select SHA256 in Kconfig matthias.bgg
2021-01-27 9:46 ` Qu Wenruo
2021-01-27 12:01 ` David Sterba
2021-01-27 12:14 ` Qu Wenruo
2021-01-27 13:47 ` David Sterba
2021-01-27 13:57 ` Marek Behun [this message]
2021-01-30 19:21 ` Tom Rini
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=20210127145711.44db831d@nic.cz \
--to=marek.behun@nic.cz \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=u-boot@lists.denx.de \
--cc=wqu@suse.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 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).