public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, Dan Williams <dcbw@redhat.com>,
	libertas-dev@lists.infradead.org, netdev@vger.kernel.org,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: manual merge of the wireless tree with Linus' tree
Date: Tue, 17 Aug 2010 12:29:44 +0930	[thread overview]
Message-ID: <201008171229.46175.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100817115203.e8a76e44.sfr@canb.auug.org.au>

On Tue, 17 Aug 2010 11:22:03 am Stephen Rothwell wrote:
> Hi John,
> 
> Today's linux-next merge of the wireless tree got a conflict in
> drivers/net/wireless/libertas/if_sdio.c between commit
> 886275ce41a9751117367fb387ed171049eb6148 ("param: lock if_sdio's
> lbs_helper_name and lbs_fw_name against sysfs changes") from Linus' tree
> and commit 3d32a58b87cd251b50842f93b87d5458061c0cfc ("libertas: [sdio]
> use common firmware request helper and new firmware locations") from the
> wireless tree.
> 
> OK, I can't quite figure out what is going on here.  The latter commit
> removes that code that was modified by the former, so I effectively
> reverted the former commit (by using this file from the wireless tree)
> since the "helper" and "firmware" fields of struct if_sdio_card don't
> seem to be used anywhere anymore.  Can they be removed as well?

I'm looking at the wireless tree now.

You can drop the commit as you have done.  But it leaves three problematic
writable charp parameters in the libertas/ directory which now need lifetime
management.

ie. kparam_block_sysfs_write()/unblock around them, and probably they need
to be copied.

Cheers,
Rusty.




  reply	other threads:[~2010-08-17  2:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  1:52 linux-next: manual merge of the wireless tree with Linus' tree Stephen Rothwell
2010-08-17  2:59 ` Rusty Russell [this message]
2010-08-17  3:07   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2014-02-14  0:19 Stephen Rothwell
2012-01-04  1:40 Stephen Rothwell
2011-09-20  3:28 Stephen Rothwell
2011-09-20 12:55 ` John W. Linville
2011-09-20  3:22 Stephen Rothwell
2011-09-19  5:14 Stephen Rothwell
2011-09-19  5:28 ` Luciano Coelho
2011-09-15  3:14 Stephen Rothwell
2011-09-15  7:17 ` Helmut Schaa
2011-09-15  3:14 Stephen Rothwell
2011-08-30  3:46 Stephen Rothwell
2011-05-12  1:42 Stephen Rothwell
2011-05-11  1:52 Stephen Rothwell
2011-04-27  1:00 Stephen Rothwell
2011-04-13  2:30 Stephen Rothwell
2011-04-08  4:10 Stephen Rothwell
2011-04-08  5:11 ` Jussi Kivilinna
2011-04-08  4:10 Stephen Rothwell
2010-09-21  2:20 Stephen Rothwell
2010-09-21  2:09 Stephen Rothwell
2010-09-21  6:53 ` Ohad Ben-Cohen
2010-09-21  8:57   ` Ohad Ben-Cohen
2010-09-21 15:08 ` John W. Linville
2010-06-15  2:00 Stephen Rothwell
2010-06-15 14:42 ` John W. Linville
2010-05-10  1:27 Stephen Rothwell
2010-04-27  1:28 Stephen Rothwell
2010-01-06  2:29 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=201008171229.46175.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dcbw@redhat.com \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    /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