mbox

pull-request: can-next 2013-08-29

Message ID 521FB992.5080002@pengutronix.de
State Accepted, archived
Delegated to: David Miller
Headers show

Pull-request

git://gitorious.org/linux-can/linux-can-next.git for-davem

Message

Marc Kleine-Budde Aug. 29, 2013, 9:13 p.m. UTC
Hello David,

this is a pull request for net-next. There are two patches from Gerhard
Sittig, which improves the clock handling on mpc5121. Oliver Hartkopp
provides a patch that adds a per rule limitation of frame hops.

regards,
Marc

---

The following changes since commit 7ec06da81d2b98859b558d8d551a0c4e3d9516a3:

  net: packet: document available fanout policies (2013-08-29 16:43:29 -0400)

are available in the git repository at:

  git://gitorious.org/linux-can/linux-can-next.git for-davem

for you to fetch changes up to 391ac1282dd7ff1cb8245cccc5262e8e4173edc4:

  can: gw: add a per rule limitation of frame hops (2013-08-29 22:58:24 +0200)

----------------------------------------------------------------
Gerhard Sittig (2):
      can: mscan: add a comment on reg to idx mapping
      can: mscan: improve clock API use

Oliver Hartkopp (1):
      can: gw: add a per rule limitation of frame hops

 drivers/net/can/mscan/mpc5xxx_can.c | 23 ++++++++++++++++-------
 drivers/net/can/mscan/mscan.c       | 25 ++++++++++++++++++++++++-
 drivers/net/can/mscan/mscan.h       |  3 +++
 include/uapi/linux/can/gw.h         |  9 ++++++++-
 net/can/gw.c                        | 35 +++++++++++++++++++++++++++++++----
 5 files changed, 82 insertions(+), 13 deletions(-)

Comments

Marc Kleine-Budde Sept. 2, 2013, 7:06 p.m. UTC | #1
Hello David,

On 08/29/2013 11:13 PM, Marc Kleine-Budde wrote:
> this is a pull request for net-next. There are two patches from Gerhard
> Sittig, which improves the clock handling on mpc5121. Oliver Hartkopp
> provides a patch that adds a per rule limitation of frame hops.

have you forgotten this pull request?

Marc

> The following changes since commit 7ec06da81d2b98859b558d8d551a0c4e3d9516a3:
> 
>   net: packet: document available fanout policies (2013-08-29 16:43:29 -0400)
> 
> are available in the git repository at:
> 
>   git://gitorious.org/linux-can/linux-can-next.git for-davem
> 
> for you to fetch changes up to 391ac1282dd7ff1cb8245cccc5262e8e4173edc4:
> 
>   can: gw: add a per rule limitation of frame hops (2013-08-29 22:58:24 +0200)
> 
> ----------------------------------------------------------------
> Gerhard Sittig (2):
>       can: mscan: add a comment on reg to idx mapping
>       can: mscan: improve clock API use
> 
> Oliver Hartkopp (1):
>       can: gw: add a per rule limitation of frame hops
> 
>  drivers/net/can/mscan/mpc5xxx_can.c | 23 ++++++++++++++++-------
>  drivers/net/can/mscan/mscan.c       | 25 ++++++++++++++++++++++++-
>  drivers/net/can/mscan/mscan.h       |  3 +++
>  include/uapi/linux/can/gw.h         |  9 ++++++++-
>  net/can/gw.c                        | 35 +++++++++++++++++++++++++++++++----
>  5 files changed, 82 insertions(+), 13 deletions(-)
>
David Miller Sept. 4, 2013, 1:56 a.m. UTC | #2
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Mon, 02 Sep 2013 21:06:10 +0200

> Hello David,
> 
> On 08/29/2013 11:13 PM, Marc Kleine-Budde wrote:
>> this is a pull request for net-next. There are two patches from Gerhard
>> Sittig, which improves the clock handling on mpc5121. Oliver Hartkopp
>> provides a patch that adds a per rule limitation of frame hops.
> 
> have you forgotten this pull request?

If you actually checked the patchwork queue, you're see that this pull
request was still "under review" and there are people who have been
waiting much longer than you have.

I just pulled this in and will push it out once my build tests complete.

There is no reason for you to ever ask me the above question unless
your pull request doesn't show up in patchwork in an appropriate
state.  By default assume I am backlogged and I will get to it
whenever time and my resources allow.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html