All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kernel@pengutronix.de,
	linux-can@vger.kernel.org,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	Bastian Stender <bst@pengutronix.de>,
	Elenita Hinds <ecathinds@gmail.com>,
	Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>,
	Maxime Jayat <maxime.jayat@mobile-devices.fr>,
	Robin van der Gracht <robin@protonic.nl>,
	Oleksij Rempel <ore@pengutronix.de>,
	David Jander <david@protonic.nl>
Subject: Re: pull-request: can-next 2019-10-07
Date: Wed, 9 Oct 2019 09:33:10 +0200	[thread overview]
Message-ID: <3c38ea33-c362-fd85-7801-17e34af18233@pengutronix.de> (raw)
In-Reply-To: <2ffa00e7-d447-9216-587d-30396a47ca64@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 722 bytes --]

Hello David,

On 10/7/19 4:38 PM, Marc Kleine-Budde wrote:
> this is a pull request for net-next/master consisting of 12 patches.

Please don't merge this pull request, it has several shortcomings :(

>   git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-5.5-20191007

I've deleted the tag, so that merging fails, if you try before reading
this mail.

Looking for a brown paper bag,
Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-10-09  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 14:38 pull-request: can-next 2019-10-07 Marc Kleine-Budde
2019-10-08 19:09 ` Jakub Kicinski
2019-10-09  7:40   ` Marc Kleine-Budde
2019-10-09  7:33 ` Marc Kleine-Budde [this message]
2019-11-12 15:57 Marc Kleine-Budde

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=3c38ea33-c362-fd85-7801-17e34af18233@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=bst@pengutronix.de \
    --cc=davem@davemloft.net \
    --cc=david@protonic.nl \
    --cc=dev.kurt@vandijck-laurijssen.be \
    --cc=ecathinds@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=maxime.jayat@mobile-devices.fr \
    --cc=netdev@vger.kernel.org \
    --cc=ore@pengutronix.de \
    --cc=robin@protonic.nl \
    --cc=socketcan@hartkopp.net \
    /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.