All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Coresight ML <coresight@lists.linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL v2] Coresight changes for v5.16
Date: Wed, 27 Oct 2021 19:41:08 +0200	[thread overview]
Message-ID: <YXmPNNig91Pay9U5@kroah.com> (raw)
In-Reply-To: <CANLsYkwcUbV-kX3yZt6K0rK9PBUpkW=fp2_Y5Bd3+fCgxZr4EA@mail.gmail.com>

On Wed, Oct 27, 2021 at 11:32:43AM -0600, Mathieu Poirier wrote:
> On Wed, 27 Oct 2021 at 00:50, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Oct 26, 2021 at 01:55:45PM -0600, Mathieu Poirier wrote:
> > > The following changes since commit 5816b3e6577eaa676ceb00a848f0fd65fe2adc29:
> > >
> > >   Linux 5.15-rc3 (2021-09-26 14:08:19 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > >   git@gitolite.kernel.org:pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v5.16
> >
> > Better but I get the following errors when my scripts try to merge them.
> > Note, the linux-next scripts will give you the same complaint, so this
> > isn't a new thing:
> 
> Can you point me to the linux-next script you are referring to above?
> Usually when that happens I get an email but this time I didn't get
> anything.

Is this tree/branch in linux-next now?  If so, you should have gotten an
email.

My scripts were sent to the workflow mailing list a year or so ago, I
can dig them up if needed.

thanks,

greg k-h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Coresight ML <coresight@lists.linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL v2] Coresight changes for v5.16
Date: Wed, 27 Oct 2021 19:41:08 +0200	[thread overview]
Message-ID: <YXmPNNig91Pay9U5@kroah.com> (raw)
In-Reply-To: <CANLsYkwcUbV-kX3yZt6K0rK9PBUpkW=fp2_Y5Bd3+fCgxZr4EA@mail.gmail.com>

On Wed, Oct 27, 2021 at 11:32:43AM -0600, Mathieu Poirier wrote:
> On Wed, 27 Oct 2021 at 00:50, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Oct 26, 2021 at 01:55:45PM -0600, Mathieu Poirier wrote:
> > > The following changes since commit 5816b3e6577eaa676ceb00a848f0fd65fe2adc29:
> > >
> > >   Linux 5.15-rc3 (2021-09-26 14:08:19 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > >   git@gitolite.kernel.org:pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v5.16
> >
> > Better but I get the following errors when my scripts try to merge them.
> > Note, the linux-next scripts will give you the same complaint, so this
> > isn't a new thing:
> 
> Can you point me to the linux-next script you are referring to above?
> Usually when that happens I get an email but this time I didn't get
> anything.

Is this tree/branch in linux-next now?  If so, you should have gotten an
email.

My scripts were sent to the workflow mailing list a year or so ago, I
can dig them up if needed.

thanks,

greg k-h

  reply	other threads:[~2021-10-27 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 19:55 [GIT PULL v2] Coresight changes for v5.16 Mathieu Poirier
2021-10-26 19:55 ` Mathieu Poirier
2021-10-27  6:50 ` Greg KH
2021-10-27  6:50   ` Greg KH
2021-10-27 17:32   ` Mathieu Poirier
2021-10-27 17:32     ` Mathieu Poirier
2021-10-27 17:41     ` Greg KH [this message]
2021-10-27 17:41       ` Greg KH
2021-10-27 18:01       ` Mathieu Poirier
2021-10-27 18:01         ` Mathieu Poirier

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=YXmPNNig91Pay9U5@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=coresight@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.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.