linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Luciano Coelho <coelho@ti.com>
Subject: Re: linux-next: manual merge of the wireless-next tree with the net-next tree
Date: Sun, 10 Feb 2013 18:58:47 -0800	[thread overview]
Message-ID: <1360551527.2028.10.camel@joe-AO722> (raw)
In-Reply-To: <20130211133350.5f510bbb28759960a19a98af@canb.auug.org.au>

On Mon, 2013-02-11 at 13:33 +1100, Stephen Rothwell wrote:
> Hi John,
> 
> Today's linux-next merge of the wireless-next tree got conflicts in
> drivers/net/wireless/ti/wlcore/sdio.c and
> drivers/net/wireless/ti/wlcore/spi.c between commit 0d2e7a5c6080
> ("wireless: Remove unnecessary alloc/OOM messages, alloc cleanups") from
> the net-next tree and commit afb43e6d88e5 ("wlcore: remove if_ops from
> platform_data") from the wireless-next tree.
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
> 

Thanks Stephen.

Can you remove just the dev_err below too please.

+       pdev_data = kzalloc(sizeof(*pdev_data), GFP_KERNEL);
+       if (!pdev_data) {
+               dev_err(&func->dev, "can't allocate platdev_data\n");
+               goto out;
+       }

Joe

  reply	other threads:[~2013-02-11  2:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  2:33 linux-next: manual merge of the wireless-next tree with the net-next tree Stephen Rothwell
2013-02-11  2:58 ` Joe Perches [this message]
2013-02-11  6:47   ` Luciano Coelho
2013-02-11  7:40     ` Stephen Rothwell
2013-02-11  7:53       ` Luciano Coelho
2013-02-11  8:02         ` [PATCH] wlcore: remove newly introduced alloc/OOM messages Luciano Coelho
2013-02-11  8:06           ` Luciano Coelho
2013-02-11  8:07           ` Joe Perches
2013-02-11  8:07             ` Luciano Coelho
2013-02-11  8:08           ` Felipe Balbi
2013-02-11  8:21         ` [PATCH v2] " Luciano Coelho
2013-02-11  8:24           ` Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2014-03-07  1:07 linux-next: manual merge of the wireless-next tree with the net-next tree Stephen Rothwell
2013-09-27  3:19 Stephen Rothwell
2013-06-27  4:23 Stephen Rothwell
2013-06-27  7:34 ` Berg, Johannes
2013-06-04  2:33 Stephen Rothwell
2012-06-28  2:40 Stephen Rothwell
2012-05-03  1:31 Stephen Rothwell
2012-05-03  1:35 ` David Miller
2012-04-24  2:48 Stephen Rothwell
2012-04-24  5:07 ` Grumbach, Emmanuel
2012-04-16  2:49 Stephen Rothwell
2012-04-16  2:49 Stephen Rothwell
2012-04-16  2:48 Stephen Rothwell
2012-04-13  2:41 Stephen Rothwell
2012-04-13  2:49 ` Stephen Rothwell
2012-04-13  2:30 Stephen Rothwell
2012-04-13  2:51 ` Stephen Rothwell
2012-04-11  2:56 Stephen Rothwell
2012-04-10  1:32 Stephen Rothwell
2012-03-16  1:58 Stephen Rothwell
2012-02-01  2:39 Stephen Rothwell
2012-01-05  3:04 Stephen Rothwell
2012-01-05  3:12 ` Larry Finger
2012-01-05  3:30   ` David Miller
2012-01-05  3:45   ` Stephen Rothwell
2011-12-21 11:59 Stephen Rothwell

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=1360551527.2028.10.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=coelho@ti.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).