linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Felix Fietkau <nbd@openwrt.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"Justin P. Mattock" <justinmattock@gmail.com>
Subject: linux-next: manual merge of the trivial tree with the wireless tree
Date: Mon, 11 Apr 2011 13:28:44 +1000	[thread overview]
Message-ID: <20110411132844.fa651c08.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

Hi Jiri,

Today's linux-next merge of the trivial tree got a conflict in
drivers/net/wireless/ath/ath9k/phy.h between commit a9b6b2569cf1
("ath9k_hw: turn a few big macros into functions") from the wireless tree
and commit 6eab04a87677 ("treewide: remove extra semicolons") from the
trivial tree.

The former commit removed the code that the latter changed, so I did that.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-04-11  3:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  3:28 Stephen Rothwell [this message]
2011-04-11 15:15 ` linux-next: manual merge of the trivial tree with the wireless tree Justin P. Mattock
2011-04-11 15:17   ` Jiri Kosina
2011-04-11 15:24     ` Justin P. Mattock
2011-04-13  9:14 ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2013-08-21  4:20 Stephen Rothwell
2011-04-27  1:43 Stephen Rothwell
2011-04-27  9:22 ` Jiri Kosina
2009-11-17  4:49 Stephen Rothwell
2009-11-17 22:18 ` Jiri Kosina
2009-11-17 23:38   ` Stephen Rothwell
2009-06-03  5:22 Stephen Rothwell
2009-06-03  8:07 ` Jiri Kosina
2009-06-03  8:14   ` Johannes Berg

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=20110411132844.fa651c08.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jkosina@suse.cz \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).