mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfgang Walter <linux@stwm.de>
To: David Miller <davem@davemloft.net>
Cc: xiaofeng.yan2012@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ap420073@gmail.com,
	yanxiaofeng7@jd.com
Subject: Re: [PATCH v2] hsr: Fix a compilation error
Date: Wed, 22 Jan 2020 13:27:37 +0100	[thread overview]
Message-ID: <2043688.Di36XlgKKK@stwm.de> (raw)
In-Reply-To: <20200120.132136.1992070505971817725.davem@davemloft.net>

Am Montag, 20. Januar 2020, 13:21:36 schrieb David Miller:
> From: "xiaofeng.yan" <xiaofeng.yan2012@gmail.com>
> Date: Mon, 20 Jan 2020 14:26:39 +0800
> 
> > From: "xiaofeng.yan" <yanxiaofeng7@jd.com>
> > 
> > A compliation error happen when building branch 5.5-rc7
> > 
> > In file included from net/hsr/hsr_main.c:12:0:
> > net/hsr/hsr_main.h:194:20: error: two or more data types in declaration
> > specifiers> 
> >  static inline void void hsr_debugfs_rename(struct net_device *dev)
> > 
> > So Removed one void.
> > 
> > Fixes: 4c2d5e33dcd3 ("hsr: rename debugfs file when interface name is
> > changed") Signed-off-by: xiaofeng.yan <yanxiaofeng7@jd.com>
> > Acked-by: Taehee Yoo <ap420073@gmail.com>
> 
> Applied, thank you.

This seems to be the same fix as the fix from Arnd Bergmann:

	https://lkml.org/lkml/2020/1/7/876

which was applied to net-next:

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b9ae51273655a72a12fba730843fd72fb132735a

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

      reply	other threads:[~2020-01-22 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20  6:26 xiaofeng.yan
2020-01-20 12:21 ` David Miller
2020-01-22 12:27   ` Wolfgang Walter [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=2043688.Di36XlgKKK@stwm.de \
    --to=linux@stwm.de \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xiaofeng.yan2012@gmail.com \
    --cc=yanxiaofeng7@jd.com \
    /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

all inboxes | Powered by JetHome®