Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, kernel@pengutronix.de, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2017-01-24,pull-request: can-next 2017-01-24
Date: Fri, 27 Jan 2017 11:24:44 -0500 (EST)	[thread overview]
Message-ID: <20170127.112444.682986770132734034.davem@davemloft.net> (raw)
In-Reply-To: <37eedb82-54d7-c7a9-0cd6-ed26738efff7@pengutronix.de>

From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Fri, 27 Jan 2017 10:02:09 +0100

> this is a pull request of 4 patches for net-next/master.
> 
> The first patch by Oliver Hartkopp adds a netlink API to configure the
> interface termination of a CAN card. The next two patches are by me and
> add a netlink API to query and configure CAN interfaces that only
> support fixed bitrates. The last patch by Colin Ian King simplifies the
> return path in the softing_cs driver's softingcs_probe() function.

Pulled, thanks.

      reply	other threads:[~2017-01-27 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27  9:02 pull-request: can-next 2017-01-24 Marc Kleine-Budde
2017-01-27 16:24 ` David Miller [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=20170127.112444.682986770132734034.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox