public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Boaz Harrosh <bharrosh@panasas•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
	James.Bottomley@HansenPartnership•com,
	linux-next@vger•kernel.org, Sam Ravnborg <sam@ravnborg•org>,
	michaelc@cs•wisc.edu, fujita.tomonori@lab•ntt.co.jp,
	jeff@garzik•org, osd-dev@open-osd•org,
	linux-scsi@vger•kernel.org, Sami.Iren@seagate•com,
	Pete Wyckoff <pw@padd•com>,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
Date: Mon, 10 Nov 2008 14:52:21 +0200	[thread overview]
Message-ID: <49182E85.9010405@panasas.com> (raw)
In-Reply-To: <20081110102607.378c3279.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi Boaz,
> 
> On Sun, 09 Nov 2008 16:58:59 +0200 Boaz Harrosh <bharrosh@panasas•com> wrote:
>> I have prepared a branch for linux-next based on today's Linus tree
>> It is here:
>>     git://git.open-osd.org/linux-open-osd.git linux-next
>> This is if it's OK with James, as these bits are his responsibility.
>> They need only sit in linux-next for a couple of weeks to get some wider
>> compilation exposure. Other then that they are totally new code and
>> are safe. Eventually they should be included into Linux-next through
>> scsi-misc-2.6.
> 
> I have added that tree to linux-next for today.
> 
> What I say to everyone:  commits in that branch must have been posted
> somewhere appropriate, reviewed, unit tested and destined for the next
> merge window.  Also, note that my (new) practise is to temporarily drop a
> tree if it causes non-trivial conflicts (especially with Linus' tree), so
> don't be too upset if you get a message from me to that effect.
> 

Thank you Stephen, very much

This has proven itself already. I found some warnings on some ARCHs
concerning printk of u64 types. I have made a sweep and fixed all these
places and others.
(same place: git://git.open-osd.org/linux-open-osd.git linux-next)

If you could keep it for the next round it could be grate. So I can make
sure I got rid of all the warnings.

Thanks again
Boaz

next prev parent reply	other threads:[~2008-11-10 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48876009.8010701@panasas.com>
     [not found] ` <491073BB.4000900@panasas.com>
2008-11-04 19:19   ` [PATCHSET 00/18] open-osd: OSD Initiator library for Linux Andrew Morton
2008-11-05 13:56     ` Boaz Harrosh
2008-11-09 14:58     ` Boaz Harrosh
2008-11-09 23:26       ` Stephen Rothwell
2008-11-10 12:52         ` Boaz Harrosh [this message]
2008-11-10 13:04           ` 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=49182E85.9010405@panasas.com \
    --to=bharrosh@panasas$(echo .)com \
    --cc=James.Bottomley@HansenPartnership$(echo .)com \
    --cc=Sami.Iren@seagate$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=fujita.tomonori@lab$(echo .)ntt.co.jp \
    --cc=jeff@garzik$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-scsi@vger$(echo .)kernel.org \
    --cc=michaelc@cs$(echo .)wisc.edu \
    --cc=osd-dev@open-osd$(echo .)org \
    --cc=pw@padd$(echo .)com \
    --cc=sam@ravnborg$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox