From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martyn Welch <martyn.welch@collabora.co.uk>
Cc: Linux Driver Project Developer List <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] VME Subsystem patches for 4.13-rc7
Date: Fri, 1 Sep 2017 19:15:18 +0200 [thread overview]
Message-ID: <20170901171518.GA31446@kroah.com> (raw)
In-Reply-To: <20170901170848.GA30668@hermes.home>
On Fri, Sep 01, 2017 at 06:08:48PM +0100, Martyn Welch wrote:
> The following changes since commit 0f9b011d3321ca1079c7a46c18cb1956fbdb7bcb:
>
> driver core: bus: Fix a potential double free (2017-08-31 18:57:30 +0200)
>
> are available in the git repository at:
>
> https://gitlab.collabora.com/martyn/linux.git tags/vme-next-4.13-rc7
>
> for you to fetch changes up to 92203389d32f83f71cb1944840af31ffb3a42e6f:
>
> vme: tsi148: Adjust 14 checks for null pointers (2017-09-01 14:08:46 +0100)
>
> ----------------------------------------------------------------
> VME Subsystem changes for driver-core-next v4.13-rc7
>
driver-core? No, you should make this against char-misc-next. But
really, just make it against 4.13-rc7 and then it shouldn't matter what
tree I pull it into.
Also, can you provide more merge text information? A one line really
doesn't say what is going on here. Look on lkml for lots of examples of
what people put here.
As an example, see the emails I send to Linus for when I ask him to pull
the char-misc tree.
thanks,
greg k-h
prev parent reply other threads:[~2017-09-01 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 17:08 [GIT PULL] VME Subsystem patches for 4.13-rc7 Martyn Welch
2017-09-01 17:15 ` Greg Kroah-Hartman [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=20170901171518.GA31446@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martyn.welch@collabora.co.uk \
/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