All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: linux-fpga@vger.kernel.org
Subject: Re: [GIT PULL] firmware: stratix10: fix for v5.17
Date: Wed, 23 Feb 2022 08:32:13 +0100	[thread overview]
Message-ID: <YhXi/Yx6Vc/fpCrx@kroah.com> (raw)
In-Reply-To: <20220222162801.385838-1-dinguyen@kernel.org>

On Tue, Feb 22, 2022 at 10:28:01AM -0600, Dinh Nguyen wrote:
> The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
> 
>   Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/stratix10_svc_fix_v5.17
> 
> for you to fetch changes up to 41a069ab421a9540f75314d3e1bfe5fec6bfdf9f:
> 
>   firmware: stratix10-svc: add missing callback parameter on RSU (2022-02-17 06:05:42 -0600)
> 
> ----------------------------------------------------------------
> Stratix10 Service Driver fix for v5.17
> - Add a missing callback parameter
> 
> ----------------------------------------------------------------
> Ang Tien Sung (1):
>       firmware: stratix10-svc: add missing callback parameter on RSU
> 
>  drivers/firmware/stratix10-svc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

You forgot to tag the stable tree with this fix.

Please resend this just as a single patch, no need for a pull request
for something like that.  If it was sent as a patch, I could have fixed
it up on my own.

Also, consider adding the "Link:" tag to the original patch submission.

Please fix up and resend.

thanks,

greg k-h

      reply	other threads:[~2022-02-23  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 16:28 [GIT PULL] firmware: stratix10: fix for v5.17 Dinh Nguyen
2022-02-23  7:32 ` 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=YhXi/Yx6Vc/fpCrx@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dinguyen@kernel.org \
    --cc=linux-fpga@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.