From: Greg KH <gregkh@linuxfoundation.org>
To: SeongJae Park <sjpark@amazon.com>
Cc: Muchun Song <songmuchun@bytedance.com>,
Filipe Manana <fdmanana@suse.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
Alexander Tsoy <alexander@tsoy.me>, Takashi Iwai <tiwai@suse.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Michael Chan <michael.chan@broadcom.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Vincent Guittot <vincent.guittot@linaro.org>,
Taehee Yoo <ap420073@gmail.com>,
Fabio Estevam <festevam@gmail.com>, Jan Kara <jack@suse.cz>,
Dongli Zhang <dongli.zhang@oracle.com>,
YueHaibing <yuehaibing@huawei.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Adam Ford <aford173@gmail.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Xiaochen Shen <xiaochen.shen@intel.com>,
sashal@kernel.org, amit@kernel.org, sj38.park@gmail.com,
stable@vger.kernel.org
Subject: Re: [5.4.y] Found 27 commits that might missed
Date: Sat, 5 Sep 2020 09:09:46 +0200 [thread overview]
Message-ID: <20200905070946.GA184702@kroah.com> (raw)
In-Reply-To: <20200904141748.3658-1-sjpark@amazon.com>
On Fri, Sep 04, 2020 at 04:17:48PM +0200, SeongJae Park wrote:
> > <snip>
> >
> > Stopping right here, if you have fixes that will not cleanly apply, and
> > you think they should be applied, please fix them and send the proper
> > backport. I don't have the cycles to do these on my own.
> >
> > Same for anything else here that you think should be applied but does
> > not cleanly build/apply.
>
> Totally agreed. Actually, I posted a similar report[1] before and received
> similar response. I promised to back-port some of those by myself. That's
> still in my TODO list, but I was unable to get a time to revisit it quite long
> time. From this, I realized that it wouldn't be easy to review, test, and
> backport all of the such suspicious things by myself. Scaling up to multiple
> stable series (the tool says there are 152 fixes and 147 mentions for 4.9.y)
> seems impossible.
>
> For the reason, I updated the tool to make the report to be sent to not only
> the stable maintainers but also the authors of the suspicious commits, because
> the review / test / backport of their own commits would be much easier that
> others. As a result, we were able to find one suspended commit:
> https://lore.kernel.org/stable/CAKfTPtAkOes+HmVabRazhCBBUo0M+QW38q3Zzj_O3O+Ghvc1pA@mail.gmail.com/
That work had already been done before your email was sent.
I too can write a tool that sends out "this patch might be for stable,
will you do the work for it!" emails, but that's a bit rude to ask
others to do your work for you, don't you agree? By asking me and
others to dig through this list, when you said you don't have the time
to do so, feels very odd to me.
And if you have only 152 "fixes" for 4.9.y, that's great, should be easy
to work through. I do know that most of the "easy" backports are
already done, so what is left are the ones that take real work, or do
not make any sense, as your list shows.
So I don't think this report actually helped anyone here, do you?
Again, if you can do the backporting, that will help out greatly.
thanks,
greg k-h
next prev parent reply other threads:[~2020-09-05 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 15:27 [5.4.y] Found 27 commits that might missed SeongJae Park
2020-08-31 7:50 ` Jan Kara
2020-08-31 8:16 ` [External] " Muchun Song
2020-08-31 8:37 ` Vincent Guittot
2020-08-31 9:43 ` Takashi Iwai
2020-09-04 11:49 ` Greg KH
2020-09-04 14:17 ` SeongJae Park
2020-09-05 7:09 ` Greg KH [this message]
2020-09-05 8:02 ` SeongJae Park
2020-09-05 22:50 ` Sasha Levin
2020-09-06 5:24 ` SeongJae Park
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=20200905070946.GA184702@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=aford173@gmail.com \
--cc=alexander@tsoy.me \
--cc=amit@kernel.org \
--cc=ap420073@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dongli.zhang@oracle.com \
--cc=fdmanana@suse.com \
--cc=festevam@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jack@suse.cz \
--cc=michael.chan@broadcom.com \
--cc=mika.kuoppala@linux.intel.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=sashal@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=tudor.ambarus@microchip.com \
--cc=vincent.guittot@linaro.org \
--cc=xiaochen.shen@intel.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yuehaibing@huawei.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