mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.7.y 0/5] exfat stable patches for 5.7.y
Date: Wed, 1 Jul 2020 21:38:24 -0400	[thread overview]
Message-ID: <20200702013824.GH2687961@sasha-vm> (raw)
In-Reply-To: <20200701232024.2083-1-namjae.jeon@samsung.com>

Hi Namjae,

On Thu, Jul 02, 2020 at 08:20:19AM +0900, Namjae Jeon wrote:
>Could you please push exfat stable patches into 5.7.y kernel tree ?

I've queued them up, however it would be much easier if for commits that
don't require any modification to allow backporting you would just
provide the commit ids in Linus's tree rather than the patches
themselves.

I do see that you had to modify this one:

>Sungjong Seo (1):
>  exfat: flush dirty metadata in fsync

In which case, a header in the commit message indicating the upstream
commit id would be appriciated. Something like this:

[ Upstream commit 5267456e953fd8c5abd8e278b1cc6a9f9027ac0a ]

Thank you!

-- 
Thanks,
Sasha

  parent reply	other threads:[~2020-07-02  1:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200701232535epcas1p3787fa9426c087372556cba2fdb7232ac@epcas1p3.samsung.com>
2020-07-01 23:20 ` Namjae Jeon
     [not found]   ` <CGME20200701232536epcas1p1e0f92c7cc47e06ce490088c2e3cc1a21@epcas1p1.samsung.com>
2020-07-01 23:20     ` [PATCH 5.7.y 1/5] exfat: Set the unused characters of FileName field to the value 0000h Namjae Jeon
     [not found]   ` <CGME20200701232537epcas1p37fafe2525f4164dc814b02ec9b18df2d@epcas1p3.samsung.com>
2020-07-01 23:20     ` [PATCH 5.7.y 2/5] exfat: add missing brelse() calls on error paths Namjae Jeon
     [not found]   ` <CGME20200701232538epcas1p1e1e682b31b736069e70f5799244e27d5@epcas1p1.samsung.com>
2020-07-01 23:20     ` [PATCH 5.7.y 3/5] exfat: call sync_filesystem for read-only remount Namjae Jeon
     [not found]   ` <CGME20200701232538epcas1p1219929c259f41782831936a2afeeafdf@epcas1p1.samsung.com>
2020-07-01 23:20     ` [PATCH 5.7.y 4/5] exfat: move setting VOL_DIRTY over exfat_remove_entries() Namjae Jeon
     [not found]   ` <CGME20200701232539epcas1p4b7cb5db391c6974f541b4b8b5263ba65@epcas1p4.samsung.com>
2020-07-01 23:20     ` [PATCH 5.7.y 5/5] exfat: flush dirty metadata in fsync Namjae Jeon
2020-07-02  1:38   ` Sasha Levin [this message]
2020-07-02  1:45     ` [PATCH 5.7.y 0/5] exfat stable patches for 5.7.y Namjae Jeon

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=20200702013824.GH2687961@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=stable@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®