All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
	mhi@lists.linux.dev, quic_carlv@quicinc.com, slark_xiao@163.com
Subject: Re: [GIT PULL] MHI changes for v6.3
Date: Thu, 2 Feb 2023 19:17:14 +0300	[thread overview]
Message-ID: <Y9viCijUV3LvQZ8C@kadam> (raw)
In-Reply-To: <Y9vczrEM8Rcb48wC@kroah.com>

On Thu, Feb 02, 2023 at 04:54:54PM +0100, Greg KH wrote:
> On Mon, Jan 30, 2023 at 01:51:31PM +0530, Manivannan Sadhasivam wrote:
> > The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
> > 
> >   Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/mani/mhi.git tags/mhi-for-v6.3
> 
> I get the following error when pulling this in and trying to push it
> out:
> 
> Commit: 62c0f48fa940 ("bus: mhi: ep: Fix off by one in mhi_ep_process_cmd_ring()")
> 	Fixes tag: Fixes: 2527ad44ddb2 ("bus: mhi: ep: Check if the channel is supported by the controller")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> 
> 
> Didn't you get this error also from linux-next?  I use the same scripts as they
> have.
> 
> Please fix up and resend.

Somebody must have done a rebase.  It's now:

Fixes: 6de4941c0215 ("bus: mhi: ep: Check if the channel is supported by the controller")

Manivannan, can you take care of that?

regards,
dan carpenter


  reply	other threads:[~2023-02-02 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  8:21 [GIT PULL] MHI changes for v6.3 Manivannan Sadhasivam
2023-02-02 15:54 ` Greg KH
2023-02-02 16:17   ` Dan Carpenter [this message]
2023-02-02 17:29     ` Manivannan Sadhasivam
2023-02-02 17:28   ` Manivannan Sadhasivam

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=Y9viCijUV3LvQZ8C@kadam \
    --to=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=mani@kernel.org \
    --cc=mhi@lists.linux.dev \
    --cc=quic_carlv@quicinc.com \
    --cc=slark_xiao@163.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 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.