mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SeongJae Park <sjpark@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sjpark@amazon.com>, <stable@vger.kernel.org>,
	SeongJae Park <sjpark@amazon.de>, <doebel@amazon.de>,
	<aams@amazon.de>, <mku@amazon.de>, <jgross@suse.com>,
	<julien@xen.org>, <wipawel@amazon.de>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] Backport of patch series for stable 4.4 branch
Date: Tue, 5 Jan 2021 11:51:07 +0100	[thread overview]
Message-ID: <20210105105107.3564-1-sjpark@amazon.com> (raw)
In-Reply-To: <X/RC3ghc7u4uPIjT@kroah.com>

On Tue, 5 Jan 2021 11:43:42 +0100 Greg KH <gregkh@linuxfoundation.org> wrote:

> On Tue, Jan 05, 2021 at 11:37:02AM +0100, SeongJae Park wrote:
> > Hi Greg,
> > 
> > On Mon, 28 Dec 2020 12:29:11 +0100 Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > > On Thu, Dec 17, 2020 at 05:03:57PM +0100, SeongJae Park wrote:
> > > > From: SeongJae Park <sjpark@amazon.de>
> > > > 
> > > > Changes from v2
> > > > (https://lore.kernel.org/stable/20201217130501.12702-1-sjpark@amazon.com/)
> > > > - Move 'nr_pending' increase from 5th patch to 4th patch
> > > > 
> > > > Changes from v1
> > > > (https://lore.kernel.org/stable/20201217081727.8253-1-sjpark@amazon.com/)
> > > > - Remove wrong 'Signed-off-by' lines for 'Author Redacted'
> > > 
> > > All now queued up, but you also need a series of this for the 4.9.y tree
> > > as well.
> > 
> > Thank you for your efforts!
> > 
> > However, I was able to cherry-pick this series, which is already merged in
> > 4.4.y, to 4.9.y without conflicts.
> > 
> >     $ git checkout stable/linux-4.9.y -b xsa349_4.9
> >     $ git cherry-pick d8b0d52e408ca..3c71d2f637c8
> >     warning: inexact rename detection was skipped due to too many files.
> >     warning: you may want to set your merge.renamelimit variable to at least 6130 and retry the command.
> >     [xsa349_4.9 51b4cb3db28a] xen/xenbus: Allow watches discard events before queueing
> >      Date: Mon Dec 14 10:02:45 2020 +0100
> >      4 files changed, 16 insertions(+), 1 deletion(-)
> >     warning: inexact rename detection was skipped due to too many files.
> >     warning: you may want to set your merge.renamelimit variable to at least 6130 and retry the command.
> >     [xsa349_4.9 3242225d9645] xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path()
> >      Date: Mon Dec 14 10:04:18 2020 +0100
> >      6 files changed, 17 insertions(+), 7 deletions(-)
> >     warning: inexact rename detection was skipped due to too many files.
> >     warning: you may want to set your merge.renamelimit variable to at least 6130 and retry the command.
> >     [xsa349_4.9 10d6c1301412] xen/xenbus/xen_bus_type: Support will_handle watch callback
> >      Date: Mon Dec 14 10:05:47 2020 +0100
> >      2 files changed, 4 insertions(+), 1 deletion(-)
> >     warning: inexact rename detection was skipped due to too many files.
> >     warning: you may want to set your merge.renamelimit variable to at least 6130 and retry the command.
> >     [xsa349_4.9 3875703f1e6b] xen/xenbus: Count pending messages for each watch
> >      Date: Mon Dec 14 10:07:13 2020 +0100
> >      2 files changed, 21 insertions(+), 12 deletions(-)
> >     warning: inexact rename detection was skipped due to too many files.
> >     warning: you may want to set your merge.renamelimit variable to at least 6130 and retry the command.
> >     [xsa349_4.9 40e3b315cd18] xenbus/xenbus_backend: Disallow pending watch messages
> >      Date: Mon Dec 14 10:08:40 2020 +0100
> >      1 file changed, 7 insertions(+)
> > 
> > Seems you tried to merge the series for upstream in 4.9.y:
> > 
> >     https://lore.kernel.org/stable/1609154834239118@kroah.com/
> > 
> > This must because I didn't test this series with v4.9 and mention it.  Sorry
> > for making a confusion.  Could you please check this again?
> 
> I can't do anything with a set of git cherry-picks like above, can you
> please send the patches as a series so that I can apply them cleanly?

Sure, I will post it soon.

> 
> And I don't remember what happened with that failure, sorry, dealing
> with hundreds of patches a week makes them all blur together...

I understand.  No problem at all.


Thanks,
SeongJae Park

      reply	other threads:[~2021-01-05 10:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 16:03 SeongJae Park
2020-12-17 16:03 ` [PATCH v3 1/5] xen/xenbus: Allow watches discard events before queueing SeongJae Park
2020-12-17 16:03 ` [PATCH v3 2/5] xen/xenbus: Add 'will_handle' callback support in xenbus_watch_path() SeongJae Park
2020-12-17 16:04 ` [PATCH v3 3/5] xen/xenbus/xen_bus_type: Support will_handle watch callback SeongJae Park
2020-12-17 16:04 ` [PATCH v3 4/5] xen/xenbus: Count pending messages for each watch SeongJae Park
2020-12-17 16:05 ` [PATCH v3 5/5] xenbus/xenbus_backend: Disallow pending watch messages SeongJae Park
2020-12-28 11:29 ` [PATCH v3 0/5] Backport of patch series for stable 4.4 branch Greg KH
2021-01-05 10:37   ` SeongJae Park
2021-01-05 10:43     ` Greg KH
2021-01-05 10:51       ` SeongJae Park [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=20210105105107.3564-1-sjpark@amazon.com \
    --to=sjpark@amazon.com \
    --cc=aams@amazon.de \
    --cc=doebel@amazon.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mku@amazon.de \
    --cc=sjpark@amazon.de \
    --cc=stable@vger.kernel.org \
    --cc=wipawel@amazon.de \
    /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®