All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
	Stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: FW: Re: [PATCH 5.7.y 0/4] exfat stable patches for 5.7.y
Date: Sun, 26 Jul 2020 23:47:13 +0900	[thread overview]
Message-ID: <CAKYAXd_E9AREHbq3v87YbopBUxKU+cDd+OJkUS4fSjA1FMMQow@mail.gmail.com> (raw)
In-Reply-To: <20200726082152epcms1p54e52279179cea382baf02c4616af315b@epcms1p5>

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

> > > On Fri, Jul 24, 2020 at 09:15:40AM +0900, Namjae Jeon wrote:
> > > >Hi,
> > > >
> > > >Could you please pick up exfat stable patches ?
> > >
> > Hi Sasha,
> > > I see that the upstream commits already have stable tags and don't need modifications for backporting,
> > > so there is no need to explicitly send them here - they will be picked up automatically.
> > Okay, I see:)
>
Hi Greg,

Sorry for late reply. I checked this mail late.
> As Sasha said, these will normally get picked up automatically.  We wait
> until a patch is in a release from Linus (i.e. a -rc) before taking
> them, but we can take them earilier if you ask for them.
Okay, I like that you apply them after 5.8-rc7 is released if these
patches can be applied in 5.7. I was just worried that 5.7 stable
kernel release is closed without these patches being applied :)
>
> You did include one patch in this series that was not marked for stable,
> so I've taken that, and the other 3 now to make it easy.
Ah, okay, I will check stable mark in patches next time.

Thanks for your mail!
>
> thanks,
>
> greg k-h
>
>
>
>
>

[-- Attachment #2: noname --]
[-- Type: image/gif, Size: 13402 bytes --]

[-- Attachment #3: noname --]
[-- Type: image/gif, Size: 13402 bytes --]

      parent reply	other threads:[~2020-07-26 14:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200724002112epcas1p24c54808617a5baddef4e4a2f49722866@epcas1p2.samsung.com>
2020-07-24  0:15 ` [PATCH 5.7.y 0/4] exfat stable patches for 5.7.y Namjae Jeon
     [not found]   ` <CGME20200724002121epcas1p31a4629c7cf9d3b342d18d8f5faf371e2@epcas1p3.samsung.com>
2020-07-24  0:15     ` [PATCH 5.7.y 1/4] exfat: fix overflow issue in exfat_cluster_to_sector() Namjae Jeon
     [not found]   ` <CGME20200724002122epcas1p3611340519231e6d365a603bcec134e39@epcas1p3.samsung.com>
2020-07-24  0:15     ` [PATCH 5.7.y 2/4] exfat: fix wrong hint_stat initialization in exfat_find_dir_entry() Namjae Jeon
     [not found]   ` <CGME20200724002123epcas1p1ba65569ce62beb1ba94efb38907a798b@epcas1p1.samsung.com>
2020-07-24  0:15     ` [PATCH 5.7.y 3/4] exfat: fix wrong size update of stream entry by typo Namjae Jeon
     [not found]   ` <CGME20200724002124epcas1p2b7fe53394e20e4dccc23e61e2a82b828@epcas1p2.samsung.com>
2020-07-24  0:15     ` [PATCH 5.7.y 4/4] exfat: fix name_hash computation on big endian systems Namjae Jeon
2020-07-24  3:57   ` [PATCH 5.7.y 0/4] exfat stable patches for 5.7.y Sasha Levin
2020-07-24  4:00     ` Namjae Jeon
2020-07-24  9:42       ` Greg KH
     [not found]         ` <20200726082152epcms1p54e52279179cea382baf02c4616af315b@epcms1p5>
2020-07-26 14:47           ` Namjae Jeon [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=CAKYAXd_E9AREHbq3v87YbopBUxKU+cDd+OJkUS4fSjA1FMMQow@mail.gmail.com \
    --to=linkinjeon@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=namjae.jeon@samsung.com \
    --cc=sashal@kernel.org \
    --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 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.