From: Greg KH <gregkh@linuxfoundation.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: airlied@redhat.com, akpm@linux-foundation.org, arnd@arndb.de,
daniel.vetter@ffwll.ch, david@redhat.com, dongwon.kim@intel.com,
hch@infradead.org, hughd@google.com, jgg@nvidia.com,
junxiao.chang@intel.com, kraxel@redhat.com, osalvador@suse.de,
peterx@redhat.com, stable@vger.kernel.org,
vivek.kasireddy@intel.com, willy@infradead.org
Subject: Re: FAILED: patch "[PATCH] mm/gup: avoid an unnecessary allocation call for" failed to apply to 6.11-stable tree
Date: Sun, 17 Nov 2024 22:48:08 +0100 [thread overview]
Message-ID: <2024111701-footsore-bouncing-7834@gregkh> (raw)
In-Reply-To: <0b27eaaa-2ae7-422b-8b22-e92e49ab439c@nvidia.com>
On Sun, Nov 17, 2024 at 01:38:42PM -0800, John Hubbard wrote:
> On 11/17/24 1:27 PM, John Hubbard wrote:
> > On 11/17/24 1:25 PM, Greg KH wrote:
> > > On Sun, Nov 17, 2024 at 01:19:09PM -0800, John Hubbard wrote:
> > > > On 11/17/24 12:33 PM, gregkh@linuxfoundation.org wrote:
> > ...
> > > Patch is line-wrapped :(
> > >
> > > Can you resend it in a format I can apply it in?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > OK, I'm going to use git-send-email after all. Thunderbird is clearly
> > not The Way here. Just a sec. :)
> >
>
> OK, I've sent the fixed up version, here:
>
> https://lore.kernel.org/20241117213229.104346-1-jhubbard@nvidia.com
That worked, thanks!
prev parent reply other threads:[~2024-11-17 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 20:33 FAILED: patch "[PATCH] mm/gup: avoid an unnecessary allocation call for" failed to apply to 6.11-stable tree gregkh
2024-11-17 21:19 ` John Hubbard
2024-11-17 21:25 ` Greg KH
2024-11-17 21:27 ` John Hubbard
2024-11-17 21:38 ` John Hubbard
2024-11-17 21:48 ` Greg KH [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=2024111701-footsore-bouncing-7834@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel.vetter@ffwll.ch \
--cc=david@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=junxiao.chang@intel.com \
--cc=kraxel@redhat.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vivek.kasireddy@intel.com \
--cc=willy@infradead.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