From: Greg KH <gregkh@linuxfoundation.org>
To: Oded Gabbay <oded.gabbay@gmail.com>
Cc: Oded Gabbay <ogabbay@kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] habanalabs fixes for 5.13-rc2
Date: Mon, 10 May 2021 16:31:13 +0200 [thread overview]
Message-ID: <YJlDsZMuPs8U1kD9@kroah.com> (raw)
In-Reply-To: <CAFCwf11uA7PscSpkQ7BD+FW7+dFy1_GoeaPJSLDS_VnQKhoa6g@mail.gmail.com>
On Sat, May 08, 2021 at 11:46:14AM +0300, Oded Gabbay wrote:
> On Sat, May 8, 2021 at 11:42 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Sat, May 08, 2021 at 11:39:31AM +0300, Oded Gabbay wrote:
> > > Hi Greg,
> > >
> > > This pull request contains a number of important fixes for 5.13-rc2.
> > > Mainly fixes to support our new F/W with enhanced security features,
> > > but also additional bugs.
> > > See details in the tag message below.
> >
> > Does this include the stuff in your previous pull request? Should I
> > drop that one from my queue or do both?
> >
> > I will be waiting until after 5.13-rc1 before I can take any of these...
> >
> > thanks,
> >
> > greg k-h
>
> Yes, it includes that one. For some reason, lkml didn't show me that
> the previous email was sent so I thought there was again a problem in
> the mail server.
> And therefore, I've sent this one again with 1 additional fix compared
> to the previous one.
> So you can drop the previous one.
Ok, now dropped the old one and pulled in this one, thanks!
greg k-h
next prev parent reply other threads:[~2021-05-10 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 8:39 [git pull] habanalabs fixes for 5.13-rc2 Oded Gabbay
2021-05-08 8:42 ` Greg KH
2021-05-08 8:46 ` Oded Gabbay
2021-05-10 14:31 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-02 16:16 Oded Gabbay
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=YJlDsZMuPs8U1kD9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--cc=ogabbay@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;
as well as URLs for NNTP newsgroup(s).